Errors while booting the system

So recently I’ve installed EOS Apollo with i3wm and everytime the system boots I get following errors/information:

:: running early hook [udev]
Starting version 250.5-1-arch
:: running hook [udev]
:: Triggering uevents...
:: running hook [keymap]
:: Loading keymap...done.
:: running hook [encrypt]
:: running hook [openswap]
Device does not exist or access denied.
:: running hook [resume]
Waiting 10 seconds for device /dev/mapper/luks-SEQUENCE-OF-NUMBERS1 ...
ERROR: resume: hibernation device '/dev/mapper/luks-SEQUENCE-OF-NUMBERS1' not found
:: performing fsck on 'dev/mapper/luks-SEQUENCE-OF-NUMBERS2'
/dev/mapper/luks-SEQUENCE-OF-NUMBERS2: clean, Numbers/Numbers files, Numbers/Numbers blocks
:: mounting 'dev/mapper/luks-SEQUENCE-OF-NUMBERS2' on real root
:: running cleanup hook [udev]

Prieviously I was using Plasma and never had these messages before.

Is it something to worry about and should I take care of it?

Appreciate the help!

Perhaps some more info could be useful to forummembers who are able to assist you:

lsblk -f

cat /etc/fstab

cat /etc/default/grub

Good luck with troubleshhoting!



Yup, this means you have a hibernation device identified in /etc/default/grub that doesn’t exist (or isn’t available).

/etc/fstab might show it.

1 Like

lsblk -f

NAME                     FSTYPE      FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
β”œβ”€sda1                   vfat        FAT32 NO_LABEL 236D-B249                             298,9M     0% /boot/efi
β”œβ”€sda2                   crypto_LUKS 1              7ea9d4b6-fc37-49ea-9b87-780b0e3a45f4                
β”‚ └─luks-7ea9d4b6-fc37-49ea-9b87-780b0e3a45f4
β”‚                        ext4        1.0            0922ce01-3e07-41ad-954d-5808633a6c6b   89,2G    55% /
└─sda3                   crypto_LUKS 1              3f881d06-e94b-405f-b753-56e03e7500fe                
                         swap        1     swap     6db410c2-9c7f-49b0-879d-205be79769d6                [SWAP]

cat /etc/fstab

   1   β”‚ # /etc/fstab: static file system information.
   2   β”‚ #
   3   β”‚ # Use 'blkid' to print the universally unique identifier for a device; this may
   4   β”‚ # be used with UUID= as a more robust way to name devices that works even if
   5   β”‚ # disks are added and removed. See fstab(5).
   6   β”‚ #
   7   β”‚ # <file system>             <mount point>  <type>  <options>  <dump>  <pass>
   8   β”‚ UUID=236D-B249                            /boot/efi      vfat    defaults,noatime 0 2
   9   β”‚ /dev/mapper/luks-7ea9d4b6-fc37-49ea-9b87-780b0e3a45f4 /              ext4    defaults,noatime 0 1
  10   β”‚ /dev/mapper/luks-3f881d06-e94b-405f-b753-56e03e7500fe swap           swap    defaults   0 0
  11   β”‚ tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

