Project

General

Profile

Unable to access encrypted system

doolio - about 2 years ago -

Since my last "successful" upgrade (sometime in January or February 2022) I'm unable to decrypt my encrypted drive and therefore can't boot my (i686) system. I have separate logical volumes for /boot, /root, /swap and /home. When I can access my system I have to enter my passphrase twice - once at the GRUB screen and again at the TTY screen (never got around to reducing this to one passphrase entry). I can get past the GRUB screen but not the TTY. Perhaps unsurprising as the GRUB payload is not in an encrypted partition? Nothing is printed at the TTY prompt when I enter the passphrase (as usual) but I can't get past this prompt.

Now, I've been able to access my system by booting off a liveUSB and chrooting into my system. From there I was able to upgrade my system but I can't say if it was completely successful as there was some pacman messages about the add_udev_rule command not being found namely:

/usr/lib/initcpio/functions: line 196: add_udev_rule: command not found

My /etc/mkinitcpio.conf HOOKS are as follows:

HOOKS=(base udev autodetect modconf block keyboard keymap consolefont encrypt lvm2 resume filesystems fsck shutdown)

I've tried upgrading again today but am unable due to unresolved dependency errors. I believe they are unrelated to my overall issue and have raised bug [#3204] on these.

Can someone please help me accessing my encrypted system again? If not is there a way I can get my data from this system via the chroot?

TIA.

[#3204] : https://labs.parabola.nu/issues/3204


Replies (1)

RE: Unable to access encrypted system - doolio - about 2 years ago -

Issue resolved by downgrading mkinitcpio (see BR https://labs.parabola.nu/issues/3205 for more details)

    (1-1/1)