Filesystems are responsible for organizing how data is stored and recovered. One way or another, with time, the filesystem may become corrupted and certain parts of it may not be accessible. If your filesystem develops such inconsistency it is recommended to verify its integrity.


This can be completed via a system utility called fsck (file system consistency check). This check can be done automatically during boot time or ran manually.


In this article, we are going to review the fsck utility and its usage to help you repair disk errors.


When to Use fsck in Linux


There are different scenarios when you will want to run fsck. Here are few examples:


The system fails to boot.

Files on the system become corrupt (often you may see input/output error).

Attached drive (including flash drives/SD cards) is not working as expected.


fsck Available options


Fsck command needs to be run with superuser privileges or root. You can use it with different arguments. Their usage depend on your specific case. Below you will see some of the more important options:

-A – Used for checking all filesystems. The list is taken from /etc/fstab.

-C – Show progress bar.

-l – Locks the device to guarantee no other program will try to use the partition during the check.

-M – Do not check mounted filesystems.

-N – Only show what would be done – no actual changes are made.

-P – If you want to check filesystems in parallel, including root.

-R – Do not check root filesystem. This is useful only with ‘-A‘.

-r – Provide statistics for each device that is being checked.

-T – Does not show the title.

-t – Exclusively specify the filesystem types to be checked. Types can be comma separated list.

-V – Provide description what is being done.


How to Run fsck to Repair Linux File System Errors


In order to run fsck, you will need to ensure that the partition you are going to check is not mounted. For the purpose of this article, I will use my second drive /dev/sdb mounted in /mnt.


Here is what happens if I try to run fsck when the partition is mounted.

# fsck /dev/sdb


To avoid this unmount the partition using.

# umount /dev/sdb


Then fsck can be safely ran with.

# fsck /dev/sdb


Understanding fsck exit codes


After running fsck, it will return an exit code. These cods can be seen in fsck’s manual by running:

# man fsck


0      No errors
1      Filesystem errors corrected
2      System should be rebooted
4      Filesystem errors left uncorrected
8      Operational error
16     Usage or syntax error
32     Checking canceled by user request
128    Shared-library error   


Repair Linux Filesystem Errors


Sometimes more than one error can be found on a filesystem. In such cases you may want fsck to automatically attempt to correct the errors. This can be done with:

# fsck -y /dev/sdb


The -y flag, automatically “yes” to any prompts from fsck to correct an error.


Similarly, you can ran the same on all filesystems (without root):

$ fsck -AR -y 


How to Run fsck on Linux Root Partition


In some cases, you may need to run fsck on the root partition of your system. Since you cannot run fsck while the partition is mounted, you can try one of these options:

  • Force fsck upon system boot
  • Run fsck in rescue mode


We will review both situations.


Force fsck Upon System Boot


This is relatively easy to complete, the only thing you need to do is create a file called forcefsck in the root partition of your system. Use the following command:

# touch /forcefsck


Then you can simply force or schedule a reboot of your system. During the next bootup, the fsck will be performed. If downtime is critical, it is recommended to plan this carefully, since if there are many used inodes on your system, fsck may take some extra time.


After your system boots, check if the file still exists:

# ls /forcefsck


If it does, you may want to remove it in order to avoid fsck on every system boot.


Run fsck in Rescue Mode


Running fsck in rescue mode requires few more steps. First prepare your system for reboot. Stop any critical services like MySQL/MariaDB etc and then type.

# reboot


During the boot, hold down the shift key so that the grub menu is shown. Select the “Advanced options”.


Then choose “Recovery mode”.


In the next menu select “fsck”.


You will be asked if you wish to have your / filesystem remounted. Select “yes”.


You should see something similar to this.


You can then resume to normal boot, by selecting “Resume”.


Was this answer helpful? 0 Users Found This Useful (0 Votes)