Last week my cache pool failed and i had to replace this drive and reinstall all my dockers.

I sent a complaint to Crucial since the drive is still under warranty (less than 2 years old).

They asked to use their Storage Executive software and send them the SMART information (which i attach here).

They came back with this reply:

After reviewing the SMART data, the SSD is currently reporting Good Health with 94% lifetime remaining. Additionally, the drive shows:

• Reallocated NAND Block Count: 0

• Current Pending ECC Count: 0

• SMART Off-line Scan Uncorrectable Errors: 0

• Write Error Rate: 0

While the SMART attribute Reported Uncorrectable Errors shows a value of 1041, this attribute by itself is not generally indicative of a failing SSD. 

Based on the SMART data provided, there is currently no indication that the SSD is experiencing a hardware failure, and the reported error count is not something a concern on its own.

I don't understand how they can say the drive is fine, don't the uncorrectable errors mean something?

I believe the SATA connections were fine since there were no UDMA CRC errors before this. there were no problems after I swapped the replacement drive to the same slot.

Does any one have some experience with this?

Edited Monday at 10:10 AM2 days by limawaken

Not a great sign; I have multiple of those devices, and they don't show any errors there. Did you run an extended SMART test? If that passes, I expect they won't replace it.

but if data is getting corrupted during read/write, then the drive is essentially unusable. will they replace it only if the drive is completely dead due to hardware failure?

they guy is saying that the uncorrectable errors is not of concern but didn't explain what those errors mean. i feel cheated.

Those errors can be intermittent; that is, the data is returned correctly on a retry; otherwise, you should get an i/o error. Devices should never return bad data, unless there's a firmware bug.

thank you, that was good to know. i'll put the drive back in and see if it causes more problems. thanks @JorgeB @whipdancer