Date: Sat, 18 Jun 2005 10:47:52 -0400 From: "Steve Bertrand" <iaccounts@ibctech.ca> To: "'Titus von Boxberg'" <ut@bhi-hamburg.de> Cc: freebsd-questions@freebsd.org Subject: RE: Booting with multiple RAID1 configs Message-ID: <20050618144959.6CADC43D1F@mx1.FreeBSD.org> In-Reply-To: <42B34293.6050300@bhi-hamburg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> You might use loader(8) to set the root device ("rootdev"
> variable) explicitly to ar1s1a. Then you should also update
> fstab to reflect the numbering change.
> I don't know of any way to change the ata numbering scheme.
> Mainboard controllers always seem to be probed (and numbered)
> first. I think there is no way to get your original raid back
> to ar0 if you also use your mainboard controllers.
Thank you so, so much.
After trying to mount / to ufs:/dev/ar1s1a at the MountRoot prompt and
it failing, I thought something more serious was the problem, so:
- I added kern.rootdev=/dev/ar1s1a to sysctl.conf
- Changed the / fs in /etc/fstab to point to /dev/ar1s1a
At that point, the system loaded the root filesystem, but since that was
the only one I changed, it errored out mounting the rest (which was
expected).
I simply mounted them manually /dev/ar1s1N to /usr /var and /home,
remounted the / filesystem rw, ee the /etc/fstab and changed all the
mountpoints to ar1, rebooted, and all is well!
I now have 2 RAID1 configs on the same box, and am successfully booting
off of the promise raid properly before the motherboard disks!!
Thanks to all who provided feedback! I hope this situation can help
someone else who wants to boot off of an arbitrary disk before the
motherboard disk in the future!
Steve
>
> Cheers
> Titus
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050618144959.6CADC43D1F>