From owner-freebsd-questions@FreeBSD.ORG Tue Feb 3 01:11:01 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 2D3A916A4CE for ; Tue, 3 Feb 2004 01:11:01 -0800 (PST) Received: from m00.ca.astound.net (m00.ca.astound.net [64.85.239.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4674543D39 for ; Tue, 3 Feb 2004 01:11:00 -0800 (PST) (envelope-from rchopra@cal.berkeley.edu) Received: from cal.berkeley.edu (astound-64-85-229-134.ca.astound.net [64.85.229.134]) by m00.ca.astound.net (8.12.10/8.12.10) with ESMTP id i1399GKL030381 for ; Tue, 3 Feb 2004 01:09:16 -0800 Message-ID: <401F6542.2090504@cal.berkeley.edu> Date: Tue, 03 Feb 2004 01:09:22 -0800 From: Rishi Chopra User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org References: <401F1A5E.8040105@cal.berkeley.edu> In-Reply-To: <401F1A5E.8040105@cal.berkeley.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Subject: Re: Booting Problem 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: Tue, 03 Feb 2004 09:11:01 -0000 I booted into single-user mode and ran 'fsck' - the latest output to the terminal says: **** FILE SYSTEM MARKED CLEAN **** /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes **** FILE SYSTEM STILL DIRTY **** Will fsck continue attempting to fix the filesystem? Have I suffered a total loss or is fsck still doing its thing? If this is a total loss, can I do anything to get my data back? -Rishi Rishi Chopra wrote: > I'm getting the following error message during startup: > > /usr: mount pending error: blocks 16 files 1 > > I'm guessing this orrcured due to a shutdown during background fsck of > the filesystem. > > Will the error fix itself (e.g. will the boot process continue and > finally proceed to a prompt) or do I need to intervene? If intervention > is required, how would I go about setting things right? > -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra