shell command to fix filesystem

edit

fsck is used to check and optionally repair one or more Linux file systems, Do not run fsck on a live or mounted file system. Running fsck on a mounted filesystem can usually result in disk and/or data corruption.

If no filesystems are specified on the command line, fsck will default to checking filesystems in /etc/fstab serially. This is equivalent to the -As options.

You can do this with fsck -Vy. And check the exit code of fsck afterwards with

echo $?

. These are some values you could get:

    0 - No errors
    1 - File system errors corrected
    2 - File system errors corrected, system should be rebooted
    4 - File system errors left uncorrected
    8 - Operational error
    16 - Usage or syntax error.
    32 - Fsck canceled by user request
   128 - Shared-library error

Once you are in the debug shell you should be able to run the fsck utility on the corrupted file system, try:

fsck -y

or

fsck -y <target-filesystem>

when it finishes type exit or ctrl+d to resume the normal boot process.

Thanks a lot .... it saved my day....

thanks again. best regards,

thanks for the commands posts here. i have encountered the same problem in fedora 16 full version. but it is finally recovered from the command fsck -y

this is working for my fedora 15 even..Thank you very much

thanks a lot. it worked 4 me.

Hello! I just wanted to say i had the same problem, happened when i upgraded the linux kernel with yumex. I also found that the partition was inside mapper. Thig is after doing the whole process (and ia ran echo $? to verify there were no errors) every time i boot the most recent kernel i keep getting the same message and either i have to do the same process of fsck o just ignore it, type exit and continue booting normally... Is it normal that it keeps giving me the same mistake after running the fsck on the right partition? Thanks for your time!

Hello! I just wanted to say i had the same problem, happened when i upgraded the linux kernel with yumex. I also found that the partition was inside mapper. Thig is after doing the whole process (and ia ran echo $? to verify there were no errors) every time i boot the most recent kernel i keep getting the same message and either i have to do the same process of fsck o just ignore it, type exit and continue booting normally... Is it normal that it keeps giving me the same mistake after running the fsck on the right partition? Thanks for your time!