tldr/pages/common/badblocks.md

30 lines
925 B
Markdown
Raw Normal View History

2017-06-11 14:30:40 +01:00
# badblocks
> Search a device for bad blocks.
2021-03-31 11:13:06 +01:00
> Some usages of badblocks can cause destructive actions, such as erasing all data on a disk, including the partition table.
> More information: <https://manned.org/badblocks>.
2017-06-11 14:30:40 +01:00
- Search a disk for bad blocks by using a non-destructive read-only test:
`sudo badblocks {{/dev/sdX}}`
2017-06-11 14:30:40 +01:00
- Search an unmounted disk for bad blocks with a [n]on-destructive read-write test:
2017-06-11 14:30:40 +01:00
`sudo badblocks -n {{/dev/sdX}}`
2017-06-11 14:30:40 +01:00
- Search an unmounted disk for bad blocks with a destructive [w]rite test:
2017-06-11 14:30:40 +01:00
`sudo badblocks -w {{/dev/sdX}}`
- Use the destructive [w]rite test and [s]how [v]erbose progress:
`sudo badblocks -svw {{/dev/sdX}}`
- In destructive mode, [o]utput found blocks to a file:
`sudo badblocks -o {{path/to/file}} -w {{/dev/sdX}}`
- Use the destructive mode with improved speed using 4K [b]lock size and 64K block [c]ount:
`sudo badblocks -w -b {{4096}} -c {{65536}} {{/dev/sdX}}`