You might try just booting it normally and letting it fail. Then enter th ufs:/dev/ad2s1a
I do this all time when I stick a hd in a fast machine to install FBSD its gets ad4s what ever... but in the machine its ends up it needs to be ad0s whatever. after I mount every manually the first time, I just change my /etc/fstab file to be what it should and everything is happy. On Mon, 22 Apr 2002, Marc Heckmann wrote: > Hi, > > I've got 4.5-STABLE setup here with vinum as per the Vinum bootstrapping howto > (http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/index.html). > > I have ad0s1a which is "/" and ad2s1a which is mounted on /rootback, it's an > exact copy of the "/" filesystem. I wanted to try one of the failure scenarios > from the howto > (http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/failures.html) so I > shutdown the machine, unplugged the ad0 drive. The machine found the boot > loader on ad2 and I have a prompt.. so far so good.. > > I do "boot -as" so that I can manually tell the kernel which root filesystem to > mount. here is what I get: > > ad2: 95396MB <WDC WD1000BB-00CCB0> [193821/16/63] at ata1-master UDMA66 > > Manual root filesystem specification: > <fstype>:<device> Mount <device> using filesystem <fstype> > eg. ufs:/dev/da0s1a > ? List valid disk boot devices > <empty line> Abort manual input > > mountroot> ufs:/dev/ad2s1a > Mounting root from ufs:/dev/ad0s1a <---- NOTE this > Root mount failed: 6 > panic: Root mount failed, startup aborted. > > Why is it still trying to use ad0s1a as the root when I explicitly told it to > use /dev/ad2s1a? > > Any ideas? thanks in advance. > > -m > > -- > m. heckmann. > -- > merconic GmbH, Chausseestr. 128-129, D-10115 Berlin (Mitte) > Telefon +49-30-726265-200, Fax +49-30-726265-211, Durchwahl -200 > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
