From owner-freebsd-questions@FreeBSD.ORG Fri Jul 28 04:40:56 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAC7316A4DE for ; Fri, 28 Jul 2006 04:40:56 +0000 (UTC) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E18343D45 for ; Fri, 28 Jul 2006 04:40:56 +0000 (GMT) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.11/8.12.11) with ESMTP id k6S4etH3073211 for ; Fri, 28 Jul 2006 00:40:55 -0400 (EDT) (envelope-from wayne@manor.msen.com) Message-Id: <200607280440.k6S4etH3073211@manor.msen.com> To: freebsd-questions@freebsd.org From: "Michael R. Wayne" Date: Fri, 28 Jul 2006 00:40:55 -0400 Sender: wayne@manor.msen.com Subject: Can not add partitions to existing 3ware RAID? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 04:40:56 -0000 Tonite I was going to allocate some more disk space to a 6.1 RELEASE system. I did it the same way I've done it for years: I went into sysinstall, selected Custom->Partition and added a new partition (twed0s3) using some of the remaining space. I then moved up to twed0s1 and did an "S" because sysinstall never remembers that the first slice was bootable and not doing this leaves one with an unbootable system. I then do a "W" to write out this information, say "Yes" to the warning since I am modifying an existing system and select the Standard Boot Manager. Instead of the normal response, I get ERROR: Unable to write data to disk twed0! and Disk partition write returned an error status! which is most disconcerting. No messages in the logs or on the (serial) console. Checking sysinstall again, the disk remains unchanged. Has something recently changed in this process? /\/\ \/\/