SSD seems dead after hard reboot during OS startup - any chance of recovery ?

florent.poujol

Prominent
Jan 11, 2018
3
0
510
Hello everyone

So today I had the magical idea to cut the power to my computer when Ubuntu was still trying to load after 20 mins.
After that I couldn't boot the computer at all. All I saw was a black screen and a single horizontal cursor.
I have access to the BIOS but nothing beyong. Same effect with or without the graphics card or RAM.

After a lot of time and some nice help on twitter (see whole thread), we concluded that the disk was dead.

To resume, all that smartctl could see is basically nothing except that the disk is 20Mb (120Gb in reality) and that SMART can't be enabled (see full output).
Gparted sees the disk but only find 20Mb of unallocated space and no partition table. But neither gparted nor cfdisk couldn't create a new partition table...
The disk is a 120Gb Corsair Force LS.

So considering that, is the disk completely dead or is there something I could do ?
I only realize now that I am typing this that there was my main data partition on that disk, not just Ubuntu...


But also have other questions :

My computer has 3 disks : 1 HD with only data, 1 SSD with Win10, 1 SSD with Ubuntu
It's the one with Ubuntu who died but why can't I boot with windows, even when the dead drive is removed ?

Also when I unplug the HD (with is supposedly only data (it contains a single NTFS partition)), the computer ask to insert a bootable drive and restart, but not when the other disks are removed ?

Finally, this append because I cut the power during Ubuntu startup, how can this "damage" a disk like that ?


So thanks you for reading, and thanks you if you can lead me to some things to do to try to recover the drive.
Florent
 
Solution
If possible it may be best to attach it to another computer to secure erase, you could do that with diskpart commands if you are able to attach it to a Windows machine (XP thru W10) by opening an elevated command prompt box and typing these commands:
diskpart
list disk
select disk n
clean all

Then access it through that computer's disk management and initialize as MBR, then quick format NTFS (for Windows).

If that fails then try the Toolbox, if both fail it is a paperweight. Good Luck!

RealBeast

Titan
Moderator
Could be your SSD has death issues (that output doesn't look promising), but I would try doing a secure erase if you can see it in Gparted.

I've also seen drives that are recoverable with an older version of Gparted or on another computer.

Finally, consider trying the Corsair Toolbox.
 

florent.poujol

Prominent
Jan 11, 2018
3
0
510
Thanks for your reply, doesn't look promising indeed.
I will try the recovery softwares I saw in several posts, including the Corsair Toolbox, but alll of them are for Windows, on which I can't boot yet... I'm working on it.

By the way I may have a answer for one of my questions:
Also when I unplug the HD (with is supposedly only data (it contains a single NTFS partition)), the computer ask to insert a bootable drive and restart, but not when the other disks are removed ?
cfdisk shows that the type of partition for this disk is HPFS/NTFS/exFAT which seems to be the kind of partition type where Windows is supposed to be.
In comparison, the partition type where windows actually is is just "Microsoft Basic Data".
 

RealBeast

Titan
Moderator
If possible it may be best to attach it to another computer to secure erase, you could do that with diskpart commands if you are able to attach it to a Windows machine (XP thru W10) by opening an elevated command prompt box and typing these commands:
diskpart
list disk
select disk n
clean all

Then access it through that computer's disk management and initialize as MBR, then quick format NTFS (for Windows).

If that fails then try the Toolbox, if both fail it is a paperweight. Good Luck!

 
Solution

florent.poujol

Prominent
Jan 11, 2018
3
0
510
The Corsair toolbox was useless, it didn't gave more information the gparted or fdisk.
It did see the disk, but as before, as a 20mb something it can't interact with in any way...

diskpart was apparently able to clean it, at least there was no error. But the disk management app asked to initialize the disk with a GPT partition and then failed because 20Mb is no enough space.

The disk must weight less than 100g, so it's not even useful as a paperweight now...

Anyway, thanks for the help, RealBeast. Good dog.