I've noticed two times already: during a big system update, encrypt could disappear from HOOKS of
/etc/mkinitcpio.conf
despite that resume - another manually inserted hook - doesn't disappear, so it's not like mkinitcpio.conf simply resets.
If initramfs is regenerated without encrypt hook, a Full Disk Encrypted Artix (currently writing a wiki) - will refuse to boot:
instead of
A password is required to access the lvm-system volume:
Enter passphrase for /dev/sda2:
a user gets
ERROR: device '/dev/mapper/lvmSystem-volRoot' not found. Skipping fsck.
and drops to emergency console.
To fix it, I have to boot with a LiveUSB, mount the encrypted volumes with
sudo su
cryptsetup benchmark # To force loading the Linux kernel modules related to Serpent and other strong encryptions from your LiveCD/LiveUSB
cryptsetup luksOpen /dev/sdX2 lvm-system
mount /dev/lvmSystem/volRoot /mnt
mount /dev/sdX1 /mnt/boot
artools-chroot /mnt /bin/bash
, then
nano /etc/mkinitcpio.conf
to insert encrypt manually
HOOKS="base udev autodetect modconf block encrypt keyboard keymap lvm2 resume filesystems fsck"
, and regenerate the initramfs with
mkinitcpio -p linux
Do you know why encrypt sometimes disappears from /etc/mkinitcpio.conf while resume doesn't?