You are not logged in.

#1 2022-12-21 15:13:31

Registered: 2017-02-08
Posts: 8

Encrypted boot failing since update but can continue

Hello all,

Since the last pacman update I ran my encrypted boot started failing and I can't seem to find out what is going wrong. So I hope someone else sees the problem.

The current behaviour:

I start up the laptop with the following boot settings:

title   Arch Linux test
linux   /vmlinuz-linux
initrd  /intel-ucode.img
initrd  /initramfs-linux.img
options nvidia-drm.modeset=1 cryptdevice=UUID=fad4a476-832c-4f4d-ad87-32c6f5ed02d6:cryptroot1 root=/dev/mapper/cryptroot1 rw

I enter my password and the system seems to boot up oke. Then I see waiting for /dev/mapper/cryptroot. If I check the service it sais the following things:

sudo journalctl -u dev-mapper-cryptroot1.device
Dec 21 15:53:09 viserion systemd[1]: Condition check resulted in /dev/mapper/cryptroot1 being skipped.
Dec 21 15:54:42 viserion systemd[1]: dev-mapper-cryptroot1.device: Job dev-mapper-cryptroot1.device/start time>
Dec 21 15:54:42 viserion systemd[1]: Timed out waiting for device /dev/mapper/cryptroot1.
Dec 21 15:54:42 viserion systemd[1]: dev-mapper-cryptroot1.device: Job dev-mapper-cryptroot1.device/start fail>
Dec 21 15:54:50 viserion systemd[1]: Unnecessary job was removed for /dev/mapper/cryptroot1.

So after a while it fails and this service fails:

Dec 21 15:54:43 viserion @ystemctl[1070]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing.

If I now press ctrl-d the emergency shell will exit and I will get a normal boot. I'm not really sure where to look for the problem so I hope you guys can help me.

This is my /etc/mkinitcpio.conf:

# vim:set ft=sh
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)

# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries

# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.

# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
#HOOKS=(base autodetect modconf block filesystems keyboard systemd systemd-tool)
#HOOKS=(base udev autodetect keyboard keymap consolefont modconf block encrypt filesystems keyboard )
HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block encrypt lvm2 filesystems fsck)

# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.

# Additional options for the compressor



#2 2022-12-22 02:10:48

From: Cymru
Registered: 2011-11-27
Posts: 7,127

Re: Encrypted boot failing since update but can continue

You are, presumably, using systemd-boot. What was in the latest update? I'm guessing systemd was updated as there have been a number of similar reports.

Assuming systemd was updated, see

Last edited by cfr (2022-12-22 02:15:04)

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L


#3 2022-12-22 06:31:21

Registered: 2017-02-08
Posts: 8

Re: Encrypted boot failing since update but can continue

Yes I'm using systemd boot and I guess that was updated. However I can't find a post with this problem. It is really weird to me that unlocking the rootdisk fails but a boot can be continued. Almost as if the rootdisk is trying to be unlocked twice.


Board footer

Powered by FluxBB