860 failing early

ep0x73

2[H]4U
2FA
Joined
Sep 5, 2013
Messages
2,663
the system is in raid 1 so you can't run trim with windows but as I read this drive has it's own garbage collection

this is sata 1 so not the main drive in a sense but the copy drive, seems unusual

I could break up the intel raid and not lose anything and then trim it but not sure what would help, right?
 

Attachments

  • CrystalDiskInfo_20241213012756.png
    CrystalDiskInfo_20241213012756.png
    57.8 KB · Views: 0
The title of the thread says 870 but CDI says 860 EVO. Which is it?

The SSD is in "Raid 1" but you have 5 drives with the same drive letter? Raid 1 is just basic mirroring, so the same 500GB is duplicated on all 5 drives?

Are all of the drives in the Raid 1 array identical drives that were purchased at the same time? If so, how does the SMART info compare on those other drives?

That's a lot of Total Host Writes, especially for an older smaller TLC drive. That drive should theoretically have a write endurance of ~300TB but it can be much less in practice if you are keeping the drive nearly full, which prevents the drive's wear-leveling algorithm from functioning properly. The drive has an SLC and DRAM cache which should also help with endurance in most real-world situations but I don't know how that would be affected due to being part of a Raid 1 array.

I don't think that TRIM is going to help you much now. I'd say that you probably got your money's worth out of what was already a cheap drive to begin with. It's probably best to look for a replacement at this point. You can find some older enterprise-grade drives for pretty cheap on places like eBay, like the Samsung SM863A for example. They are workhorse MLC drives that pretty much last forever no matter how much you use them. I keep one in my system just for random write-heavy tasks that aren't super important, to extend the life of my more expensive SSDs. I have almost 100TB written on one so far and it's still at 98%. As far as that specific 860 EVO that is at 8% goes, it's also important to keep in mind that the reported percentage is just an estimate. It doesn't mean that the drive is guaranteed to fail when it hits 0%. In my experience, most SSDs that I've had fail did so long before they ever got near 0%. If it's not giving you any actual problems yet, it's possible that it could continue to work for a long time.
 
The title of the thread says 870 but CDI says 860 EVO. Which is it?

The SSD is in "Raid 1" but you have 5 drives with the same drive letter? Raid 1 is just basic mirroring, so the same 500GB is duplicated on all 5 drives?

Are all of the drives in the Raid 1 array identical drives that were purchased at the same time? If so, how does the SMART info compare on those other drives?

That's a lot of Total Host Writes, especially for an older smaller TLC drive. That drive should theoretically have a write endurance of ~300TB but it can be much less in practice if you are keeping the drive nearly full, which prevents the drive's wear-leveling algorithm from functioning properly. The drive has an SLC and DRAM cache which should also help with endurance in most real-world situations but I don't know how that would be affected due to being part of a Raid 1 array.

I don't think that TRIM is going to help you much now. I'd say that you probably got your money's worth out of what was already a cheap drive to begin with. It's probably best to look for a replacement at this point. You can find some older enterprise-grade drives for pretty cheap on places like eBay, like the Samsung SM863A for example. They are workhorse MLC drives that pretty much last forever no matter how much you use them. I keep one in my system just for random write-heavy tasks that aren't super important, to extend the life of my more expensive SSDs. I have almost 100TB written on one so far and it's still at 98%. As far as that specific 860 EVO that is at 8% goes, it's also important to keep in mind that the reported percentage is just an estimate. It doesn't mean that the drive is guaranteed to fail when it hits 0%. In my experience, most SSDs that I've had fail did so long before they ever got near 0%. If it's not giving you any actual problems yet, it's possible that it could continue to work for a long time.
I have two in raid1 for C and two spinners for D

I bought a 500 870 to have on hand just in case, it was on sale, around 46 bucks
 
So you cannot manually run the trim command from powershell on that drive? I ask because I have had to do that with a USB connected SSD that Windows refused to optimize automatically.
I tried command prompt it does nothing, it's not available apparently when in a raid array

I will say in raid 1 my reads are over 1000, write slow down to 350 instead of 500 not in raid

if both drives gets the same writes why is my O drive only at 56%, that is what makes no sense
 
Last edited:
Not sure about the 860evo, but I recommend you make sure that 870evo has the most recent firmware (last time I checked, that was version SVT02B6Q) before using it. It is guaranteed to kill itself on older firmware. That model was the first ssd I ever encountered that silently destroyed files, where I only discovered something was wrong when copying of said files started to fail.

Samsung's handling of that defect (no public acknowledgment of the problem at all) put them back on my manure-list of ssd brands.
 
Last edited:
Not sure about the 860evo, but I recommend you make sure that 870evo has the most recent firmware (last time I checked, that was version SVT02B6Q) before using it. It is guaranteed to kill itself on older firmware. That model was the first ssd I ever encountered that silently destroyed files, where I only discovered something was wrong when copying of said files started to fail.

Samsung's handling of that defect (no public acknowledgment of the problem at all) put them back on my manure-list of ssd brands.
thanks for the heads up, I have a 870 on the way, before I install into my raid array I will put it in a USB dock, check the firmware but good chances it is updated to the latest
 
Back
Top