At my previous job, I had a Redhat 6.2 box set up that handled a small
amount of mail, ran a few majordomo lists, and did some web serving. This
weekend, the people there unpluged the box on accident and it won't boot
normally because of some errors on /dev/hda8, which just happens to be the /
From what they are tlling me over the phone, this is what is happening.
They turn the machine on, and it gets to LILO: then tries to boot the
kernal. It runs the pre-check on /dev/hda8 ( I had him look at the
/etc/fstab to find out what partition that is, and it's the root / ) and has
a problem. From what he says, it takes him to a point where he can type in
the root password and get to a command-line ( a "pwd" showed /root ) and
tells him he can run fsck manually or hit ^D to kill the shell. I get him
to the command-line with the root password and we tried running fsck with
different parameters, but it doesn't seem to fix it because after a reboot,
it takes him right back to the password prompt after giving the same error
messages when trying to do the initial fsck on /dev/hda8.
What options should I run on fsck to get it to fix the root partition? If
this isn't the correct way to approach this problem, what is?
None of the data on this machine is real critical, but it would be nice for
them to get it back up and running the way it was, because noone there has
the know-how to reinstall and get majordomo running.
Any help is appreciated. I'm not on-site where the machine is, so if it
takes a couple days to get back to any questions you may have, it's because
I have to call them and talk them through anything you guys suggest.