Date: Mon, 01 Nov 2010 22:03:58 -0700 From: perryh@pluto.rain.com To: dteske@vicor.com Cc: guru@unixarea.de, freebsd-questions@freebsd.org Subject: Re: sysinstall(8) && bsdlabel a new disk Message-ID: <4ccf9bbe.l08XJVISTgP78tSZ%perryh@pluto.rain.com> In-Reply-To: <1288627455.6744.24.camel@localhost.localdomain> References: <20101031200258.GA1302@tiny.Sisis.de> <1288627455.6744.24.camel@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
Devin Teske <dteske@vicor.com> wrote: > sysinstall probes hardware when it starts. Therefore, after making > changes (specifically after writing) to the disk in the FDISK > partition editor, you need to Ctrl-C and Abort-out and relaunch > sysinstall so that it probes the new disk devices (ad4s1, ad4s2, > etc.) before you can start adding BSD disklabels (ad4s1a, ad4s1b, > etc.) to the slice (aka partition). > > This has been an age-old problem (hmmm, perhaps get could some mad > karma for fixing it). At least in 8.1, there is a sysinstall operation somewhere to re-probe devices, presumably to cover exactly this sort of situation. Does it not work?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ccf9bbe.l08XJVISTgP78tSZ%perryh>