You are not logged in.
Pages: 1
I suffered a disk crash (read errors) on a month old 2TB drive last week, and before returning it to the store I figured I should test the drive. I ran a low level format and some tests in Windows and everything to my surprise checked out fine, so I thought I'd run badblocks from my Arch server since that's where the disk is supposed to be used.
I started a destructive write test like this:
badblocks -wsv /dev/sda
It has now been running for almost 35 hours, and it's only 33% into "Testing with pattern 0xaa", which would mean almost 100 hours for one pass, and I think badblocks does 4 different test passes with different patterns.
Is it normal for badblocks to be this slow? I have never run it before; the only thing I have for comparison is the low level format and testing in Windows, and that finished in less than 24 hours.
Offline
Pages: 1