Date: Fri, 13 Mar 1998 17:43:02 -0800 From: brian@worldcontrol.com To: freebsd-questions@FreeBSD.ORG Subject: Re: root filesystem and -current (a different twist) Message-ID: <19980313174302.A924@top.worldcontrol.com> In-Reply-To: <v04003a13b12f8002d3ad@[208.140.182.45]>; from Cory Kempf on Fri, Mar 13, 1998 at 08:03:06PM -0500 References: <v04003a0ab12f0521f376@[208.140.182.45]>; <199803130024.SAA11363@toybox.cc.iastate.edu>; <199803130024.SAA11363@toybox.cc.iastate.edu> <19980313133514.09198@freebie.lemis.com> <v04003a0ab12f0521f376@[208.140.182.45]> <19980314101858.58251@freebie.lemis.com> <v04003a13b12f8002d3ad@[208.140.182.45]>
next in thread | previous in thread | raw e-mail | index | archive | help
>> What has happened is relatively complicated: they've eliminated the
>> "compatibility slice", so you will no longer be able to mount
>> /dev/sd0a. Use /dev/sd0s1a instead (in /etc/fstab). Don't be put off
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> by the fact that it will then claim to mount /dev/sd0s2a; that's a
>> known bug.
>
> Tried that.
[it didn't work it seems]
I ran into a interesting twist with regard to this change. I caught
the warning email and had successfully made the changes on most of my
machines.
I did the same thing on my laptop and rebooted to an unable to mount
root message. Funny, I had successfully done the conversion on
other machines.
My laptop has a wd type controller and did _not_ have a /dev/wd0s2a
entry in /dev.
A quick ( cd /dev; ./MAKEDEV wd0s2a ) solved the problem.
(FreeBSD is on the second slice on my laptop)
--
Brian Litzinger <brian@worldcontrol.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980313174302.A924>