topic Re: how to correct the root file system in Operating System - Linux

how to correct the root file system

leyearn — Sat, 18 Feb 2006 07:33:52 GMT

turboliux 7
power off suddenly
the system can't boot
the following wrong messages

CHECKING ROOT FILESYSTEM
/ CONTAINS A FILE SYSTEM WITH ERRORS CHECK FORCED
/ : |===========================
ERROR READING BLOCK 2129978 (ATTEMPT TO READ BLOCK FROM FILESYSTEM
RESULTED IN HORT READ)WHILE DOING INODE SCAN

UNEXCECTED INCONSISTENCY; RUN FSCK ANUALLY

(i.e.,without -a or -p options)
It means that the root file system is corrupted
how can i fix it?

Re: how to correct the root file system

Stuart Browne — Sat, 18 Feb 2006 08:25:36 GMT

First try to boot it into single user mode, and do preceisely what it's telling you ('fsck -r /dev/'. Use 'mount' to find out what that is).

Fix whatever issues it's got.

If it wont allow you to do that, find a bootable linux CD with a 'rescue' or 'repair' mode, and do the fsck from there.

This will hopefully fix the issue.

Re: how to correct the root file system

Vitaly Karasik_1 — Sun, 19 Feb 2006 01:17:58 GMT

Even if you'll be able to boot your system after running fsck, I strongly recommend to check system logs - maybe your harddisk going bad. In this case you should urgently transfer your linux to a new disk.

Re: how to correct the root file system

dirk dierickx — Mon, 20 Feb 2006 02:36:54 GMT

looks like a disk failure to me too.

Re: how to correct the root file system

dipesh_2 — Mon, 20 Feb 2006 03:50:21 GMT

run the system in single user mode. and run fsck command and fixed the error. and take the backup on another disk drive. This is seems tobe disk failuer.

Re: how to correct the root file system

Vipulinux — Mon, 20 Feb 2006 05:20:09 GMT

Hi

I guess you need to check your disk. Download few HE check utilities from net and try to diagnose your disk.

Cheers

Re: how to correct the root file system

Bill Thorsteinson — Mon, 20 Feb 2006 10:12:41 GMT

Booting to single user mode is the correct
way to correct this. FSCK manually.

This is not an unutual occurance using
an unjournaled file system (EXT2).

Once you are up and running consider:
- Check the rc script for the mount and
see if you can set a flag to automatically
fix errors during booting.
- If supported, consider making your root
file system journalled. (EXT3). This
will reduce the likelyhood of such failures
in the future.