WD30EFRX bad sector warning but it's gone after using badblocks on linux

Hello,

I have a bit of doubts about this one.

I recently RMA’d a drive that had a lot of bad sectors. After receiving the recertified one, i used it to switch another failing hdd on my NAS.

The thing is, the HDD had a current pending sector. I did all smart tests and always gave me an error.

Since i use a linux box for testing (like i did with the previous hdd) i used badblocks to scan for bads.

I noticed that the raw read error was 8 at the time.

After badblocks the drive doesn’t show any reallocated or current pending sectors but the raw read error is now at 10.

My doubt is, is this disk still fine or can i RMA the drive before it fails ? Just think it was weird that 2 drives, almost at the same time, had issues. 1 doesn’t have any errors anymore and the other was full of bads.

I’m currently running a long test with WD Diag to check for more information.

1 Like

Hi sk3,

I would suggest to run Quick Test using Data Lifeguard Diagnostic Tool to diagnose the health of the WD internal hard drives. If it fails, you can contact WD Support to get replacement under warranty period.

Hello,

Well before i used Lifeguard any Short/Quick test would flag as bad. I then used badblocks, did extended Test from Lifeguard + write zeros on the drive.

The drive always comes out clean and the Raw Read Error stays at 10. My doubt is if the hdd will be stable enough as a backup drive.