SSD Superblock failed

[Jamie Grimwood]

Hey there,

 

I am new to the forum and was hoping someone could help me. Recently one of my drives in my server went into read-only mode. After a reboot, it went into kernel panic. Once the datacenter technicians took a look, they ended up saying that the drives superblock had corrupted. They installed a new OS on new drives, and plugged in the old drives into the machine so we could pull the *crucial* data off of it, however it is refusing to mount, with the error “can’t read superblock”. I've tried switching superblock backups with 0 luck. What else can I do as I really need this data back. Thanks.

[Levent]

I deal with this problem every other month and this write-up is what I use. That being said, if the data is matter of life and death, I would always recommend you to use professional data recovery services.

[Jamie Grimwood]

Just now, Levent said:

I deal with this problem ever other month and this write-up is what I use. That being said, if the data is matter of life and death, I would always recommend you to use professional data recovery services.

Sadly, i've tried this guide already. None of the backups seem to have worked and always produce the same output. 

 

[Kilrah]

Note that this corrects the original filesystem, if it's gone read-only it will be unable to so you'll need to image it first and work on the image. That's probably why you get the errors you do.

[Jamie Grimwood]

1 minute ago, Kilrah said:

Note that this corrects the original filesystem, if it's gone read-only that won't work so you'll need to image it first and work on the image. That's probably why you get the errors you do.

Do you have a guide for this?

[Kilrah]

See the "Create a Clone Disk Image" section there https://linuxhint.com/make-disk-images-dd-command-linux/

 

You'll need a drive bigger than the source one to store it on obviously. If using ubuntu you can then mount the image using "Disks", make sure to uncheck "read-only" as it's enabled by default.

 

After making the image I'd copy it to yet another drive before doing work just in case the attempt at fixing things fails and corrupts it more and the source drive happened to die for good at the same time as well...