From owner-freebsd-questions@FreeBSD.ORG Mon Feb 9 02:18:38 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 52AC416A4CE for ; Mon, 9 Feb 2004 02:18:38 -0800 (PST) Received: from rdsnet.ro (smtp.rdsnet.ro [62.231.74.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C2A543D1F for ; Mon, 9 Feb 2004 02:18:37 -0800 (PST) (envelope-from itetcu@apropo.ro) Received: (qmail 9679 invoked from network); 9 Feb 2004 10:17:10 -0000 Received: from unknown (HELO it.buh.cameradicommercio.ro) (81.196.25.19) by mail.rdsnet.ro with SMTP; 9 Feb 2004 10:17:07 -0000 Date: Mon, 9 Feb 2004 12:18:52 +0200 From: Ion-Mihai Tetcu To: Ion-Mihai Tetcu Message-Id: <20040209121852.7a09fcab@it.buh.cameradicommercio.ro> In-Reply-To: <20040209114446.5b8d5689@it.buh.cameradicommercio.ro> References: <401F1A5E.8040105@cal.berkeley.edu> <401F6542.2090504@cal.berkeley.edu> <20040203112519.3f806ab3@it.buh.cameradicommercio.ro> <402716D3.5060604@cal.berkeley.edu> <20040209114446.5b8d5689@it.buh.cameradicommercio.ro> X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: questions@freebsd.org cc: Rishi Chopra Subject: Re: Booting Problem After Power Loss (fsck)? 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: Mon, 09 Feb 2004 10:18:38 -0000 On Mon, 9 Feb 2004 11:44:46 +0200 Ion-Mihai Tetcu wrote: > On Sun, 08 Feb 2004 21:12:51 -0800 > Rishi Chopra wrote: > > > Here's a summary of my problem so far: [..] > To summarize: > > 1. See if you have disk activity when fsck seems to be stuck. > > 2. Try fsck (-p) first on root, the on tmp, /var, /usr, /home. > > 3. Esp. if fsck / doesn't go ok try booting verbose with Fixit CD and > run fsck from there. > > 4. If 1 gets you the same results try putting the disk in another ^^^^^^^^ If 3 gets ... > machine where you have debugging options in the kernel, break to > debugger and gather info from there (esp. if you're running 5.x try > asking on current@ what exactly to look for in the debugger). -- IOnut Unregistered ;) FreeBSD user