Skip to content

Hibernation device not found after fresh installation with latest manjaro images

I'm coming from manjaro's user forum and was pointed to this repo to report a bug existing on all the latest manjaro images. Since I recommend manjaro to all my friends I would like to give new users a smooth experience with manjaro. Unfortunately there is a general issue with hibernation and disc encryption when using the latest manjaro images (reproduced with XFCE and KDE images) After installing the latest official XFCE manjaro (manjaro-xfce-21.2.6-220416-linux515.iso / or manjaro-kde-21.2.6-220416-linux515.iso) with disc encryption and hibernation the user prompted with the following error message after first reboot:

Device does not exist or access denied. ERROR: resume: hibernation device '/dev/mapper/luks-....' not found

I wasn't able to reproduce the issue with an older image e.g. manjaro-xfce-21.1.6-211017-linux513.iso. So this bug seems to be introduced somewhere in between 21.1.6 and 21.2.6.

Attaching some console outputs and information about the exact installation setup, so that everybody is able to reproduce the issue.

calamares version 3.2.53-2 included in manjaro-xfce-21.2.6-220416-linux515.iso

installation-hibernate-disc-encrypt

Error Message after installation is done and reboot was triggered: hibernation-device-not-found2

$ cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
/dev/mapper/luks-f81d2daf-dca7-4bb1-a125-df6698cd6583 /              ext4    defaults,noatime 0 1
/dev/mapper/luks-34d4fe94-388a-439c-bc4e-d185ce9370df swap           swap    defaults,noatime 0 0
$ lsblk -o name,uuid
NAME                                          UUID
sda                                           
├─sda1                                        f81d2daf-dca7-4bb1-a125-df6698cd6583
│ └─luks-f81d2daf-dca7-4bb1-a125-df6698cd6583 6569186d-f45a-4861-ab32-e75f68b10499
└─sda2                                        34d4fe94-388a-439c-bc4e-d185ce9370df
  └─luks-34d4fe94-388a-439c-bc4e-d185ce9370df f0346115-8966-46b1-acd2-7ca1c44a84d2
$ /etc/crypttab 
<name>               <device>                         <password> <options>
luks-f81d2daf-dca7-4bb1-a125-df6698cd6583 UUID=f81d2daf-dca7-4bb1-a125-df6698cd6583     /crypto_keyfile.bin luks
luks-34d4fe94-388a-439c-bc4e-d185ce9370df UUID=34d4fe94-388a-439c-bc4e-d185ce9370df     /crypto_keyfile.bin luks
$ cat /etc/default/grub |grep LINUX_DEFAULT
GRUB_CMDLINE_LINUX_DEFAULT="quiet cryptdevice=UUID=f81d2daf-dca7-4bb1-a125-df6698cd6583:luks-f81d2daf-dca7-4bb1-a125-df6698cd6583 root=/dev/mapper/luks-f81d2daf-dca7-4bb1-a125-df6698cd6583 apparmor=1 security=apparmor resume=/dev/mapper/luks-34d4fe94-388a-439c-bc4e-d185ce9370df udev.log_priority=3"
Edited by ntl
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information