29
10
I'm running badblocks (or rather "e2fsck -c") on a 1TB drive and if the progress indicator is any indication (no pun intended), it's going to take almost forever to complete.
Right now it says 0.01% done, 30:20 elapsed
which would mean the thing would take 17 weeks or so to complete, which seems rather excessive in my book.
Is that a normal amount of time for such a check to take or it simply that my suspicions are correct in that the drive is failing, thus causing the check to take only slightly shorter than eternity?
I found this question here, but that pertains to the amount of passes done.
In addition to Zoredache's comment above, different switches to
badblocks
cause it to perform different tasks, which will also affect runtimes, for example the-w
switch. – JeffG – 2011-03-07T17:58:46.003Note that the -w option involves the complete removal of the unit, so its use should be avoided in every unit containing useful information for the user. – None – 2014-12-18T00:22:49.730
2It almost certainly depends on the interface, the drive, and how bad the drive is, if there is actually any failures. I can tell you on one of my computers a badblocks scan took ~70 hours for a 1.5TB drive attached through SATA. If you where connected via USB2.0, or 1.0 it would be far longer. – Zoredache – 2011-02-02T00:38:21.890
It is attached using e-SATA. I suppose I'll just give it a while and see how far along it is after a good night's sleep. – Steven Don – 2011-02-02T00:43:05.537
@Zoredache - I think your comment should be an answer instead. – Nifle – 2011-02-02T06:02:14.063
1The time required would (also) depend on the mode
badblocks
is running in: read-only, non-destructive read-write or destructive read-write. Having said that, 30 minutes for 0.1% does seem long. – SabreWolfy – 2012-06-22T14:10:40.257That's 30 minutes for 0.01%, not 0.1%. Anyway, the question is rather old. The drive had indeed failed (spectacularly). – Steven Don – 2012-06-27T09:28:43.153