Reading a failed SSD?

My drive failed yesterday, it had Windows & another partitin with data I want to get if it is simple to do. The thing is it was after a update, not sure if that did it. Linux doesn’t see it at all though, so IMO the drive faailed. The odd thing, it was fine, no strangeness before thar.

If it were a spinning hard disk drive, then you could try salvaging things by mounting it read-only. But SSDs work entirely differently, and if they fail, then there’s usually nothing you can do, because SSDs tend to fail catastrophically, not gradually like an HDD.

See, this is why you need to make backups on a separate drive, man. You never know when it’s going to fail, and then at least you’ll still have a copy of all your data.

4 Likes

No backup, no sympathy.

There are professional companies, working for forensics,

tools are not for the ordinary people, i fear.

And neither are the invoices of said specialized companies. :face_with_diagonal_mouth:

2 Likes

I experienced this two times - first with a SanDisk SSD and later with a brand new Samsung Evo.

As they were my system drives, I had my backups ready on HDD, so as soon as they were replaced it’s not difficult to restore the system.

I had about 20 minutes warning for the Sandisk after which it was completely unavailable, the Samsung didn’t make it through it’s first day - I had to wait for a replacement.

However, there’s little point fostering dreams of running testdisk to recover data - SSD’s just die differently.

1 Like

Out of luck then. I was hoping it was Windows update, heard of them making the sys not see the drive, but Linux doesn’t even see it, so…

Well, no, what a Windows update does tend to do is wipe out your EFI stubs in favor of its own — and re-enable Secure Boot. But that’s usually reparable.

Does your EFI firmware or BIOS still see the drive?

Nope, google said plug it just into power overnight. That might fix it long enough to get dat6a copied.

Incredibly, about three months ago Microsoft released an automatic update (KB5063878) that made some SSDs disappear and data may get corrupted…

3 Likes

One of the messages in the thread:

For the community, I am sharing that if you search YT - JayTwoCents SSD Problem Way Worse

You will find the video where Jay has been able to show how to reproduce the problem that is affecting many controllers not just Phison Controllers.

Certain high bandwidth applications being run can trigger Windows to bluescreen and BIOS to lose the drive.

Jay rectifies it by hard powercycling the computer. On a laptop battery would need to be disconnected - so that the SSD drive controller is completely without power to lose any settings and the same for computer bios. then after hard power on normal operation should resume.

curious for others to report back here if they are able to recover based on above steps – drive should become visible in bios after full/hard power cycle where drive and bios clear drive settings…

Best regards,

Wez

So unplug your computer for multiple hours, and plug it back in, boot to BIOS and see if the SSD reappears again if this is the issues that affected you.

5 Likes

Would it be invisable to linux also?

The drive simply disappears from the computer. Sometimes rebooting reappears, sometimes not.

Well the connector came apart, I didn’t see it, but my dad said that. He is going to sodor (sp) it back.

3 Likes

Nope, didn’t work. Smashed the board with a hammer, so no one can get anything of it.

:white_check_mark: Solved with hammer.

4 Likes

May be it was a Samsung drive. :grinning_face:

3 Likes

Problem solved… the Klingon way… :face_with_hand_over_mouth:

:backhand_index_pointing_down:

2 Likes