I can't offer much but have found an article you might find useful - is it SSD or mechanical? If the latter, does it spin up?
This (for mechanical drives) is quite detailed and might be useful for info (more perhaps from the section "Recover Your Data with Hardware" onwards)
http://www.lifehacker.co.uk/2013/02/07/recover-data-hard-drive-goes-belly
Presumably SSD controller boards can be replaced too if necessary... would be interested to hear how you get on.
On Fri, 14 Jul 2017, at 11:52, Rob Malpass via Hampshire wrote:
> Hi all
>
> After a recent power outage here overnight, one of my servers failed to boot and went into emergency mode (Ubuntu 16.04) with no amount of fsck getting me out of trouble. After a lot of faffing with fstab (it has about 5 drives attached to it) I’ve found the UUID of the failing drive. This was by trial and error removing them all and adding them one by one rebooting each time until I found the problem drive.>
> Now when I do:
>
> sudo blkid |grep <UUID of failing drive>
>
> there is no listing. As (thank goodness) the problem drive wasn’t important, I can just leave its entry commented out in /etc/fstab but I’d like to try and fix it if I can. But if I can’t see it in the list of UUIDs, how do I mount it and therefore try and fix it?>
> Cheers
> Rob
>
>
> Virus-free. www.avg.com[1]
>
> --
> Please post to: Hampshire@???
> Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
> LUG URL: http://www.hantslug.org.uk
> --------------------------------------------------------------
Links:
1.
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient
--
Please post to: Hampshire@???
Web Interface:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL:
http://www.hantslug.org.uk
--------------------------------------------------------------
