I recently got this bad news message trying to boot: /dev/hda11: UNEXPECTED INCONSISTANCY; RUN fsck MANUALLY (i.e. without -a or -p options) I think it would be a good idea if the message told users to run fsck.ext2. fsck doesn't fix anything. The average newbie, home user like myself, needs to experiment around to find the answer, and that is not the best scenario, under the circumstances. BTW: I did manage to fix everything, except for one one file left in /lost+found. br-xr-srwT 1 17957 32545 101, 104 Sep 11 1994 #12601 which looks like it goes in /dev. Any idea of where I could find out what the file name is? Thanks, Eric Bolotin
You can do rpm -V dev to verify the dev package. However, the permissions are goofy enough that it is unlikely that you lost+found file is "real" -- it's an inode that was damaged so the file type and mode happen to be as displayed. There are too many failure modes of a file system to be handled with a better error message. The message that is displayed, while uninformative, is at least constant (i.e. the same as its always been).