What is wrong with this disk, smart report included.

[dikkiedirk]

Can this disk be trusted? Or does it need to be replaced immediately?

Or should a disk with pending sectors be replaced first?

 

I just finished a parity check on a server with this disk finding 0 errors.

smartsdb.zip

[SSD]

This disk has 32 reallocated sectors. This is not, in and of itself, a problem.

 

It also appears to have had a cabling problem roughly 6,000 power on hours ago. I am assuming that whatever that problem was it was long since fixed.

 

Getting back to the reallocated sectors - each disk has a reserve of spare sectors. If some sectors fail, the drive maps in (reallocates) some spare sectors for the bad sectors, putting the bad sectors out of service. So your disk did what is was supposed to do with the 32 bad sectors it found.

 

Problem is, it is rather common that once sectors start to fail, more sectors follow. So you might find that the 32 reallocated sectors start to grow and grow and grow, and the next thing you have 2000 of them and your drive is running out of spare sectors.

 

To determine if the 32 will hold steady, you need to exercise the drive. If it is in the array you can run parity checks. If not, you can run preclear cycles. If after 3 parity checks or 2 preclear cycles, the 32 has not increased, you can trust the disk. But if each cycle is showing more current or pending sectors, the drive is deteriorating and should not be used in your array.

[dikkiedirk]

Thanks. I will take care of it. Where do you see it had a cabling problem 6000 hours ago?

 

I have a 2 TB that finishes preclearing soon. I can use it to replace this one and then run a couple of preclear runs on it.

 

I hope there will be no dramatic changes.

[SSD]

So your drive has 6987 power on hours on it.

 

  9 Power_On_Hours          0x0012  100  100  000    Old_age  Always      -      6987

 

And the latest ATA error occured when there were 885 hours on it.

Error 1185 occurred at disk power-on lifetime: 885 hours (36 days + 21 hours)

  When the command that caused the error occurred, the device was active or idle.

 

The ATA errors are normally signs of a cabling / connection problem to the drive.

 

That was over 6000 power on hours ago.

[dikkiedirk]

OK, thanks for the clarification.

 

Learning all the time.