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.
tal@lemmy.today 4 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
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.