Bad Sectors: western digital caviar black 1tb
Posted 21 February 2011 - 04:38 AM
I bought a couple of western digital caviar black 1tb drives last december after reading the Leaderboard on this site and the drive I used for my main data storage is giving me problems.
You can see all the files within Windows7 but accessing them is painfully slow, some files copy across to another drive ok while other are painfully slow or dont copy at all.
I've run chkdsk /r and it stalls at 43% on pass 4/5 so I'm guessing bad sectors. Is there any software which will help fix my drive without losing data? Dont realy want to low level format as I need some of the files.
Also do you know of a good disc image software which will be able to access the drive?
Posted 21 February 2011 - 07:58 AM
Go ahead and run WD Diags against each drive, full test, and see what you get and psot back.
Twitter - @StorageReview
Posted 21 February 2011 - 11:36 AM
Posted 21 February 2011 - 11:46 AM
My thought process would follow something like this:
Use Linux live CD, check drive SMART status log using smartmontools
If drive is borked, try mounting read-only and copy data off
Once data is off, send in for drive exchange
Chances are you got a drive with a small defect. Happens to the best of them. Hopefully you can still recover the data on the drive.
Posted 21 February 2011 - 04:01 PM
If you follow TSullivan's advice (backup and test) and smartmon shows you where the bad sector is:
(smartctl -t long /dev/sdX ; wait ; smartctl -a /dev/sdX)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 36932 387700232
You could try to fix it yourself:
# force realloc dd if=/dev/zero of=/dev/sdX seek=387700232 bs=512 count=1 oflag=direct # test dd if=/dev/zero of=/dev/sdX seek=387700232 bs=512 count=1
If you suspect there's more than one bad sector and/or don't want to deal with this type of process, but have all your data backed up, just boot up wddiag and do a long test (which should run a short test first). If it finds and corrects any errors, you should probably run another long test to verify all is well.
I use wddiag (and similar utils) alot at work. Some drives keep chuggin' along without issue after that, others bite the dust after initially looking ok.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users