From owner-freebsd-bugs Thu Jun 8 11: 0: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BBFBB37BC24 for ; Thu, 8 Jun 2000 11:00:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA95354; Thu, 8 Jun 2000 11:00:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 8 Jun 2000 11:00:01 -0700 (PDT) Message-Id: <200006081800.LAA95354@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Chris Wilkes Subject: Re: bin/12421: sysinstall label fails Reply-To: Chris Wilkes Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/12421; it has been noted by GNATS. From: Chris Wilkes To: freebsd-gnats-submit@FreeBSD.org, aa8vb@ipass.net Cc: Subject: Re: bin/12421: sysinstall label fails Date: Thu, 08 Jun 2000 10:57:30 -0700 In Randall's bug report he states: Exit sysinstall after Fdisk, restart, then it works. Some sysinstall state seems to be corrupt the first time around. This is the same procedure I have to follow to get /stand/sysinstall to Label the disk correctly. I'm using FreeBSD 4.0; looks like this problem carried over from 3.2. Label never ever works the first time around. I have to quit, then rmdir the directory created. I'm adding 1G of swap space and 58G of file system space to my 60G array, if that matters. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message