Date: Thu, 8 Jun 2000 13:20:03 -0700 (PDT) From: Chris Wilkes <cwilkes@singingfish.com> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/12421: sysinstall label fails Message-ID: <200006082020.NAA13894@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/12421; it has been noted by GNATS. From: Chris Wilkes <cwilkes@singingfish.com> To: Randall Hopper <aa8vb@nc.rr.com> Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/12421: sysinstall label fails Date: Thu, 8 Jun 2000 13:14:29 -0700 (PDT) What's odd is that I watched the other admin setup this box and he didn't have to do the exit sysinstall and re-enter when he was doing the inital setup. This problem only seems to occur for me (maybe that's the problem) when trying to add this largish raid array. When going back into the Label portion none of my changes are in there. So I can't see why doing it a second time works ... its not like there is any "stub" information for it to go on and know how to mkfs the drives. Chris on Thu, 8 Jun 2000, Randall Hopper wrote: > Chris Wilkes: > |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. > > Sorry you're having the same trouble, though I'm glad to hear that it > wasn't something specific to my hardware. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006082020.NAA13894>