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
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.
Okay, it looks like you posted this prior to me posting my comment above. I’m not familiar with this graphical utility, but I’m assuming that it means that your disk is visible (like, if you run ls /dev/sda, you see your disk).
So what you’ve probably got is a functioning hard drive, with a functioning partition table, and on the first partition (/dev/sda1), a LUKS layer.
I haven’t used LUKS, but it’s a block-level encryption layer for Linux. It’ll have some command to expose an unencrypted layer, and you can mount that.
I think that mount the mount(1) command is probably calling the mount(2) system call, and it’s returning ENOENT, error 2. The mount(2) man page says “ENOENT A pathname was empty or had a nonexistent component.”.
Hmm. So, I expect from the cyan color there that that “luks-d8…” thing is a symlink that points at some device file that LUKS creates when that luksOpen command runs.
Maybe ls -l /dev/mapper/luks-d8... and see what it points at and whether that exists as a first step? It’s probably gonna be some device file somewhere in /dev.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
What exactly do you mean by “not mountable”?
I attempted to mount the disk and it says “unable to mount”.
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.
Here are some more screenshot of the disk. Maybe its a BTRFS failure?
Okay, it looks like you posted this prior to me posting my comment above. I’m not familiar with this graphical utility, but I’m assuming that it means that your disk is visible (like, if you run
ls /dev/sda, you see your disk).So what you’ve probably got is a functioning hard drive, with a functioning partition table, and on the first partition (/dev/sda1), a LUKS layer.
I haven’t used LUKS, but it’s a block-level encryption layer for Linux. It’ll have some command to expose an unencrypted layer, and you can mount that.
Let’s try walking through this in a terminal.
From https://superuser.com/questions/1702871/how-to-do-cryptsetup-luksopen-and-mount-in-a-single-command, it looks like the way this works is that one runs:
Your encrypted partition name is presently at /dev/sda1. So try running:
That should prompt you for a password. If it can decrypt it, it looks like it creates a block device at /dev/mapper/my-unencrypted.
You can then create a directory to use as a mountpoint:
And try mounting it (assuming that it’s just a filesystem):
Same Error. Weird.
considers
I think that mount the mount(1) command is probably calling the mount(2) system call, and it’s returning ENOENT, error 2. The mount(2) man page says “ENOENT A pathname was empty or had a nonexistent component.”.
Hmm. So, I expect from the cyan color there that that “luks-d8…” thing is a symlink that points at some device file that LUKS creates when that
luksOpencommand runs.Maybe
ls -l /dev/mapper/luks-d8...and see what it points at and whether that exists as a first step? It’s probably gonna be some device file somewhere in /dev.