Using fsck to Find and Repair Disk Errors and Bad Sectors
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
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.
fsckis not installed by default when using Linode’s rescue mode, and instead the
e2fscktool, which fsck functions as a frontend for, will need to be called directly for standard
extfilesystems. 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.
|Attempt to fix errors automatically. Use with caution.|
|Force fsck to check a file system even if it thinks it’s clean.|
|Check all disks listed in |
|Show progress bar (ext2 and ext3 file systems only).|
|Skip mounted file systems.|
|Test run. Describes what would happen without executing the check itself.|
|Use with the |
|If using the |
|Check only a specific type of filesystem.|
|Skip the title on startup.|
|Interactive repair mode.|
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.
dfto view a list of currently mounted disks. If you are using Rescue Mode, the disk you want to check should not be listed:
fdiskto view disk locations:
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.
umountto unmount the disk location copied in the previous step:
If the disk is declared in
/etc/fstab, change the
nonethere as well.
Run fsck on the target disk, using the desired options. This example checks all file systems (
fsck -A /dev/sda
The error codes that fsck returns can be understood with the following table from man7.org:
|Code||Error Code Meaning|
|1||Filesystem errors corrected|
|2||System should be rebooted|
|4||Filesystem errors left uncorrected|
|16||Usage or syntax error|
|32||Checking canceled by user request|
-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.
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.
This page was originally published on