How to Check Bad Sectors or Bad Blocks on Hard Disk in Linux

Let us start by defining a bad sector/block, it’s a section on a disk drive or flash memory that can not be read from or written to anymore, as a result of a fixed physical damage on the disk surface or failed flash memory transistors.

As bad sectors continue to accumulate, they can undesirably or destructively affect your disk drive or flash memory capacity or even lead to a possible hardware failure.

It is also important to note that the presence of bad blocks should alert you to start thinking of getting a new disk drive or simply mark the bad blocks as unusable.

Therefore, in this article, we will go through the necessary steps that can enable you determine the presence or absence of bad sectors on your Linux disk drive or flash memory using certain disk scanning utilities.

That said, below are the methods:

Check Bad Sectors in Linux Disks Using badblocks Tool

A badblocks program enables users to scan a device for bad sectors or blocks. The device can be a hard disk or an external disk drive, represented by a file such as /dev/sdc.

Firstly, use the fdisk command with superuser privileges to display information about all your disk drives or flash memory plus their partitions:

$ sudo fdisk -l
List Linux Filesystem Partitions
List Linux Filesystem Partitions

Then scan your Linux disk drive to check for bad sectors/blocks by typing:

$ sudo badblocks -v /dev/sda10 > badsectors.txt
Scan Hard Disk Bad Sectors in Linux
Scan Hard Disk Bad Sectors in Linux

In the command above, badblocks is scanning device /dev/sda10 (remember to specify your actual device) with the -v enabling it to display details of the operation. In addition, the results of the operation are stored in the file badsectors.txt by means of output redirection.

In case you discover any bad sectors on your disk drive, unmount the disk and instruct the operating system not to write to the reported sectors as follows.

You will need to employ e2fsck (for ext2/ext3/ext4 file systems) or fsck command with the badsectors.txt file and the device file as in the command below.

The -l option tells the command to add the block numbers listed in the file specified by filename (badsectors.txt) to the list of bad blocks.

------------ Specifically for ext2/ext3/ext4 file-systems ------------ 
$ sudo e2fsck -l badsectors.txt /dev/sda10


------------ For other file-systems ------------ 
$ sudo fsck -l badsectors.txt /dev/sda10

Scan Bad Sectors on Linux Disk Using Smartmontools

This method is more reliable and efficient for modern disks (ATA/SATA and SCSI/SAS hard drives and solid-state drives) which ship in with a S.M.A.R.T (Self-Monitoring, Analysis and Reporting Technology) system that helps detect, report and possibly log their health status, so that you can figure out any impending hardware failures.

You can install smartmontools by running the command below:

------------ On Debian/Ubuntu based systems ------------ 
$ sudo apt-get install smartmontools

------------ On RHEL/CentOS based systems ------------ 
$ sudo yum install smartmontools

Once the installation is complete, use smartctl which controls the S.M.A.R.T system integrated into a disk. You can look through its man page or help page as follows:

$ man smartctl
$ smartctl -h

Now execute the smartctrl command and name your specific device as an argument as in the following command, the flag -H or --health is included to display the SMART overall health self-assessment test result.

$ sudo smartctl -H /dev/sda10
Check Linux Hard Disk Health
Check Linux Hard Disk Health

The result above indicates that your hard disk is healthy, and may not experience hardware failures any soon.

For an overview of disk information, use the -a or --all option to print out all SMART information concerning a disk and -x or --xall which displays all SMART and non-SMART information about a disk.

In this tutorial, we covered a very important topic concerning disk drive health diagnostics, you can reach us via the feedback section below to share your thoughts or ask any questions and remember to always stay connected to Tecmint.

If you liked this article, then do subscribe to email alerts for Linux tutorials. If you have any questions or doubts? do ask for help in the comments section.

If You Appreciate What We Do Here On TecMint, You Should Consider:

TecMint is the fastest growing and most trusted community site for any kind of Linux Articles, Guides and Books on the web. Millions of people visit TecMint! to search or browse the thousands of published articles available FREELY to all.

If you like what you are reading, please consider buying us a coffee ( or 2 ) as a token of appreciation.

Support Us

We are thankful for your never ending support.

33 thoughts on “How to Check Bad Sectors or Bad Blocks on Hard Disk in Linux”

  1. Thanks much for the help on this topic. I’m reading at that it’s better to use the -c option of e2fsck, which ensures that the numbering system for the blocks in badsectors.txt is correct, skipping the direct use of badblocks.

    See also the discussion of the -l option on this score. Also, if someone is planning on using a live Linux install DVD in rescue mode then with an unmounted disk I don’t understand how a *.txt file could be referenced (this said by someone who’s never actually really studied Linux or disk drives).

  2. I’ve found smartctl to be pretty much useless. It always says “test passed” on every disk I’ve tried it on, including ones with bad sectors.

  3. e2fsck won’t run on a mounted filesystem, but my disk with bad sectors is the system disk. How can I run e2fsck on the system disk?

    • @Robert,

      First, boot into single-user mode and unmout file system.

      # init 1
      # umount /dev/sda

      Make sure to replace /dev/sda with your disk name.

      Then, run e2fsck command.

      # e2fsck -y /dev/sda
  4. Since my drive is portable, how every OS can identify the bad sector in bad sector.txt file not use again rather than give not use it in a specific OS

    • The badsectors.txt file is only used by e2fsck -l. Once you’ve run e2fsck -l, the bad sectors are marked as such within the filesystem itself, so you no longer need the badsectors.txt file.

  5. Using badblocks this way (manually) can result in problems as the (assumed) block sizes may not match between badblocks and fsck. Better to run the appropriate fsck.ext2/3 tool with the -c option to let it scan by itself and ensure the block size is correct.

    • @Anon

      I presume you have tasted the methods above with SSDs, and may you give us an explanation for your conclusion. That will help us understand better, why you have said so and probably find other ways to deal with bad sectors on SSDs.

  6. So much fail in this article. Modern drives remap bad sectors so the bad blocks command will not detect them. Smartmontools are better but you need to examine individual readings to determine drive health.

    I have a 2 TB that developed about 2500 remapped sectors before drive health changed from good.

    • @HankB

      Good concern here and thanks for letting us know about the behavior of modern disks while detecting bad sectors in relation to badblocks utility, there are two methods offered in the article, a user can employ the two approaches to determine disk health(badblocks for older disks and smartmontools for modern disks as you have explained).

      Again, smartctl which controls S.M.A.R.T system has multiple other options that you can try as per the descriptions in the man page, if you suspect a critical issue with your disk drive, you may probably want to check individual partitions for better diagnostics.

  7. I see the first method is Read Only, to be clear, the second method is a “Passive” (Read Only) Check as well? I would want to minimize unnecessary Read/Writes to an SSD.

    If a bad sector is found, will these methods try ‘testing’ the sector?


    • @Greg

      For the case of badblocks utility you can enable write-mode test to all sectors by using the -w. This option allows badblocks command to scan for bad sectors by writing some patterns such as 0xaa, 0x55, 0xff, 0x00 on every block of the device, reading every sector and comparing the contents.

      However, do not use the -w flag on a disk with an existing file system, you can read more about this warning from the badblocks man page.

      Then, smartctl utility will print out an error or “failed” overall health test result after S.M.A.R.T tests all bad sector to show an imminent hardware failure.


Got something to say? Join the discussion.

Have a question or suggestion? Please leave a comment to start the discussion. Please keep in mind that all comments are moderated and your email address will NOT be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.