Date: Tue, 2 Nov 2010 07:04:08 +0100 From: Matthias Apitz <guru@unixarea.de> To: perryh@pluto.rain.com Cc: dteske@vicor.com, freebsd-questions@freebsd.org Subject: Re: sysinstall(8) && bsdlabel a new disk Message-ID: <20101102060408.GA1860@current.Sisis.de> In-Reply-To: <4ccf9bbe.l08XJVISTgP78tSZ%perryh@pluto.rain.com> References: <20101031200258.GA1302@tiny.Sisis.de> <1288627455.6744.24.camel@localhost.localdomain> <4ccf9bbe.l08XJVISTgP78tSZ%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
El día Monday, November 01, 2010 a las 10:03:58PM -0700, perryh@pluto.rain.com escribió: > 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? My situation was in 9-CURRENT. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <guru@unixarea.de> - w http://www.unixarea.de/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101102060408.GA1860>