From owner-freebsd-hackers Tue Oct 3 05:51:53 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA28557 for hackers-outgoing; Tue, 3 Oct 1995 05:51:53 -0700 Received: from ic.net (falcon.ic.net [152.160.101.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id FAA28552 for ; Tue, 3 Oct 1995 05:51:50 -0700 Received: by ic.net (Smail3.1.28.1 #6) id m0t06oo-000grMC; Tue, 3 Oct 95 08:51 WET DST Message-Id: From: rdm@ic.net (Rob Misiak) Subject: Re: system crash - help! To: hackers@freefall.FreeBSD.org Date: Tue, 3 Oct 1995 08:51:34 -0400 (EDT) In-Reply-To: from "rdm" at Oct 3, 95 08:49:28 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1206 Sender: owner-hackers@FreeBSD.org Precedence: bulk I wrote: > > 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 [snip] Ok, in case anyone is interested, I fixed the problem. What happened is fsck (I think that's what did this) marked some files - including /etc/ttys (causing the login problem) and /etc/hosts - character devices. I luckily had the 2.0.5-release CD lying around, so I replaced all of the messed up files I could find, and the system is back to normal. Thinking back a to a couple months ago, I remember when a friend of mine tried FreeBSD he had a sort of similar problem after a system crash, and never could get the system back to normal. Perhaps it is a problem with fsck? Rob