Date: Fri, 16 Oct 1998 12:03:44 -0400 From: Chris Johnson <cjohnson@palomine.net> To: Jaye Mathisen <mrcpu@internetcds.com>, stable@FreeBSD.ORG Subject: Re: Annoying >2.2.5 oddity on reboot. Message-ID: <19981016120344.A23647@palomine.net> In-Reply-To: <Pine.NEB.3.95.981016082329.2118L-100000@schizo.cdsnet.net>; from Jaye Mathisen on Fri, Oct 16, 1998 at 08:27:08AM -0700 References: <Pine.NEB.3.95.981016082329.2118L-100000@schizo.cdsnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 16, 1998 at 08:27:08AM -0700, Jaye Mathisen wrote:
>
>
> I have a bunch of DEC ZX and HX 6000 P6 boxes. Have been running 2.2.5
> for heap 'um big long time, zero troubles.
>
> So I upgraded 2 of them to -stable as of yesterday.
>
> Now neither of them will reboot properly. They shutdown, and get to the
> stage where they should start reloading, and they just hang.
The following, from the 2.2.6 errata, might help:
---- System Update Information:
o Root mountpoint change which affects those upgrading via
"make world" or a FreeBSD 2.2.6 upgrade.
Fix: 2.2.6 introduces a change in the naming of the device from
which the root filesystem is mounted. This change affects all systems,
however user intervention is only required for systems undergoing an
upgrade installation.
Previously, the root filesystem was always mounted from the
compatibility slice, while other partitions on the same disk were
mounted from their true slice. This might, for example, have resulted
in an /etc/fstab file like:
# Device Mountpoint FStype Options Dump Pass#
/dev/wd0s2b none swap sw 0 0
/dev/wd0a / ufs rw 1 1
/dev/wd0s2f /local0 ufs rw 1 1
/dev/wd0s2e /usr ufs rw 1 1
For FreeBSD 2.2.6 and later, this format changes so that the device for
'/' is consistent with others, ie.
# Device Mountpoint FStype Options Dump Pass#
/dev/wd0s2b none swap sw 0 0
/dev/wd0s2a / ufs rw 1 1
/dev/wd0s2f /local0 ufs rw 1 1
/dev/wd0s2e /usr ufs rw 1 1
If /etc/fstab is not updated manually in this case, the system will
issue a warning message whenever / is mounted (normally at startup)
indicating the change that must be made. In addition, trouble may be
experienced if the root filesystem is not correctly unmounted, whereby
the root filesystem will not be marked clean at the next reboot.
This change should be made as soon as the upgraded system has been
successfully rebooted.
------------------------------
Chris Johnson
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981016120344.A23647>