0

i am using Red Hat linux 9.0.
when i booting the system it gives
"filesystem error.Run fsck manually."
and asking for root password for maintanace. when i raun fsck .the system booting without giving errors.once we restart the computer it gives same error as above"
so can u give me solution?

7
Contributors
6
Replies
7
Views
12 Years
Discussion Span
Last Post by Trinco
0

Is this a new install? ie can you wipe and start over or are you trying to upgrade? When my old machines give me this its usually some bad areas on the drive and I just reformat and reinstall.

0

i am using Red Hat linux 9.0.
when i booting the system it gives
"filesystem error.Run fsck manually."
and asking for root password for maintanace. when i raun fsck .the system booting without giving errors.once we restart the computer it gives same error as above"
so can u give me solution?

Run fsck.....Itz a filesystem checking command......
"e2fsck -b ext2(0r 8193) /dev/hda0(or 1 or 2 or 3)"
Most probably the above command will fix the problem....

0

From In search of l33t [subverted.net]:

You can force an immediate reboot and on the reboot an fsck by issuing the command …
shutdown -F -r

The machine drives will be unmounted cleanly, and the system will reboot. While the machine is rebooting the system will force fsck all drives that are set to mount automatically as specified in /etc/fstab.

The guy also suggests touching forcefsck under root (/). IIRC, both of these things were suggested in Essential System Administrator [oreily.com]

0

i am using Red Hat linux 9.0.
when i booting the system it gives
"filesystem error.Run fsck manually."
and asking for root password for maintanace. when i raun fsck .the system booting without giving errors.once we restart the computer it gives same error as above"
so can u give me solution?

This may be a silly question, but do you shut down the system with the 'shutdown' command before turning it off? If you don't cleanly unmount the disk then cached information won't get written to the disk and it will need an fsck upon reboot.

0

I think the one question the everyone has been missing is which filesystem is it saying needs to have the fsck run? Check the /etc/fstab file and see what partitions you are mounting and make sure that you run fsck on all of them.

0

I experience the same problem just a week ago, the problem was bad clusters on disk, just the sector where GRUB was installed :(
After some fsck's I realise that dropping the old HDD and buying a new one it's the better fix :S
Try HirenBoot live CD, you'll find tools to make low-level formats, maybe you can fix the problem (if you've bad clusters, of course).
Greetings from Argentina!

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.