• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Need advice about possibly defective HDD

What to do? What to do?

  • Just use the drive, you're probably gonna be okay

    Votes: 0 0.0%
  • Use the drive, but keep a close eye on it

    Votes: 0 0.0%
  • Get a warranty replacement if possible

    Votes: 2 100.0%
  • Latrine!

    Votes: 0 0.0%

  • Total voters
    2
  • Poll closed .

68k2x86

n00b
Joined
Dec 15, 2011
Messages
3
After buying a 4TB WD HD, I captured the SMART stats, ran badblocks (4 passes, read + write), and noted the SMART stats again, looking out for reallocated sectors.

I didn't get any reallocated sectors, but I did get 6 raw read errors and badblocks reported 4 bad blocks during the first pass.

I have seen mentioned that read errors can be caused by such things as electrical interference with SATA cables, so are these errors likely transient, or should I try to get a replacement (I think it has a 3 year warranty)?

11c42o3.png


2ik7ewk.png


33bmh6t.png
 
When I get any problems in badblocks I then use the -p2 option to make sure it completes 2 entire runs of the 4 tests before I call it okay. If I see any more failure I always RMA the drive (well except for the firmware bug that I found on 2TB Samsung f4 drives a few years back).
 
Try to run an extended smart test, if that fails too I'll definitely request a warranty replacement.

> smartctl -t long /dev/<>
 
Try to run an extended smart test, if that fails too I'll definitely request a warranty replacement.

> smartctl -t long /dev/<>

I actually did but since it came up clean I didn't include it in the original post. Does this change your recommendation?

2niutsz.png
 
When I get any problems in badblocks I then use the -p2 option to make sure it completes 2 entire runs of the 4 tests before I call it okay. If I see any more failure I always RMA the drive (well except for the firmware bug that I found on 2TB Samsung f4 drives a few years back).

In other words, I should run bad blocks again, with an additional 8 passes, and if all is well, keep the drive?
 
Back
Top