Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Here's the message I get:
------------------------------------------------------------------------------
Checking root file system
/ contains a file system with errors, check forced
/:
Inode 3329 has image flag set
/:UNEXPECTED INCONSISTENCY:
Run fsck manually,
(i.e. without -a or -p options)
***An error ocurred during the file system check
***Dropping you to a shell: The system will reboot
***when you leave the shell.
Give root password for maintenance or type control-D for normal startup.
---------------------------------------------------------------------------------
Using Control-D results in returning to the same message
Using fsck results in repeated instances of a mesage that says something like
Repair file system #1
Then, if I type fsck, I get the same message, incremented by 1.
i.e., Repair file system #2
This goes on and on and on, with no diagnostic help.
I repeated this fsck loop 100 times and gave up.
The only thing I did just before I shutdown last time was to download imwheel (a mousewheel module), ./configure, make, make install.
What's going on?
From one of my references, I found that the following command will cause the system to check everything manually: fsck -A -V ; echo == $? ==
This command starts an interactive operation that might proceed because it can ask you questions.
The "== $? ==" command is to unambiuously interpert the outcom of the fsck operation. If the value printed between the equal signs (on the output caused by the command) is less than "4", all is well. If the value is more, you have more work to do.
Values are:
0 No errors
1 Filesystem errors corrected
2 System should be rebooted
4 Filesystem errors left uncorrected
8 Operational error
16 Usage syntax error
128 Shared library error.
Originally posted by rdaves@earthlink.net From one of my references, I found that the following command will cause the system to check everything manually: fsck -A -V ; echo == $? ==
This command starts an interactive operation that might proceed because it can ask you questions.
The "== $? ==" command is to unambiuously interpert the outcom of the fsck operation. If the value printed between the equal signs (on the output caused by the command) is less than "4", all is well. If the value is more, you have more work to do.
Values are:
0 No errors
1 Filesystem errors corrected
2 System should be rebooted
4 Filesystem errors left uncorrected
8 Operational error
16 Usage syntax error
128 Shared library error.
Good thing U found the answer as I was clueless 'til now.
THe big question is WHY you got the errors on your root fs.
Don't know what I did to cause the problem. This has happened to me once before, however, I forgot how to fix it until I retraced my steps. I don't understand why Linux isn't able to fix the problem, as all I do is answer "Y" to a whole bunch of questions and I'm fixed. At least these two times, I am fixed.
Thanks
I had a similar experience however I got out of the loop by giving:
I rebooted followed the instructions on the screen typed fsck.ext2 /dev/hdh3 and answered yes to all the questions i didnt understand, rebooted using Ctrl D and Whew! the Linux screen pop back up....
When this happened to me, I had found my screen saver frozen (some kind of rainbow spiral figure) on my monitor. System would accept no input from the keyboard or mouse. After cold-booting I got the message above and had the same experience answering "fsck" to each prompt. Of course all my wind'ohs-using buddies thought it was a hoot. I look forward to trying the solution. Thanks
I've had good and bad experiences with fsck. I've done the same thing several times and it left my Linux unuseable. However, most of the time, I notice no change after the mishap after fsck does its thing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.