cat /etc/default/grub

   1   β”‚ # GRUB boot loader configuration
   2   β”‚ 
   3   β”‚ GRUB_DEFAULT=0
   4   β”‚ GRUB_TIMEOUT=5
   5   β”‚ GRUB_DISTRIBUTOR="EndeavourOS"
   6   β”‚ GRUB_CMDLINE_LINUX_DEFAULT="cryptdevice=UUID=7ea9d4b6-fc37-49ea-9b87-780b0e3a45f4:luks-7ea9d4b6-fc37-49ea-
       β”‚ 9b87-780b0e3a45f4 root=/dev/mapper/luks-7ea9d4b6-fc37-49ea-9b87-780b0e3a45f4 resume=/dev/mapper/luks-3f881
       β”‚ d06-e94b-405f-b753-56e03e7500fe loglevel=3 nowatchdog nvme_load=YES"
   7   β”‚ GRUB_CMDLINE_LINUX=""
   8   β”‚ 
   9   β”‚ # Preload both GPT and MBR modules so that they are not missed
  10   β”‚ GRUB_PRELOAD_MODULES="part_gpt part_msdos"
  11   β”‚ 

  12   β”‚ # Uncomment to enable booting from LUKS encrypted devices
  14   β”‚ 
  15   β”‚ # Set to 'countdown' or 'hidden' to change timeout behavior,
  16   β”‚ # press ESC key to display menu.
  17   β”‚ GRUB_TIMEOUT_STYLE=menu
  18   β”‚ 
  19   β”‚ # Uncomment to use basic console
  20   β”‚ GRUB_TERMINAL_INPUT=console
  21   β”‚ 
  22   β”‚ # Uncomment to disable graphical terminal
  23   β”‚ #GRUB_TERMINAL_OUTPUT=console
  24   β”‚ 
  25   β”‚ # The resolution used on graphical terminal
  26   β”‚ # note that you can use only modes which your graphic card supports via VBE
  27   β”‚ # you can see them in real GRUB with the command `vbeinfo'
  28   β”‚ GRUB_GFXMODE=auto
  29   β”‚ 
  30   β”‚ # Uncomment to allow the kernel use the same resolution used by grub
  32   β”‚ 
  33   β”‚ # Uncomment if you want GRUB to pass to the Linux kernel the old parameter
  34   β”‚ # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
  35   β”‚ #GRUB_DISABLE_LINUX_UUID=true
  36   β”‚ 
  37   β”‚ # Uncomment to disable generation of recovery mode menu entries
  39   β”‚ 
  40   β”‚ # Uncomment and set to the desired menu colors.  Used by normal and wallpaper
  41   β”‚ # modes only.  Entries specified as foreground/background.
  42   β”‚ #GRUB_COLOR_NORMAL="light-blue/black"
  43   β”‚ #GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
  44   β”‚ 
  45   β”‚ # Uncomment one of them for the gfx desired, a image background or a gfxtheme
  46   β”‚ #GRUB_BACKGROUND="/path/to/wallpaper"
  47   β”‚ #GRUB_THEME="/path/to/gfxtheme"
  48   β”‚ GRUB_THEME=/boot/grub/themes/EndeavourOS/theme.txt
  49   β”‚ 
  50   β”‚ # Uncomment to get a beep at GRUB start
  51   β”‚ #GRUB_INIT_TUNE="480 440 1"
  52   β”‚ 
  53   β”‚ # Uncomment to make GRUB remember the last selection. This requires
  54   β”‚ # setting 'GRUB_DEFAULT=saved' above.
  55   β”‚ #GRUB_SAVEDEFAULT=true
  56   β”‚ 
  57   β”‚ # Uncomment to disable submenus in boot menu
  59   β”‚ 
  60   β”‚ # Probing for other operating systems is disabled for security reasons. Read
  61   β”‚ # documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
  62   β”‚ # functionality install os-prober and uncomment to detect and include other
  63   β”‚ # operating systems.
  64   β”‚ GRUB_DISABLE_OS_PROBER=false

This looks good to me but thing is I am not good with encryption :blush: :sweat_smile:

While waiting for users with more experience in this area, you could try:

sudo mkinitcpio -P


sudo grub-mkconfig -o /boot/grub/grub.cfg

and reboot. No guaranties :wink:

Also, perhaps post:

cat /etc/mkinitcpio.conf

Ok, I’ll try it, thanks!

1 Like

cat /etc/mkinitcpio.conf

   1   β”‚ # vim:set ft=sh
   2   β”‚ # MODULES
   3   β”‚ # The following modules are loaded before any boot hooks are
   4   β”‚ # run.  Advanced users may wish to specify all system modules
   5   β”‚ # in this array.  For instance:
   6   β”‚ #     MODULES=(piix ide_disk reiserfs)
   7   β”‚ MODULES=""
   8   β”‚ 
   9   β”‚ # BINARIES
  10   β”‚ # This setting includes any additional binaries a given user may
  11   β”‚ # wish into the CPIO image.  This is run last, so it may be used to
  12   β”‚ # override the actual binaries included by a given hook
  13   β”‚ # BINARIES are dependency parsed, so you may safely ignore libraries
  14   β”‚ BINARIES=()
  15   β”‚ 
  16   β”‚ # FILES
  17   β”‚ # This setting is similar to BINARIES above, however, files are added
  18   β”‚ # as-is and are not parsed in any way.  This is useful for config files.
  19   β”‚ FILES="/crypto_keyfile.bin"
  20   β”‚ 
  21   β”‚ # HOOKS
  22   β”‚ # This is the most important setting in this file.  The HOOKS control the
  23   β”‚ # modules and scripts added to the image, and what happens at boot time.
  24   β”‚ # Order is important, and it is recommended that you do not change the
  25   β”‚ # order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
  26   β”‚ # help on a given hook.
  27   β”‚ # 'base' is _required_ unless you know precisely what you are doing.
  28   β”‚ # 'udev' is _required_ in order to automatically load modules
  29   β”‚ # 'filesystems' is _required_ unless you specify your fs modules in MODULES
  30   β”‚ # Examples:
  31   β”‚ ##   This setup specifies all modules in the MODULES setting above.
  32   β”‚ ##   No raid, lvm2, or encrypted root is needed.
  33   β”‚ #    HOOKS=(base)
  34   β”‚ #
  35   β”‚ ##   This setup will autodetect all modules for your system and should
  36   β”‚ ##   work as a sane default
  37   β”‚ #    HOOKS=(base udev autodetect block filesystems)
  38   β”‚ #
  39   β”‚ ##   This setup will generate a 'full' image which supports most systems.
  40   β”‚ ##   No autodetection is done.
  41   β”‚ #    HOOKS=(base udev block filesystems)
  42   β”‚ #
  43   β”‚ ##   This setup assembles a pata mdadm array with an encrypted root FS.
  44   β”‚ ##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
  45   β”‚ #    HOOKS=(base udev block mdadm encrypt filesystems)
  46   β”‚ #
  47   β”‚ ##   This setup loads an lvm2 volume group on a usb device.
  48   β”‚ #    HOOKS=(base udev block lvm2 filesystems)
  49   β”‚ #
  50   β”‚ ##   NOTE: If you have /usr on a separate partition, you MUST include the
  51   β”‚ #    usr, fsck and shutdown hooks.
  52   β”‚ HOOKS="base udev autodetect modconf block keyboard keymap consolefont encrypt openswap resume filesystems fsck"
  53   β”‚ 
  54   β”‚ # COMPRESSION
  55   β”‚ # Use this to compress the initramfs image. By default, zstd compression
  56   β”‚ # is used. Use 'cat' to create an uncompressed image.
  57   β”‚ COMPRESSION="zstd"
  58   β”‚ #COMPRESSION="gzip"
  59   β”‚ #COMPRESSION="bzip2"
  60   β”‚ #COMPRESSION="lzma"
  61   β”‚ #COMPRESSION="xz"
  62   β”‚ #COMPRESSION="lzop"
  63   β”‚ #COMPRESSION="lz4"
  64   β”‚ 
  66   β”‚ # Additional options for the compressor

