Horrible failure of Kingston SSDNow V+200

[LongRunner]

I had a 120GB one of these fail at about 6 years old, which ended up silently corrupting the data.
(Not even S.M.A.R.T. admitted that there was anything wrong with it. )

I don't know how common this is, but I've included them in my product recalls anyway; if you have some, then I strongly recommend replacing them with a good model, as soon as possible (hopefully before it's too late). When you don't need them, they should be destroyed to prevent anyone from re-using them and losing their data.

This leaves me very wary of any SSDs with SandForce controllers in them. (Not that those don't have a bad reputation already.)

[Behemot]

Never seen any drive to wear out yet under normal usage. Maybe in servers being used as cache. What did you do to it?

Samsung 840 Evo were not particularly great either, the cells were loosing charge and needed to be rewritten regularly otherwise the drive would get terribly slow. So Samsung introduced new FW which does that on background, distributing the lost speed to every time you run it

[LongRunner]

It's not me who did anything to it; Windows 7's scheduled defragmentation (which, to be fair, should have been switched off – but that's the builder's job, and they didn't care to) was enough.

I don't doubt that enterprise SSDs are reliable, but these are total junk.

[Behemot]

There is some scheduled defragmentation? Never seen that. Thought it's run manually. I do that only with HDDs, using Vopt.

[LongRunner]

Now the other one's gone bad in the same manner.

Since this type of failure is below the level of the Deathstars, SandForce