Date: Wed, 25 Jul 2007 21:58:33 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: fsck to fix HD problem Message-ID: <20070725215833.58b47a22@gumby.homeunix.com.> In-Reply-To: <460a65190bb88ed0676417e1033dd160@szalbot.homedns.org> References: <d7195cff0707242244q3263040dy1267a40b1be0437f@mail.gmail.com> <460a65190bb88ed0676417e1033dd160@szalbot.homedns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 25 Jul 2007 07:50:38 +0200 Zbigniew Szalbot <zbigniew@szalbot.homedns.org> wrote: > > Hello, > > >> so I decided to use fsck to check my HD. I ran it > >> in the foreground mode with the -y flag. It gives me the below > >> information. My question is - should I worry (it is more a home > >> machine than a real server) and if yes, how can I fix the problem? > > . . . > > > > To do anything more than merely report problems > > you should drop into single-user mode, unmount > > everything except root (hopefully. If it gets angry, > > reboot into single-user mode.) and run fsck (as is > > or with the -y flag if you feel daring.) on the filesystems > > in question. > > Is the single-user mode necessary. As it is a family machine I know > when I am the only one using it. > The fsck output was the normal stuff you see if you pull-out the plug (if you're lucky). Did you check if the background fsck was still running? In practice you rarely need to do do a manual check - most reboots can be handled by a background check, and most cases where it can't are spotted during the initial foreground check and done in the foreground. Just watch the console for unexpected softupdate inconsistencies. If you run fsck with -y, you might as well set "fsck_y_enable=yes" in rc.conf and have it done automatically if the initial preen fails.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070725215833.58b47a22>