How to set up automatic filesystem checks and repair on Linux

One of the most important tasks in Linux administration is to check the integrity of the filesystem. The Linux filesystem can be damaged under various circumstances, e.g., system crash, power loss, disconnected disk, accidentally overwritten i-node, etc. Thus it is a good idea to check the integrity of the filesystem regularly to minimize the risk of filesystem corruption. When it comes to checking and repairing Linux filesystem, fsck is a useful tool.

In this tutorial, I am going to describe how to set up automatic filesystem checks with fsck tool.

Trigger Automatic Filesystem Check upon Boot

If you want to trigger fsck automatically upon boot, there are distro-specific ways to set up unattended fschk during boot time.

On Debian, Ubuntu or Linux Mint, edit /etc/default/rcS as follows.

$ sudo vi /etc/default/rcS
# automatically repair filesystems with inconsistencies during boot

On CentOS, edit /etc/sysconfig/autofsck (or create it if it doesn't exist) with the following content.

$ sudo vi /etc/sysconfig/autofsck

Force Regular Filesystem Checks

If the filesystem is large, you can force filesystem checks on a regular basis, instead of every boot time. In order to do so, first find out the filesystem configuration with tune2fs command. The following command line shows the current values of filesystem related parameters. Note that /dev/sda1 is the partition where the filesystem superblock is located.

$ sudo tune2fs -l /dev/sda1

From tune2fs output, you can see not only the filesystem state (clean or not), but also parameters that are related to filesystem checks. "Maximum mount count" parameter is the number of mounts after which the filesystem check gets triggered. "Check interval" parameter shows the maximum time between two filesystem checks. On most Linux distros, these parameters are not set by default, meaning no regular filesystem checks are occurring.

To force filesystem check for every 30 mounts, run the following command.

$ sudo tune2fs -c 30 /dev/sda1

To force filesystem check for every 3 months, use the command below.

$ sudo tune2fs -i 3m /dev/sda1

Now verify that newly added filesystem check conditions are set properly.

$ sudo tune2fs -l /dev/sda1
. . .
Last mount time:          n/a
Last write time:          Fri Mar 14 22:29:24 2014
Mount count:              20
Maximum mount count:      30
Last checked:             Mon Mar  3 20:55:08 2014
Check interval:           7776000 (3 months)
Next check after:         Sun Jun  1 21:55:08 2014

Force One-Time Filesystem Check on the Next Reboot

If you want to trigger one-time filesystem check on your next reboot, you can use this command.

$ sudo touch /forcefsck

Once you create an empty file named forcefsck in the top directory (/) like above, it will force filesystem check the next time you boot up. After successful booting, /forcefsck will automatically be removed.

Subscribe to Xmodulo

Do you want to receive Linux FAQs, detailed tutorials and tips published at Xmodulo? Enter your email address below, and we will deliver our Linux posts straight to your email box, for free. Delivery powered by Google Feedburner.

Support Xmodulo

Did you find this tutorial helpful? Then please be generous and support Xmodulo!

The following two tabs change content below.
Dan Nanni is the founder and also a regular contributor of He is a Linux/FOSS enthusiast who loves to get his hands dirty with his Linux box. He likes to procrastinate when he is supposed to be busy and productive. When he is otherwise free, he likes to watch movies and shop for the coolest gadgets.

8 thoughts on “How to set up automatic filesystem checks and repair on Linux

  1. You seem to assume an ext* filesystem. Maybe that should be made clear before people try this on btrfs/xfs, etc...

  2. Thanks you SO much for this!...I am in the midst of helping some family members "crossover" from Windows to Linux (their beloved XP is finally giving up the ghost!) and I'm going with Linux Mint (XFCE) so to have this process happening without my intervention (or their!) will be AWESOME! (now all I have to do is setup a way for the updates to happen automatically...)

  3. Actually, it's very different between FSCKFIX=yes (debian) and AUTOFSCK_DEF_CHECK=yes (redhat). FSCKFIX=yes doesn't trigger automatic filesystem check on boot, it just attempts to fix all the errors automatically if fsck is triggered. While AUTOFSCK_DEF_CHECK=yes does trigger filesystem check on boot, and automatically fix errors since '-a' is append in fsck options.(/etc/rc.sysinit)

  4. That's great, do you happen to know how to make it approve all errors when it runs a FSCK?

    When my system does the check on reboot is asks for a root password and then I have to run FSCK from there.

    I would like it to run the file systems check at boot automatically and approve all repairs then boot up.


  5. For later Fedora and CentOS running dracut, you are now supposed to augment the kernel command line with fsck.mode=force. For now, /forcefsck still works, but you'll get this message:
    Jan 31 19:40:45 systemd-fsck[427]: Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck
    Jan 31 19:40:45 systemd-fsck[428]: Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck

  6. Slightly tangential but this is the most relevant page I've found so far. Is there a way to prevent fsck checks on OS X on disk connection?

Leave a comment

Your email address will not be published. Required fields are marked *