Mailinglist Archive: opensuse (3625 mails)

< Previous Next >
Re: [opensuse] badblocks question
  • From: Dave Plater <davejplater@xxxxxxxxx>
  • Date: Wed, 25 Jun 2008 10:22:55 +0200
  • Message-id: <4862005F.90408@xxxxxxxxx>
Jim Henderson wrote:
Got a drive that's starting to show its age (sadly, at only about 2 years old!). It's a Maxtor OneTouch drive, which actually contains 2 500 GB drives and presents via USB as a single storage device.

I started running badblocks on it a couple days ago, and it's still running. Only 61 bad blocks so far, which is good (4K blocks, reiserfs filesystem).

Just wondering how long I should expect it to take - is there anything to help one calculate the run time?

I'm doing the read-only test (since there's data on the drive). Command used is:

badblocks -b 4096 -n -o bb.txt /dev/sdb1



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.
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.
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.
Dave P
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups