1

After updating with pacman -Syu system fails to boot.

ERROR: device '/dev/lvmSystemXXX/volRootXXX' not found. Skipping fsck.
mount: /new_root: fsconfig() failed: /dev/lvmSystemXXX/volRootXXX: Can't lookup blockdev.
ERROR: failed to mount '/dev/lvmSystemXXX/volRootXXX' on real root
You are now being dropped into an emergecy shell.
sh: can't access tty: job control truned off
[rootfs ~]#

Some background info

Linux:

[rootfs ~]# uname -a
Linux archlinux 6.15.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 02 Aug 2025... x86_64 GNU/Linux

Drives

[rootfs ~]# blkid
/dev/sdb2:UUID="A123456789" TYPE="crypto_LUKS" PARTUUID="A987654321"
/dev/sdb1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="B123456789" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="B987654321"

Is there a possibility to check if the kernel was updated and eventually downgrade from emergecy shell?

mkinitcpio.conf file here

    # vim:set ft=sh
# MODULES
# 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=(usbhid xhci_hcd)
MODULES=()

# BINARIES
# 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
BINARIES=()

# FILES
# 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.
FILES=()

# HOOKS
# 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 modconf block filesystems fsck)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev modconf block filesystems fsck)
#
##   This setup assembles a mdadm array with an encrypted root file system.
##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
#    HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
##   This setup loads an lvm2 volume group.
#    HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
##   This will create a systemd based initramfs which loads an encrypted root filesystem.
#    HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr and fsck hooks.
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used for Linux ≥ 5.9 and gzip compression is used for Linux < 5.9.
# Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

# MODULES_DECOMPRESS
# Decompress loadable kernel modules and their firmware during initramfs
# creation. Switch (yes/no).
# Enable to allow further decreasing image size when using high compression
# (e.g. xz -9e or zstd --long --ultra -22) at the expense of increased RAM usage
# at early boot.
# Note that any compressed files will be placed in the uncompressed early CPIO
# to avoid double compression.
#MODULES_DECOMPRESS="no"

Problem found: pacman.log shows that at last update no more space left on the root partition. See log below.

Please help me to cleanup space and recover installation. Thank you!

