badblocks on a 1TB drive.

I always run badblocks on new drives when I get them, out of paranoia that there’s a chunk of bad disk just waiting to eat my data. Now that drives are starting to get into ludicrous sizes, the amount of time it takes to do this is going up dramatically. I just bought two 1TB drives. It turned out to be slightly cheaper than buying one 2TB drive, but had the other advantage that I could run two badblocks instances in parallel.

I invoke badblocks via mkfs’s -cc command line, which does a destructive read/write of patterns 0xaa, 0x55, 0xff, and 0x00 one 4k sector at a time. So how long does it take ?

Two days, and twenty minutes.

2 thoughts on “badblocks on a 1TB drive.”

  1. I was using badblocks yesterday and cursing the same thing. Why is it so slow BTW? Using `sudo hdparm -t /dev/sda` I get 57MB/s but badblocks was going at about 5MB/s I think?, and that was after I set -b4096.

    1. Not sure what you mean by set -b4096. hdparm always does 1MB reads afaik. Reading/Writing 4k at a time is pretty miserable for throughput. Even on SSDs.

Comments are closed.