Badblocks: Difference between revisions
| Line 15: | Line 15: | ||
To save the list of bad blocks, you need to run <code>e2fsck</code> or <code>mkfs.ext4</code>: | To save the list of bad blocks, you need to run <code>e2fsck</code> or <code>mkfs.ext4</code>: | ||
<pre> | |||
sudo e2fsck -fcck /dev/device | |||
</pre> | |||
* <code>-f</code> force check | |||
* <code>-cc</code> non-destructive write test | |||
* <code>-k</code> add bad blocks to bad blocks list | |||
<pre> | |||
mkfs.ext4 -cc /dev/device | |||
</pre> | |||
==Resources== | ==Resources== | ||
* [[Archwiki: Badblocks]] | * [[Archwiki: Badblocks]] | ||
Revision as of 01:20, 4 July 2020
Badblocks is a tool for detecting bad blocks in your hard disk.
Usage
The following will write to every block and read back to identify the number of bad blocks.
This is a destructive test.
badblocks -wsv -b 4096 /dev/sdg
-wdo a destructive write test-sshow progress-vverbose-b numblock size. Use 4096 typically.-p numdo num iterations. Typically 1 is sufficient.-t test_patternTest pattern. Select from [random,
To save the list of bad blocks, you need to run e2fsck or mkfs.ext4:
sudo e2fsck -fcck /dev/device
-fforce check-ccnon-destructive write test-kadd bad blocks to bad blocks list
mkfs.ext4 -cc /dev/device