• Post Reply Bookmark Topic Watch Topic
  • New Topic

File system error  RSS feed

Renu, Vairagade
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Help needed urgently!
I use Red Hat 6.2 Linux. Recently, after sudden shutdown due to an unexpected power failure my machine failed to start Linux properly. The boot process halts after showing the following error message:
Setting hostname dexter
Checking root file system
/dev/hda3 contains a file system with errors, check forced.
/dev/hda3 :
Directory inode 35302, block 0, offset 0 : directory currupted.
(i.e., without -a or -p options)
***An error occurred during the file system check.
***Dropping you to a shell, the system will reboot
***when you leave the shell.
Give root password for maintenance
(or type Control-D for normal startup) :

Here I logged in giving root password and then ran fsck. But it didn't correct the file system error. And Control-D doesn't give normal startup. What should I do to solve this problem? Please help.
Tim Holloway
Saloon Keeper
Posts: 18799
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What sort of errors did fsck display that made you conclude that the problem wasn't fixed (aside from the fact that it still won't boot!)?
Sometimes I've found that it's necessary to run fsck 2 or 3 times to get all of the garbage out.
You may have better luck booting from your recovery disk and running fsck from there. Or, if you're running ext2 and not ext3, you might want to go to http://www.toms.net/rb/ and download a copy of Tom's small recovery boot floppy - it packs a fairly complete recovery system (even SCSI!) on a single floppy.
If you boot from a recovery disk and get a "clean" fsck, you may want to mount the partition and manually check it for missing OS components (you won't get vey far if something like /usr/sbin got clobbered!). You might have to do a re-install of the OS.
I broke down and bought a UPS several years back. Power around here can be pretty unreliable and I'd just had lightning damage my modem. The modem cost nearly as much as the UPS (modems were more expensive back them!), and the UPS came with a $25,000 equipment protection warranty that covered not only the modem, but the whole computer.
I'm glad I did. It used to be really frustrating to be in the middle of coding something and lose it all because the lights flickered. These days I have a "smart" UPS that lets Linux know when I'm on battery power and can even shut down the system cleanly when the batteries run out.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!