From owner-freebsd-stable Fri Oct 16 09:06:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16167 for freebsd-stable-outgoing; Fri, 16 Oct 1998 09:06:05 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16103 for ; Fri, 16 Oct 1998 09:05:57 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id JAA19182; Fri, 16 Oct 1998 09:03:51 -0700 (PDT) Date: Fri, 16 Oct 1998 09:03:51 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Chris Johnson cc: stable@FreeBSD.ORG Subject: Re: Annoying >2.2.5 oddity on reboot. In-Reply-To: <19981016120344.A23647@palomine.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not even in the ballpark. We're not even getting to the bootloader on a warm boot. These are also freshinstalls (I've tried both ways), and the fstabs are correct. They cold boot perfectly. Just won't warm reboot, w/o hitting the reset button. On Fri, 16 Oct 1998, Chris Johnson wrote: > 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