HIGH QUALITY, HARD TO GET AND CUSTOM ELECTROLYTIC CAPACITORS FOR POWER SUPPLIES, DISPLAYS, TVs, MOTHERBOARDS AND MORE!

Horrible failure of Kingston SSDNow V+200

Discuss or get help with HDDs here. And yes, SSDs go in this category too.

Horrible failure of Kingston SSDNow V+200

Postby LongRunner » June 18th, 2018, 10:23 pm

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.)
Last edited by LongRunner on April 6th, 2019, 1:46 am, edited 2 times in total.
Reason: Possibly over-dramatized as originally written
Information is far more fragile than the HDDs it's stored on. Being an afterthought is no excuse for a bad product.

My PC: Core i3 4130 on GA‑H87M‑D3H with GT640 OC 2GiB and 2 * 8GiB Kingston HyperX 1600MHz, Kingston SA400S37120G and WD3003FZEX‑00Z4SA0, Pioneer BDR‑209DBKS and Optiarc AD‑7200S, Seasonic G‑360, Chenbro PC31031, Linux Mint Cinnamon 20.3.
User avatar
LongRunner
Moderator
 
Posts: 1030
Joined: May 17th, 2013, 5:48 pm
Location: Albany, Western Australia

Re: Kingston SSDNow V+200 danger!

Postby Behemot » June 19th, 2018, 2:36 am

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 :group: :facepalm:
User avatar
Behemot
Administrator
 
Posts: 435
Joined: November 28th, 2014, 8:57 am
Location: CZ

Re: Kingston SSDNow V+200 danger!

Postby LongRunner » June 19th, 2018, 2:40 am

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.
Information is far more fragile than the HDDs it's stored on. Being an afterthought is no excuse for a bad product.

My PC: Core i3 4130 on GA‑H87M‑D3H with GT640 OC 2GiB and 2 * 8GiB Kingston HyperX 1600MHz, Kingston SA400S37120G and WD3003FZEX‑00Z4SA0, Pioneer BDR‑209DBKS and Optiarc AD‑7200S, Seasonic G‑360, Chenbro PC31031, Linux Mint Cinnamon 20.3.
User avatar
LongRunner
Moderator
 
Posts: 1030
Joined: May 17th, 2013, 5:48 pm
Location: Albany, Western Australia

Re: Kingston SSDNow V+200 danger!

Postby Behemot » June 30th, 2018, 1:12 pm

There is some scheduled defragmentation? Never seen that. Thought it's run manually. I do that only with HDDs, using Vopt.
User avatar
Behemot
Administrator
 
Posts: 435
Joined: November 28th, 2014, 8:57 am
Location: CZ

Re: Horrible failure of Kingston SSDNow V+200

Postby LongRunner » February 19th, 2020, 10:33 am

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

Since this type of failure is below the level of the Deathstars, :rapidfire: :rapidfire: :rapidfire: :rapidfire: :rapidfire: SandForce
Information is far more fragile than the HDDs it's stored on. Being an afterthought is no excuse for a bad product.

My PC: Core i3 4130 on GA‑H87M‑D3H with GT640 OC 2GiB and 2 * 8GiB Kingston HyperX 1600MHz, Kingston SA400S37120G and WD3003FZEX‑00Z4SA0, Pioneer BDR‑209DBKS and Optiarc AD‑7200S, Seasonic G‑360, Chenbro PC31031, Linux Mint Cinnamon 20.3.
User avatar
LongRunner
Moderator
 
Posts: 1030
Joined: May 17th, 2013, 5:48 pm
Location: Albany, Western Australia


Return to Hard Drives

Who is online

Users browsing this forum: No registered users and 1 guest

cron