Date: Mon, 9 Feb 2004 12:18:52 +0200 From: Ion-Mihai Tetcu <itetcu@apropo.ro> To: Ion-Mihai Tetcu <itetcu@apropo.ro> Cc: Rishi Chopra <rchopra@cal.berkeley.edu> Subject: Re: Booting Problem After Power Loss (fsck)? 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 9 Feb 2004 11:44:46 +0200
Ion-Mihai Tetcu <itetcu@apropo.ro> wrote:
> On Sun, 08 Feb 2004 21:12:51 -0800
> Rishi Chopra <rchopra@cal.berkeley.edu> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040209121852.7a09fcab>