- Joined
- May 28, 2011
- Messages
- 10,996
One of my first SSDs was a Crucial M4 that had a firmware issue, it would stop writing after a specific number of power on hours. After power cycling it would work for about 1 hour and then stop working again. During that 1 hour was the only opportunity a user had to upgrade the firmware but early adopters of this drive were doomed for a while until the firmware fix came out. My drive hit that magic number a few weeks after the new firmware was released and when it happened to me I was quite irritated, it was my Windows computer that I did everything on. I thought to myself that SSD's sucked! Thankfully I found the firmware fix and resolved my problem.SSD's dead: 2x Crucial MX500 250GB
My point here is that SSD's do stop working through no fault of our own. Also infant mortality is a very real thing. I think the firmware problem likely was fixed for the MX500 lineup but sometimes quality control isn't what it should be.
I'd think this was infant mortality, bad luck. Of course as @jgreco pointed out, you could have a noisy power supply (meaning electrically noisy).I don't have the exact logs of those, but we are talking about a failed drive after 3-4 weeks being used as a boot pool only drive on a private NAS.
I picked up two of these myself as well from NewEgg, good price and I do have 4 Samsung SSDs (850 Evo and 860 Evo) that have been working well and the Samsung products work well for me.Well, I'd mostly been buying MX500 and WD Blue for hypervisor datastores for the last year or two, but this Black Friday, the 1TB 860 Evo's were going for $100 and that was hard to pass up (pointing to the stack of 18 boxes).
I don't think you really need these devices but it sounds like this is for an office/work place system so spending the money and having the strong warranty will likely make you feel better. If you have more SSD failures then look at the power supply.Maybe I'll just order some brand new Intel Data Center SSD's
As for tracking the SMART data, you could use the script smart_report.sh that @spearfoot has provided to everyone which will send you an email when it is run which contains all the SMART data you need to track a problem like this. Just have that email filtered and saved in a folder for later use. I have customized my version of this for my specific needs and it works great.
Good Luck