Error while booting into new LUKS encrypted Manjaro Install

_thomas · 20 March 2022 09:16

Hello,
so I have a slight problem, every time I boot into my new installed LUKS encrypted Manjaro.
I get promoted the following error messages on tty1.
I used the calameres installer and choose the “automated” install with no hibernation swap.I also tried the manual partitioning, but the error stays the same.

The procedure to replicate the error:
When I turn on my DellOptiplex computer, first I get promoted to enter my LUKS key, after then it shows “Slot 0 opened” so far so good.

Then I get the following prompted

But then, it boot just normally into lightDM and I can log in into my XFCE installation…

Side notes:
I had to get rid of the previously pre installed windows on this Dell computer and I think somehow the recovery partitions are involved into that.
I had to disable TPM and secure boot as well, but I honestly don’t care about those.

The error itself is not hindering me, but it’s quite annoying and I want to know what’s happening there before I go into actual production with this computer.

Thanks for all your help
Thomas

megavolt · 20 March 2022 10:23

Hello @_thomas

Isn’t it obvious? The encrypted swap does not exist (or cannot be found) which is needed for hibernation.

Check
/etc/fstab
/etc/cryptab
/etc/default/grub

_thomas · 21 March 2022 06:49

/etc/fstab

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=4371-64B5                            /boot/efi      vfat    umask=0077 0 2
/dev/mapper/luks-d67b2740-1562-45d5-8393-d0157d3252a3 /              ext4    defaults,noatime 0 1
/dev/mapper/luks-28ee9e80-53e7-4f6d-8e5d-a371519f697c swap           swap    defaults,noatime 0 0

/etc/crypttab

# <name>               <device>                         <password> <options>
luks-d67b2740-1562-45d5-8393-d0157d3252a3 UUID=d67b2740-1562-45d5-8393-d0157d3252a3     /crypto_keyfile.bin luks
luks-28ee9e80-53e7-4f6d-8e5d-a371519f697c UUID=28ee9e80-53e7-4f6d-8e5d-a371519f697c     /crypto_keyfile.bin luks

/etc/default/grub

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet cryptdevice=UUID=d67b2740-1562-45d5-8393-d0157d3252a3:luks-d67b2740-1562-45d5-8393-d0157d3252a3 root=/dev/mapper/luks-d67b2740-1562-45d5-8393-d0157d3252a3 apparmor=1 security=apparmor resume=/dev/mapper/luks-28ee9e80-53e7-4f6d-8e5d-a371519f697c udev.log_priority=3"
GRUB_CMDLINE_LINUX=""

GRUB_SAVEDEFAULT=true
#GRUB_DISABLE_SUBMENU=y
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
GRUB_TERMINAL_INPUT=console
#GRUB_TERMINAL_OUTPUT=console
GRUB_GFXMODE=auto
GRUB_GFXPAYLOAD_LINUX=keep
#GRUB_DISABLE_LINUX_UUID=true
GRUB_DISABLE_RECOVERY=true
GRUB_DISABLE_OS_PROBER=false

GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
#GRUB_INIT_TUNE="480 440 1"
#GRUB_ROOT_FS_RO=true

GRUB_ENABLE_CRYPTODISK=y

So as for me, it looks alright-ish? fstab and crypttab both know about the swap partition and therefore mounting at boot should be possible…
In the grub config file last parameter with CRYPTODISK is set and the CMDLINE parameter also knows about both LUKS drives (root and swap)

winnie · 21 March 2022 12:49

You’ll notice a resume parameter specified in your GRUB_CMDLINE_LINUX_DEFAULT.

~~The only solution is to wipe your entire drive and start all over again.~~

Moderator’s edit: That’s not true, plus it’s dangerous. Don’t listen to @winnie. You can simply remove the resume parameter from GRUB.

You should also comment out the first entry in your crypttab, since the initramfs is responsible for unlocking and mapping your root filesystem during boot.

Something like this:

_thomas:

/etc/crypttab

# <name>               <device>                         <password> <options>
# luks-d67b2740-1562-45d5-8393-d0157d3252a3 UUID=d67b2740-1562-45d5-8393-d0157d3252a3     /crypto_keyfile.bin luks
luks-28ee9e80-53e7-4f6d-8e5d-a371519f697c UUID=28ee9e80-53e7-4f6d-8e5d-a371519f697c     /crypto_keyfile.bin luks

_thomas · 21 March 2022 13:51

Soooo so far I’ve got rid of a bit oft the errors, but still there are some left, and believe me blatantly reinstalling Manjaro is no solution to a repetitive problem that directly reaccured without knowing the problem

andresgarita · 11 April 2022 18:02

I can’t include links, but try with this: (forum manjaro org) empty-etc-openswap-conf-manjaro-xfce-gnome-21-2-4-5-minimal-220301-linux515-iso-default-install-fde-nohibernation-on-efi-baremetal-or-kvm-boot-device-does-not-exists/106452/3