On Wed, 25 Jun 2008 10:22:55 +0200, Dave Plater wrote:
If you can see the display of blocks processed and 244,140,625 (1000,000,000,000 / 4096) is the approximate total number of blocks, if you take the time taken so far divided by number of blocks processed times 244140625 you will have the estimated total time. Just subtract time taken so far and you have time to completion.
Now I'm wondering why I didn't think of that. D'oh! And thanks. :-)
If you saved the badblocks list to a file using the -o filename option you can input it to fsck.reiserfs, read man fsck.reiserfs for more info.
Yep, that's my intention.
If smart is disabled on the drives and data was static for a long time you may be able to recover the sectors by doing a few zero write passes but this will take a long time. Its a good idea to run a western digital disk utility on the drives. The biggest cause of bad sectors is data that is static for a long period of time. Regards Dave P
SMART doesn't seem to work over USB, but the data has been relatively static. When you say "zero write passes", is that an option to fsck or badblocks? Is there a Linux-based WD disk utility, or is it a boot diskette (or maybe the utility CD that came with the drive, I'll have to see if I still have that)? Assume I can get that from WD. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org