From owner-freebsd-hackers  Mon Oct  2 23:54:34 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id XAA22886
          for hackers-outgoing; Mon, 2 Oct 1995 23:54:34 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA22875
          for <hackers@freefall.freebsd.org>; Mon, 2 Oct 1995 23:54:32 -0700
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id XAA17307; Mon, 2 Oct 1995 23:52:59 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id XAA00225; Mon, 2 Oct 1995 23:54:20 -0700
Message-Id: <199510030654.XAA00225@corbin.Root.COM>
To: rdm@ic.net (Rob Misiak)
cc: hackers@freefall.freebsd.org
Subject: Re: system crash - help! 
In-reply-to: Your message of "Tue, 03 Oct 95 02:13:52 EDT."
             <m0t00bw-000gp8C@ic.net> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Mon, 02 Oct 1995 23:54:20 -0700
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

>I am running 2.2-current (but I don't think that's the cause of my problem;
>see below) and I logged out of a vty, and the system just hung. The hard
>disk light was flickering, but I did not hear the disk spin at all. I ended
>up doing a cold reset, and my filesystems ended up a mess. I booted into
>single-user mode, and restored backups of /etc and /usr/local/etc (in case
>any of the files were damaged) and ran fsck, etc. I then rebooted, and
>after the disks were mounted (but right before root was re-mounted for
>read-write) the system hung again. I hit ^C, and I guess skipped whatever
>was hanging, and went on with the rest of the rc files. The same thing
>happened with sendmail, so I hit ^C again. And finally, the system hung
>once more when I was supposed to get the login prompt. Obviously, I couldn't
>do anything here. I tried also booting 2.0.5 generic and 2.1.0-something-snap
>kernels, but the same thing happened. Any idea what caused this, and more
>importantly, how to fix it? The few times that the system did crash before
>nothing like this happened. At the moment I'm stuck in single-user mode using
>cu to log into a shell account, so naturally I'm eager to get the system back
>to they way it used to be. :-)

   Sounds like your nameserver or your network connection went out to lunch.

-DG