Houston, I Have a Problem!

[Mark Holbert]

Wow, I need to keep up on this list a little better!

Actually, I've been having problems with a hard drive in my server (that's
what I get for a $15 hard drive) and have had to run fsck many times on boot
up.  My server has actually droped or lost inodes and fsch was able to at
least fix enough to get it running/limping along again.

When you are asked to hit Cntl-D, or type in the root password as in the
case of Red Hat 6.1 it seems, you should have full access to all of the
drives/partitions/mounts.  All the previous posts were correct that you have
to know on which filesystem the problem is, but I also found that you can
use a mount point such at / or /home to run the fsck against.  I typed fsck
/ and it cleaned everything up for me.  I actually liked the fact that it
prompted me for each recovery step, it was a learning experience.  But at
der.hans pointed out, if there are alot of  problems, you may be hiting 'Y'
A LOT.  According to the man page, fsck -a will run without questions, but
it warns againt it as I would if you don't know what might be lost.

Hope that helps, if not a little bit too late.

Mark Holbert
mark@linuxsoftware.org

>> Right before you got dropped to the Maint login
>> you should have gotten an error telling you which
>> filesystem failed.
>>
>> Determine which linux filesystem it is ( example: /dev/hda3 )
>> and do:
>> e2fsck /dev/hda3
>> to fix the problem.
>
>If it's root you'll also need to remount it rw.
>
>mount -o remount,rw /
>
>I think that's the command. Mark is that what I used at Stammtisch last
week? :)
>
>ciao,
>
>der.hans
>--
>#  der.hans@LuftHans.com   home.pages.de/~lufthans/   www.Opnix.com
>#  I'm not anti-social, I'm pro-individual. - der.hans