How to Use the Linux badblocks Command to Scan for Disk Errors

When a Linux server begins to experience sudden I/O errors, kernel panics, or corrupted database tables, the most likely culprit is physical degradation of the storage media. As hard disk drives (HDDs) age, their magnetic platters develop microscopic imperfections, and solid-state drives (SSDs) burn out their flash memory cells. To mathematically scan a block device and forcefully identify these failing sectors before catastrophic data loss occurs, Linux system administrators rely on the badblocks command.

Why Use the badblocks Command?

While SMART monitoring (via smartctl) provides a high-level overview of a drive’s health, it relies on the drive’s internal firmware reporting. The firmware can sometimes lie or fail to report hidden damage. The badblocks command mathematically bypasses the firmware. It interacts directly with the raw block device, systematically attempting to read (and optionally write) mathematical patterns to every single sector on the disk. If a sector fails to return the expected data, badblocks definitively proves physical degradation.

Step 1: Perform a Non-Destructive Read-Only Scan

Because the utility interacts with raw block devices, you must execute it with root privileges using sudo. A read-only scan is completely safe to perform on drives containing active data.

1. Open your Linux terminal.
2. Identify the target drive using lsblk (e.g., /dev/sdb).
3. Execute the basic read-only scan, adding the -v (verbose) flag so you can monitor its mathematical progress:

sudo badblocks -v /dev/sdb

1. Press Enter. The command will begin systematically reading every block. If it encounters a failure, it will print the exact mathematical block number to the terminal.

Step 2: Output Findings to a File for Filesystem Repair

If the scan discovers damaged sectors, you must instruct the Linux filesystem (like Ext4) to never attempt to write data to those specific mathematical coordinates again.

1. Use the -o (output) flag to generate a text file containing the corrupted block numbers:

sudo badblocks -v -o /tmp/badblocks.txt /dev/sdb

1. Once the scan finishes, you can mathematically feed this text file directly into the e2fsck (filesystem check) utility:

sudo e2fsck -l /tmp/badblocks.txt /dev/sdb1

The kernel will instantly blacklist those sectors, preventing future data corruption.

Step 3: Perform a Destructive Write-Mode Scan (WARNING)

If you are decommissioning an old drive or testing a brand-new drive before deploying it to production, you can perform a highly aggressive, destructive scan. This will mathematically erase every single piece of data on the disk.

1. Use the -w (write) flag:

sudo badblocks -w -v /dev/sdb

This command performs a mathematical stress test. It writes four distinct byte patterns (0xaa, 0x55, 0xff, and 0x00) to every single sector, and then reads them back to verify absolute data retention integrity. If the drive survives this test without throwing errors, it is safe for production use.

By integrating the badblocks command into their maintenance toolkit, Linux administrators can mathematically detect physical hardware failure long before it causes a catastrophic server crash.