File system check failed ошибка

Hi,
I have been getting a filesystem check error since yesterday now and am unable to start Arch. Upon googling and searching the arch fora, I came upon some advice which I tried which has not worked yet. Hence the new post…

Basically, I was attempting to print something off and accidentally chose a printer that was not connected to my laptop. After half a minute or so, it repeatedly started giving me notifications that the printer was not connected…in excess of 200 messages that the printer was not working which continued to pop up despite me canceling the print job. The whole system got really sluggish  (for the first time in the last year) and I had to restart the laptop upon which the boot messages appear.
It gets to the point where its loading the various filesystems. It mounts root and says it fine. Then it says

/dv/sda3: clean, 171642/915712 files, 1837167/3662820 blocks
/dev/sda2 is mounted.  /dev/sda5 is mounted.

Filesystem check failed.
Please repair manually and reboot. Note that the root file system is currently mounted readonly. To remount it read-write type: mount -n -o remount  ,rw /
When you exit the maintenance shell the system will reboot automatically.

In my system,
/dev/sda3 is root
/dev/sda2 is boot
/dev/sda5 is home

I tried fsck which tells me that home and boot are still mounted.
So I booted up using an Ubuntu Live CD and checked and repaired each file system which it successfully did. Upon rebooting into Arch, I am getting the same message.
I have not installed anything new and had upgraded the whole system a few days before the problem started.
Not sure where to go from here.
Any help, please
Thanks

Samsom

Last edited by samsom (2010-01-24 22:42:41)

Модератор: Модераторы разделов

Please do not cargo-cult stuff you found on the Internet, but try to understand what a command does before your enter it.

Your use of sudo is unnecessary — you are already logged in as the root user, and have full access.

The error message you were given indicates that the automatic file system check failed. With ext2, that happened often after a power outage, but with ext3 and ext4, one of which you are likely to be using if your system is newer than ten years, this generally does not happen unless there is faulty hardware involved.

The first command, mount -o rw,remount / essentially tells the system «It is fine, there are no errors on this disk, and you can assume the file system to be consistent enough to write files.» This is a bold statement, especially right after you received an error message stating that a file system check found problems that are so bad that the automated repairs would probably have to delete files in order to get the file system back into working shape.

The second command, dpkg --configure -a then attempted to run the post-installation scripts for packages that are marked in the dpkg database as having their files unpacked, but the scripts not run yet. If this command attempted to do anything, this means that you will need to do that later on, but now is not the proper time. The dpkg tool exists all file systems to be mounted and error-free, you only have a root file system with errors, and all others are missing.

The way to resolve your situation is:

1. Go back to read-only mode using mount -o ro,remount /. You do not want the kernel to change anything in the file system while the repair is under way.

2. Repair the root file system, using the fsck utility, which will then use the fsck.ext3 utility internally: fsck -f /.

   You can add the option -C0 to get a progress indicator.

   If you get messages about fsck being unable to read blocks because of I/O errors, you can interrupt with Ctrl-C and add the -c option to scan for bad blocks beforehand. This will take ages, but the repair operation then does not attempt to rescue any files spread over defective sectors.

   Most likely you will be asked if you agree to certain problems being fixed. Look up the error messages using your search engine of choice, there is ample documentation on the Internet. Most of these are about deleting files that are beyond repair, or moving them to the lost+found directory.

3. After that is complete, you will most likely be asked to reboot, in capital letters. This is a good idea, just enter sync first, give the disks a few seconds to write out the remaining data and then press Ctrl-Alt-Del. The reboot will be immediate, without unmounting file systems, but that is fine because the only file system mounted is read-only.

4. If after the reboot you are dropped back into the same prompt, another file system but the root file system is in need of repairs as well. Use the fsck -A command to attempt an automated repair of all non-root file systems, and manually repair those that need it. This time around, you should not be asked to reboot, as this is only needed for file systems that are mounted while being checked.

0

1

Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a- C0 /dev/sda1
/dev/sda1 is mounted.
e2fsck: Cannot continue. aborting.

fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors