Difference between revisions of "Badblocks"

From ArchWiki
Jump to: navigation, search
m (Have File System Incorporate Bad Sectors)
m (Have File System Incorporate Bad Sectors)
Line 56: Line 56:
Then re-create the file system with the information:
Then re-create the file system with the information:
  mkfs.<your-past-filesystem> -l badblocks.txt /dev/<device-PARTITION>
  mkfs.<filesystem-type> -l badblocks.txt /dev/<device-PARTITION>

Revision as of 18:07, 16 November 2011


This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

badblocks is a program to test for bad blocks (commonly known as sectors) on a storage device. A sector is a subdivision of a track on storage device and sectors that have become bad cannot be used because they have become permanently damaged (a bad sector can change a letter in a text file to causing a binary program to have a segmentation fault).

Storage Device Fidelity

Although there is no firm rule has been set, it is common thinking that a new drive should have zero bad sectors. Over time, bad sectors will develop on a storage device and although they are able to be defined to the file system so that they are avoided, continual use of the drive will usually result in additional bad sectors forming and are usually the harbinger of death of a hard drive. Replacement of the device is recommended.

Comparisons with Other Programs

Typical recommended practice for testing a storage device for bad sectors is to use the manufacturer's testing program. Most manufacturers have programs that do this. The main reasoning for this is that manufacturers usually have their standards built into the test programs that will tell you if the drive needs to be replaced or not. The caveat here being is that some manufacturers testing programs do not print full test results and allow a certain number of bad sectors saying only if they pass or not. Manufacturer programs, however, are generally quicker than badblocks sometimes a fair amount so.

Testing for Bad Sectors

To test for bad sectors the program badblocks is used in Linux. badblocks had several different modes to be able to detect bad sectors.

read-write Test

This test is primarily for testing new drives and is a read-write(only) test - it will destroy any data on the device. It is an extensive four-pass test that on some devices will take a couple days to complete.

badblocks -wsv /dev/<device>

The -w option tells badblocks to do a write test; the -s option tells badblocks to show its progress; and the -v option tells badblocks to be verbose and output the bad sectors it has detected.

read-write Test (non-destructive)

This test is designed for devices with data already on them. A non-destructive test writes a random pattern to a sector, reads the sector to verify the write, and then writes what was on the original sector. This is a single pass test and is useful as a general maintenance test.

badblocks -nsv /dev/<device>

The -n option signifies a non-destructive test.

Have File System Incorporate Bad Sectors

The easiest way would be to have the filesystem check utility (fsck) use badblocks during its check.

To do a read-write (non-destructive) test and have the bad sectors made known to the filesystem run:

fsck -vcc /dev/<device-PARTITION>

The -cc option tells run fsck in non-destructive test mode and -v tells fsck to show its output.

To do a read-only test (not recommended):

fsck -vc /dev/<device-PARTITION>

Alternately, this can be done at filesystem creation time by first finding the file systems block size. For example for ext# filesystems:

dumpe2fs /dev/<device-PARTITION> | grep 'Block size'

feed this to badblocks and save its output:

badblocks -b <block size> -ns -o badblocks.txt /dev/<device-PARTITION>

Then re-create the file system with the information:

mkfs.<filesystem-type> -l badblocks.txt /dev/<device-PARTITION>