From owner-freebsd-questions@FreeBSD.ORG Thu Feb 12 18:20:50 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 789CF16A4CE for ; Thu, 12 Feb 2004 18:20:50 -0800 (PST) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3103743D39 for ; Thu, 12 Feb 2004 18:20:50 -0800 (PST) (envelope-from mark.hessler@verizon.net) Received: from verizon.net ([68.163.225.128]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040213022049.JILK25581.out001.verizon.net@verizon.net> for ; Thu, 12 Feb 2004 20:20:49 -0600 Message-ID: <402C341B.90905@verizon.net> Date: Thu, 12 Feb 2004 21:19:07 -0500 From: Mark Hessler User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [68.163.225.128] at Thu, 12 Feb 2004 20:20:49 -0600 Subject: Fsck complains during bootup but doesn't find anything to repair. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 02:20:50 -0000 Hello, Given X not running, is there a way to interrupt/shutdown the system when it doesn't respond to ctrl^c? My Intel system running a recent 5.1-Release -> 5.2-Release upgrade hung when I typed 'xdm' for the first time. (Normally I start x with 'startx'.) I waited for a while, then powered down. Now the system boots with all four ad0sd1x partitions reporting Warning: 'NO WRITE' and 'UNEXPECTED INCONSISTENCY' during bootup. In single-user mode, I can remount them read/write, as I saw described in a mail thread: mount -u -o ro /dev/ad0sd1a / (example for /, also applies to /tmp, /var and /usr)... then run fsck: fsck / ... all mounts pass- fsck doesn't complain. But each time it boots, fsck run manually reports the same errors as above for all the hard drive mounts. So, to summarize: Question 1: is there a way to shutdown the system properly when it hangs on starting X? I tried logging in remotely and couldn't- apparently sshd wasn't happy. Question 2: what might I do to repair my filesystems or hard drive if either is broken, given that fsck run manually doesn't complain or fix anything once the filesystems have been remounted r/w? (Question 3: why does fsck seem to contradict itself, reporting errors during bootup but not when run manually in single-user mode?) --Mark Hessler, excited new migrant from microsoft.