Submitted 6 months ago by calmluck9349@infosec.pub to selfhosted@lemmy.world
The primary OS for this disk was Unraid. Its formated in BTRFS. I don’t think either of those matter. The disk spins and worked before the reboot. But now. No matter what machine, port or cable I use its not mountable. Is there anything I can try? I was going to attempt Spinrite on it however it doesn’t see anything either. Thanks! Its a HGST drive dated May2019
What exactly do you mean by “not mountable”?
I attempted to mount the disk and it says “unable to mount”. Image
I think there might need to be more than one cylinder. (Referring to photo) Hmm…
This is the error from my laptop when I try and mount. It asked for the encryption password just before this. And makes all the normal annoying hard drive sounds.
So does the actual block device show up as recognized?
tal@lemmy.today 6 months ago
If you have a Linux machine, look in
/sys/class/blockand see if it shows up there. That’ll give you a list of devices at the block device level. There should be an entry there, regardless of what you’ve done with partitioning or filesystems on those partitions.If it doesn’t show up there, the drive is probably having trouble at a hardware level. There are various tactics that people have tried to get a rotational drive functioning, like different temperatures, having the drive in different orientations, etc. Those might work, but if the drive is having physical problems, it might also continue to degrade.
Your best bet, if the information is sufficiently worthwhile to you, is probably to send the drive to a data recovery company. What they’ll do is use a drive with the same hardware, and in a clean room, swap the platters, and as long as it’s still functional, they can image the drive at that point. IIRC you’re talking something in the neighborhood of $500, though I’ve never needed to do this myself (backups!).
If it does show up, then you can look at whether you’re getting kernel log errors when attempting to read from the drive (
journalctl -k -b). If so, it might be recoverable, at least in part.If not, then whatever your issue is might only be in terms of the data on the drive. My first step – knowing nothing about how Unraid sets things up – would probably be to look at the partition table on the drive (
sudo parted <drive-device-name>). You can manually mount a partition with (mount <partition-name> <mount-point>).vegetaaaaaaa@lemmy.world 6 months ago
lsblkalso show block devices and is prettier than looking directly at/sys/class/block