How to solve ” fsck error on boot: UNEXPECTED INCONSISTENCY; “

It could happen, as it did to me, that when you open your Virtual box and start your Ubuntu virtual machine, you get the error below :

fsck from util-linux 2.26.2 /dev/sda1 contains a file system with errors, check forced. /dev/sda1: Inodes that were part of a corrupted orphan linked list found.
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck exited with status code 4
The root filesystem on /dev/sda1 requires a manual fsck Busybox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built in shell (ash) Enter ‘help’ for a list of built-in commands. (initramfs) _

How to fix that ?

What you would need to do is already suggested in the error message per se, .i.e. run the command below :

fsck /dev/sda1 -y

(or whatever partition is mentioned in the message)

Then you have to reboot and you should be good to go…

Read: Using fsck to check or repair the file system in Ubuntu

If you like the content, we would appreciate your support by buying us a coffee. Thank you so much for your visit and support.


ziad nahdy

Ziad Nahdy, fan of open source and programming languages. He is a technical writer, blogger and Linux enthusiast. He loves to read and help others with their problems. He is addicted to open source software but he also loves other technology related subjects.

This Post Has 10 Comments

  1. fsck /dev/sda5 -y worked for my ubuntu. Thanks you’re a life saver.

  2. Thanks bro, i fixed my problem. i appreciate you

  3. Thank you Very much, Suas Nahdy!!!
    It worked for me, you saved my notebook!!

  4. Ziad Nahdy*, sorry.

  5. Thanks a lot man!! Much appreciated.

  6. I did the same but whenever I reboot or shutdown my system, it comes up with the same problem.
    Now I have to type in the “fsck /dev/sda* -y” command over and over.
    what should I do?

  7. THX very much (y) I have it on doudoulinux, it’s work great

  8. You guy are a genius 👌

  9. on this error>>> /dev/sda5: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)

    after using this>>> fsck /dev/sda5 -y and fsck -fy /dev/sda5 -y getting error >>> /dev/sda5: clean, 389475/11067392 files, 5656198/44246784 blocks

  10. For me it shows
    Ext2fs_cgeck_desc: corrupt group descriptor: bad block bitmap
    Fsck.ext4:group descriptor look bad… Trying backup blocks

Leave a Reply

Close Menu