Using fsck to Find and Repair Disk Errors and Bad Sectors

This guide is part of a series on Linux commands and features. Not all commands may be relevant to Linode-specific hardware, and are included here to provide an easy to access reference for the Linux community. If you have a command or troubleshooting tip that would help others, please submit a pull request or comment.

fsck, short for file system consistency check, is a utility that examines the file system for errors and attempts to repair them if possible. It functions as a frontend utility for a combination of built-in tools to check the disk and generates a report of its findings.

On some systems, fsck runs automatically after an unclean shutdown or after a certain number of reboots.

Note

fsck is not installed by default when using Linode’s rescue mode, and instead the e2fsck tool, which fsck functions as a frontend for, will need to be called directly for standard ext filesystems. Please see our Troubleshooting Guide: Booting into Rescue Mode for guidance.

Use fsck to check your file system if your system fails to boot, if files on a specific disk become corrupt, or if an attached drive does not act as expected. Unmount the disks you intend to work on before attempting to check or repair them.

Caution

Unmount the target disk first. You risk corrupting your file system and losing data if you run fsck on an active disk.

If you are using fsck on a Linode, the easiest and safest way to unmount your disk is to use Rescue Mode. Visit our Rescue and Rebuild guide for instructions on how to boot your Linode into Rescue Mode. If you’re working on a local machine, consider using the distribution’s recovery mode or a live distribution to avoid working on a mounted disk. fsck should be run only as a user with root permissions.

1. Run df to view a list of currently mounted disks. If you are using Rescue Mode, the disk you want to check should not be listed:

   df -h
   

2. Use fdisk to view disk locations:

   fdisk -l
   

   Copy the location of the target disk to use with the fsck command.

If you are working on a Linode but do not wish to use Rescue Mode, shut down the Linode from the Linode Manager. Unmount the disk from the Configuration Profile. Apply the changes and reboot the Linode.

If you are working on a local machine, unmount the disk manually.

1. Use umount to unmount the disk location copied in the previous step:

   umount /dev/sda
   

2. If the disk is declared in /etc/fstab, change the mount point to none there as well.

Run fsck on the target disk, using the desired options. This example checks all file systems (-A) on /dev/sda:

fsck -A /dev/sda

The error codes that fsck returns can be understood with the following table from man7.org:

Use the -r option to use the interactive repair option.

This example uses fsck to check all file systems except the root, and will attempt repair using the interactive feature:

fsck -AR -y

To check and attempt to repair any errors on /dev/sda, use this format:

fsck -y /dev/sda

If fsck gets interrupted, it will complete any checks in process, but will not attempt to repair any errors it finds.

More Information

You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.

• fsck on man7.org