uhho did i kill my ssd?

sublimening

Commendable
Nov 22, 2017
17
0
1,510
I have 3 SSD's and 1 HDD on my system. I turned my comp off to install some lights and pushed wires around etc and when I turned it back on I'm missing one of my SSD's

I couldn't find it in disk management or BIOS.

I have already tried

-unplugged and replugged the drive in,
-new sata port on MOBO
-trying sata cable from another HD
-hot plugging and hot unplugging it

still no luck, doesn't show up on BIOS even with new sata cable

SSD is Sandisk Ultra plus (can't remember amount 260?)

did i somehow static shock the thing and kill it?

whats going on?
 
Solution

Always update your SSD firmware to a newer version if available!! Often they fix serious issues revolving around data integrity and reliability (as well as performance boosts). In theory you won't lose data for the update (although they do stress to back it up first, of course).

You'd very likely know if you killed it from a static shock. If you can, try it in a different system. If it doesn't show up in a new system then it's quite likely that it's killed, for some reason or another.

Try a BIOS update first, then try it in a different system.
 


ya, power cable and sata cable are fully seated and the power cable is on the same line as the other two SSD's so I think its gone....

that blows ... it just was running perfect with Fallout 4 vr.... I'm confused

I don't remember a static shock either....so how does that just happen?
 


Bios is up to date. I did have some random windows 10 "usb disconnect noises" lately. When I checked the safely remove icon all I could see what my drives so maybe that was that disconnecting a lot? prob just my stupid headset tho...

yeah ssd's go super suddenly I guess wow..
 

I've had two die on me with 100% data loss. People on hardware forums (including this one) are always harping on about the "write endurance" of MLC vs TLC vs 3D NAND etc as if that is what matters; but the actual common critical failure point of SSDs is the controller, which is obviously completely independent of the NAND used.

 


well It was the SSD I used to use as my primary drive for 4-5 years.. I remember that if that drive reached the red on disk used then it would always "LOSE" the boot file and I would have to reinstall windows all together. So that SSD had problems to begin with.
could that cause controller failure or be a symptom?
 

Almost certainly a controller issue (which includes faulty/buggy firmware). Often manufacturers will stop updating what they know is dodgy firmware and focus on marketing of their new models (which DO have updated firmware). Incidentally, how often have you updated firmware on an HDD or wish you could? Never, right?
 

lmao I have never updated firmware on an HDD or an SSD lol I think they kinda count on that.

I do keep other drivers and bios and stuff up to date.
 

Always update your SSD firmware to a newer version if available!! Often they fix serious issues revolving around data integrity and reliability (as well as performance boosts). In theory you won't lose data for the update (although they do stress to back it up first, of course).

 
Solution