From owner-freebsd-current Mon Nov 16 09:42:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05894 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:42:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05778 for ; Mon, 16 Nov 1998 09:42:13 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id MAA00377; Mon, 16 Nov 1998 12:41:42 -0500 (EST) Message-Id: <4.1.19981116114107.00b99350@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 16 Nov 1998 11:42:34 -0500 To: "Steven P. Donegan" From: Forrest Aldrich Subject: Re: Nasty rebooting in 3.0 current Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <4.1.19981116111511.00b92100@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One more detail with regards to this reboot. I discovered (overlooked) a comment from /var/log/messages that / was not unmounted cleanly. I brought the machine into single-user mode and found that the other filesystems had not been unmounted cleanly. I suppose this could have been the result of the panic reboot. Previously, though, the boot sequence would automatically perform the appropriate fsck. I did this manually in single-user mode and will keep an eye on it. Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message