Comment on HDD spins but OS doesnt see mountable disk

• calmluck9349@infosec.pub ⁨6⁩ ⁨months⁩ ago

  Here are some more screenshot of the disk. Maybe its a BTRFS failure?

  Image

  Image

  source

  • tal@lemmy.today ⁨6⁩ ⁨months⁩ ago

    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, 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 superuser.com/…/how-to-do-cryptsetup-luksopen-and…, it looks like the way this works is that one runs:

    $ sudo cryptsetup luksOpen <encrypted-device-name> <unencrypted-block-device-name>
    

    Your encrypted partition name is presently at /dev/sda1. So try running:

    $ sudo cryptsetup luksOpen /dev/sda1 my-unencrypted
    

    That should prompt you for a password. If it can decrypt it, it looks like it creates a block device at /dev/dm/my-unencrypted.

    You can then create a directory to use as a mountpoint:

     $ sudo mkdir -p /mnt/my-mount-point
    

    And try mounting it (assuming that it’s just a filesystem):

    $ sudo mount /dev/dm/my-unencrypted /mnt/my-mount-point
    

    source

    • calmluck9349@infosec.pub ⁨6⁩ ⁨months⁩ ago

      Same Error. Weird.

      Image

      source

      • tal@lemmy.today ⁨6⁩ ⁨months⁩ ago

        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 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.

        source