[2025-08-05T00:26:31+0200] [ALPM] running '80-cronie.hook'...
[2025-08-05T00:26:31+0200] [ALPM] running '90-mkinitcpio-install.hook'...
[2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img
[2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.12.41-1-lts'
[2025-08-05T00:26:32+0200] [ALPM-SCRIPTLET]   -> Running build hook: [base]
...
[2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2025-08-05T00:26:33+0200] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/13-dm-disk.rules': No space left on device
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/95-dm-notify.rules': No space left on device
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/11-dm-initramfs.rules': No space left on device
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/ossl-modules/legacy.so': No space left on device
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] install: error writing '/tmp/mkinitcpio.evH3PB/root/hooks/encrypt': No space left on device
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2025-08-05T00:26:34+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/pdata_tools': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/11-dm-lvm.rules': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/bin/dmsetup': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/usr/lib/udev/rules.d/13-dm-disk.rules': No space left on device
...
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/twofish_common.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/aegis128.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_raid6_recov.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/sm4-aesni-avx-x86_64.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/curve25519-x86_64.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast6_generic.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast_common.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/hctr2.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/hid/hid-generic.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/ecrdsa_generic.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/cdrom/cdrom.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/intel/iaa/iaa_crypto.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/nvme/host/nvme.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/wp512.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-raid.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/chelsio/chcr.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/scsi/virtio_scsi.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/fcrypt.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cast5_generic.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-mod.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/aegis128-aesni.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/des3_ede-x86_64.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/crc32c-intel.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-thin-pool.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/camellia-x86_64.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_pq.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/xxhash_generic.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/vmac.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/raid456.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/crypto_null.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/async_tx/async_xor.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/nvme/host/nvme-core.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cryptd.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/sm4_generic.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/cmac.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/xcbc.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/blake2b_generic.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/arch/x86/crypto/sm3-avx-x86_64.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/md/dm-region-hash.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/drivers/crypto/padlock-sha.ko.zst': No space left on device
[2025-08-05T00:26:35+0200] [ALPM-SCRIPTLET] cp: error writing '/tmp/mkinitcpio.evH3PB/root/lib/modules/6.12.41-1-lts/kernel/crypto/geniv.ko.zst': No space left on device
...
[2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/arch/x86/crypto/des3_ede-x86_64.ko.zst: Invalid argument
[2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/crypto/seqiv.ko.zst: Invalid argument
[2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/input/keyboard/applespi.ko.zst: Invalid argument
[2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/fs/smb/common/cifs_arc4.ko.zst: Invalid argument
[2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/mfd/max14577.ko.zst: Invalid argument
[2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/drivers/vfio/vfio.ko.zst: Invalid argument
[2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.qT6HiW/root/lib/modules/6.15.9-arch1-1/kernel/fs/zonefs/zonefs.ko.zst: Invalid argument
[2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] depmod: ERROR: Could not create index 'modules.dep'. Output is truncated: No space left on device
[2025-08-05T00:26:57+0200] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
[2025-08-05T00:26:58+0200] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2025-08-05T00:26:58+0200] [ALPM] running 'dbus-reload.hook'...
[2025-08-05T00:26:58+0200] [ALPM] running 'detect-old-perl-modules.hook'...
[2025-08-05T00:26:59+0200] [ALPM-SCRIPTLET] WARNING: '/usr/lib/perl5/5.40' contains data from at least 1 packages which will NOT be used by the installed perl interpreter.
[2025-08-05T00:26:59+0200] [ALPM-SCRIPTLET]  -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/5.40'
[2025-08-05T00:26:59+0200] [ALPM] running 'fontconfig.hook'...
[2025-08-05T00:26:59+0200] [ALPM] running 'fontconfig-32.hook'...
[2025-08-05T00:27:00+0200] [ALPM] running 'gdk-pixbuf-query-loaders.hook'...
[2025-08-05T00:27:00+0200] [ALPM] running 'ghc-register.hook'...
[2025-08-05T00:27:13+0200] [ALPM] running 'glib-compile-schemas.hook'...
[2025-08-05T00:27:13+0200] [ALPM] running 'gtk-update-icon-cache.hook'...
[2025-08-05T00:27:14+0200] [ALPM] running 'texinfo-install.hook'...
[2025-08-05T00:27:16+0200] [ALPM] running 'update-desktop-database.hook'...
[2025-08-05T00:27:16+0200] [ALPM] running 'xorg-mkfontscale.hook'...
[2025-08-05T00:27:18+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2025-08-05T00:27:18+0200] [PACMAN] synchronizing package lists
[2025-08-05T00:27:21+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2025-08-05T00:27:21+0200] [PACMAN] synchronizing package lists
[2025-08-05T00:27:24+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2025-08-05T00:27:24+0200] [PACMAN] synchronizing package lists
[2025-08-05T00:27:27+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2025-08-05T00:27:27+0200] [PACMAN] synchronizing package lists
[2025-08-05T00:28:00+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2025-08-05T00:28:00+0200] [PACMAN] synchronizing package lists
[2025-08-05T00:29:00+0200] [PACMAN] Running 'pacman -S -y --config /etc/pacman.conf --'
[2025-08-05T00:29:00+0200] [PACMAN] synchronizing package lists
11
  • So were you prompted for password or anything to unlock the drive before the errors was shown? Sounds like your bootloader config has somehow gone bad and doesn't pass anything as the "crypt device" to the early init? Commented Aug 5 at 8:32
  • 1
    Btw, anyone on Arch (or even in general) should keep (regularly updated) installation medium with them, which can be used for investigation / rescue purpose on broken system. Commented Aug 5 at 8:38
  • @TomYan : thank you! how would i do create an installation medium? as a normal archlinux user i've never stumbled over this subject -- untul now d-: Commented Aug 5 at 8:51
  • @TomYan : no, i'm thrown out of the booting process before entering the decription password. Commented Aug 5 at 8:52
  • 1
    Make sure that you are checking the right location (your installation mounted on e.g. /mnt instead of the live environment), especially if you haven't chrooted yet. Also make sure you have everything mounted in proper order (the root filesystem first, and /boot and other filesystems, if any). And if it's really wrong, arch-chroot and have it fixed, and run mkinitcpio -P to regen the initramfs. (Again, make sure you have /boot mounted beforehand if it has a dedicated filesystem. Be aware of the "location difference / change" of things before and after chroot.) Commented Aug 5 at 13:51

1 Answer 1

2

According to your blkid output, your /dev/sdb2 is encrypted with LUKS.

In your boot errors listing, there is no mention of any attempt to unlock the encryption. Did you forget to add the necessary hooks to mkinitcpio.conf for unlocking the encryption when executing initramfs? See Arch Wiki for details.

From the error messages and the blkid output, it looks like you might have a "LVM-on-LUKS" disk configuration. In that case, if the initramfs doesn't succeed in unlocking the LUKS encryption, the LVM volumes won't become accessible, and so the root filesystem cannot be mounted, and the boot will crash into emergency shell mode. That would explain all the error messages you're shown.

If the kernel was updated, your bootloader should still have the option to boot with the previous kernel and its initramfs file: those should still be there untouched by the update, just not as the default boot option.

So: reboot, and check your bootloader menus for the available kernel versions, and try booting with the second-newest one if possible. If that boots successfully, you'll need to rebuild the initramfs for the newest kernel and figure out what went wrong with it: maybe it's missing the hooks that would allow it to prompt for the LUKS passphrase, or maybe something is now wrong with cryptsetup or the initramfs scripting required to get the encryption unlocked?

Don't overwrite the initramfs of the second-newest kernel before you know for sure what went wrong with the initramfs of the newest kernel and have it fixed: currently it should still hold the known-working version of the cryptsetup tools and LUKS unlock scripting from before the upgrade.

5
  • 1
    your bootloader should still have the option to boot with the previous kernel and its initramfs file Arch. Commented Aug 5 at 8:29
  • @telcoM: thank you very much! so i haven't change anything in the configuration. i updated and rebooted, nothing else -- the standard procedure since i've instaled archlinux in 2021. now i've backedup the whole drive where the installation and encrypted partitions are (with # dd if=/dev/sdX of=/media/USER/EXTERNAL-HDD and i'm ready to try experimenting. Commented Aug 5 at 8:46
  • @TomYan : thank you! how to i initiate a boot with the previous kernel and its initramfs file? Commented Aug 5 at 8:48
  • @telcoM : can you please describe how to add the necessary hooks to mkinitcpio? i've tried to find the file, but i'm not able to find it from the emergecy shell. alternatively and/or additionally. how to boot from the previous kernel and its initramfs? Commented Aug 5 at 8:57
  • How to initiate a boot with the previous kernel depends on which bootloader you're using. Regarding the hooks for mkinitcpio, you'll first need to get the system booted into a more normal state; then, see the Arch Wiki link in my answer above. Basically, the HOOKS= line should be HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block encrypt lvm2 filesystems fsck): you seem to be missing encrypt and lvm2. Commented Aug 5 at 15:34

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.