Hard Drive "Failed" - Test fine

[Bigzaj]

I have a Samsung F4 2TB Drive that failed in my raid array, I put it back in and all of the "attributes" are fine compared to the "threshold" values set by Areca, additionally it tests fine using HDD test utility on its own.

Should I keep it out of the raid array or is it ok to try and use it again?

 

[koolaidkitten]

long as you have adaquate backup procedure, I would say give it a whirl again.
If possible tho give it a 24 hour test on its own. Give it something to do a lot of read/write access.

 

[Rectal Prolapse]

Could also be a chance that the cable connection is having issues, or that your power supply is having trouble handling the load with that drive included?

 

[drescherjm]

long as you have adaquate backup procedure, I would say give it a whirl again.
If possible tho give it a 24 hour test on its own. Give it something to do a lot of read/write access.

I recommend a linux badblocks destructive (overwrites disk / data) read / write test. That will take around 25 hours for a 2TB F4. Then look at the smart raw data.

 

[s0rce]

If its under warranty why not just send it back and get a new one?

 

[drescherjm]

If its under warranty why not just send it back and get a new one?

I would verify the drive is the problem and not something else. No point wasting the $7 to ship back a good drive.

it back and get a new one?

The thing is you Will most likely not get a new one when you rma a drive. It's absolutely possible that you will get a drive back that is worse than the one you sent out. At work (where we now rma 10 to 20 drives a year - ~ 8% annual failure rate) I have recently had a rma come back DOA.

 

[C7J0yc3]

What I do with RAID drives that fail out of arrays but have no SMART error is to DBAN (or similar wipe) the drive, then run it through HD Tune Pro's health check (basically doing a deep sector inspection for bad sectors). If everything is green after that I put it back in my array and 99/100 times it accepts the drive just fine, and usually the cause of the failed drive was bad metadata.