"unexpected inconsistency" (fsck) of the root file system failed
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
"unexpected inconsistency" (fsck) of the root file system failed
Whilst starting my computer during the file check an unexpected inconsistency occurred. It tells me fsck died with exit status 4.
Checking drive/dev/sdal: 93% (stage 4/5, 55/150)
It says a manual fsck must be performed then rebooted. I have NO idea how to perform the required action.
I have never ran this command before and I do not know what to advise you on; but I did find these 2 article's that will help you to understand and know what fsck and some of the details are about.
Different distros need different detailed instructions, although in this case they largely boil down to the equiv of insert 'rescue' disk (centos = install media), boot from that and do a fsck from there, then remove 'rescue disk' and reboot.
That's a definite possibility; could also be the disk going bad.
Of course a power spike/drop could have the same effect... having a UPS isn't always about keeping the system up, a good one also 'cleans' the incoming power.
After every x mounts, a disk will be fsck'ed anyway.
This situation calls for an 'offline' fsck by the sounds of it. In fact, if its the root disk, you can't do it online for obvious reasons
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.