Failed to start File System Check on

16,349

Solution 1

My guess for your situation would be that environmental changes have affected you HDD. So from the error message from journalctl -xb which points to file inconsistencies and the instruction to run manual file check. Use the fsck command to correct this error:

fsck /dev/sda2

And simply accept all the options give during the process. Then reboot you system.

Solution 2

Similar to the answer before https://askubuntu.com/a/1095536/676490

In my case helped:

sudo fsck /dev/sda1
sudo fsck /dev/sda2
sudo fsck /dev/sda3
sudo fsck /dev/sda4

And I accepted everthing with y (yes)

If you want to accept all automatically you can use ihmo the -y-flag:

sudo fsck -y /dev/sda4

or simmilar

Share:
16,349

Related videos on Youtube

Pablo
Author by

Pablo

Updated on September 18, 2022

Comments

  • Pablo
    Pablo almost 2 years

    A couple hours ago tried to start my Ubuntu laptop after a few months without using it and I found myself with this:

    When I boot Ubuntu I get up to this screenenter image description here

    I'm far from understanding what's exactly happening here. Does anyone know how to troubleshoot this?

    • George Udosen
      George Udosen over 5 years
      type journalctl -xb and see what it has to say!
    • Pablo
      Pablo over 5 years
      Added a screenshot of the part where it mentions the same error. Does it help?
    • George Udosen
      George Udosen over 5 years
      run this command fsck /dev/sda2 and accept all options
    • George Udosen
      George Udosen over 5 years
      Is it back up ?
    • Pablo
      Pablo over 5 years
      It's working! yes!
    • George Udosen
      George Udosen over 5 years
      Make sure you do an update on your system to bring it up to speed with the latest updates! Cheers!
    • George Udosen
      George Udosen over 5 years
      @wjandrea I have done so!
  • Sashko Lykhenko
    Sashko Lykhenko almost 5 years
    How to find out which sda or sdb is it in my case?
  • George Udosen
    George Udosen almost 5 years
    I think the error message should tell you which it is! @sashkolykhenko
  • Sashko Lykhenko
    Sashko Lykhenko over 4 years
    Well I never found it in the message, I brute-forced through all drives instead :)