I haven’t seen an encrypted swap partition in a long time.

Anyhow, can we see the output of the following, please:
sudo cat /etc/crypttab | grep -v '#'
cat /etc/mkinitcpio.conf | grep 'HOOKS="'

Unfortunately it didn’t work

1 Like


luks-7ea9d4b6-fc37-49ea-9b87-780b0e3a45f4 UUID=7ea9d4b6-fc37-49ea-9b87-780b0e3a45f4     /crypto_keyfile.bin luks
luks-3f881d06-e94b-405f-b753-56e03e7500fe UUID=3f881d06-e94b-405f-b753-56e03e7500fe     /crypto_keyfile.bin luks


HOOKS="base udev autodetect modconf block keyboard keymap consolefont encrypt openswap resume filesystems fsck"

Seems OK to me…

Here’s a long shot, but maybe …
Edit /etc/mkinitcpio.conf and change the order of your hooks. Make sure resume is located after filesystems.

Then run

sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo mkinitcpio -p linux

and reboot.

1 Like

Just saw you installed mkinitcpio-openswap. You may need to check and (re-)configure openswap (example).

Maybe also try to move the openswap hook after filesystems in your mkinitcpio.conf.

[Edit] Please post
cat /etc/openswap.conf

  1. placed both hooks openswap and resume after filesystems but nothing changed
  2. cat /etc/openswap.conf: (just this single line)
   1   β”‚ ## cryptsetup open $swap_device $crypt_swap_name

Worth reading:

1 Like

Ok, so what I discovered is that it happens now with any other EOS installation (KDE, Xfce, etc. not only i3) so there must have been a change in the latest EOS iso (Apollo)
My previous installs never had this β€œissue”

Edit /etc/openswap.conf to resemble something like the following:

## cryptsetup open $swap_device $crypt_swap_name
# cryptsetup open $swap_device $crypt_swap_name
## get uuid using e.g. lsblk -f

## one can optionally provide a keyfile device and path on this device
## to the keyfile

## additional arguments are given to mount for keyfile_device
## has to start with --options (if so desired)

## additional arguments are given to cryptsetup
## --allow-discards options is desired in case swap is on SSD partition
cryptsetup_options="--type luks"

From what I gather, most people prefer a swapfile to a partition nowadays anyway. Much more flexible imo. Unless you want to share the partition with different installs, I personally see no benefit.

Maybe try a swapfile on one of your next installs?

It’s exactly the same after adding this to the config. I mean, my PC boots just fine despite these errors so I guess it’s not a big deal. I was just wondering if it was sth serious and if it’s easy to fix.
Anyways I appreciate your help!

I actually tried it with with swapfile and the first sequence was also the same, the only difference was that the part with Hibernation wasn’t there

basically it was sth like this (installation with swapfile):

:: running early hook [udev]
Starting version 250.5-1-arch
:: running hook [udev]
:: Triggering uevents...
:: running hook [keymap]
:: Loading keymap...done.
:: running hook [encrypt]
:: performing fsck on 'dev/mapper/luks-SEQUENCE-OF-NUMBERS2'
/dev/mapper/luks-SEQUENCE-OF-NUMBERS2: clean, Numbers/Numbers files, Numbers/Numbers blocks
:: mounting 'dev/mapper/luks-SEQUENCE-OF-NUMBERS2' on real root
:: running cleanup hook [udev]


something like this?