You are not logged in.
My system which using lts 6.18.x and bootctl which -not sure exact version- installed using following command almost 6 months ago.
pacstrap -K /mnt base base-devel linux-lts linux-firmware linux-lts-headers amd-ucode lvm2 initramfs networkmanager mkinitcpio vim dhcpcd openssh man-db reflectorI've updated yesterday then tries to fall emergency shell but can't fall emergency shell...
[ OK ] Finished Early Battery Level Check.
[ OK ] Started Display Boot-Time Emergency Messages in Full Screen.
[ OK ] Stopped Virtual Console Setup.
[ OK ] Starting Virtual Console Setup...
[ OK ] Finished Virtual Console Setup.
[ OK ] Found device WDC PC SN530 SDBPNPZ-512G-1827 Linux LVM.
Starting Cryptography Setup for cryptlvm...
Please enter passphrase for disk Linux LVM (cryptlvm):
[ OK ] Finished Cryptography Setup for cryptlvm.
[ OK ] Reached target Local Encrypted Volumes.
[ OK ] Reached target System Initialization.
[ OK ] Reached target Basic System.
[ TIME ] Timed out waiting for device /dev/MyVolGroup/root.
[DEPEND] Dependency failed for /sysroot.
[DEPEND] Dependency failed for Initrd Root File System.
[DEPEND] Dependency failed for Mountpoints Configured in the Real Root.
[DEPEND] Dependency failed for Initrd Root Device.
[DEPEND] Dependency failed for File System Check on /dev/MyVolGroup/root.
[ OK ] Stopped target Basic System.
[ OK ] Reached target Initrd File Systems.
[ OK ] Stopped target System Initialization.
[ OK ] Started Emergency Shell.
[ OK ] Reached target Emergency Mode.
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs,
"systemctl reboot" to reboot, or "exit" to continue bootup.
Cannot open access to console; the root account is locked.
See sulogin(8) man page for more details.
Press Enter to continue.
Reloading system manager configuration...
Starting initrd.target...
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs,
"systemctl reboot" to reboot, or "exit" to continue bootup.
Cannot open access to console; the root account is locked.
See sulogin(8) man page for more details.
Press Enter to continue.After trying to load disks with an arch iso then try generate mkinitcpio or glance it,
cryptsetup open /dev/nvme0np2 cryptlvm
PASSPHRASE:********works
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /rofs
sda
├─sda1 exfat 1.0 Ventoy B928-3191
└─sda2
nvme0n1
├─nvme0n1p1 vfat FAT32 3609-C3E8
└─nvme0n1p2 crypto_LUKS 2 7495a2bf-0498-4c25-a940-84d7309c1aa6
└─cryptlvmlvmdiskscan
/dev/mapper/cryptlvm [ 475.92GiB]
/dev/loop0 [ <846.72MiB]
/dev/sda1 [ 57.27GiB]
/dev/sda2 [ 32.00MiB]
/dev/nvme0n1p1 [ 1.00GiB]
/dev/nvme0n1p2 [ 475.94GiB]
1 disks
5 partitions
0 LVM pysical volume whole disks
0 LVM pysical volumesCan I access console or disk content?
#ls /dev/mapper
control cryptlvm ventoy
#mount /dev/mapper/MyVolGroup/root /mnt
mount: /mnt: fsconfig() failed: /dev/mapper/MyVolGroup/root: Can't lookup blockdev.
dmesg(1) may have more information after failed mount system call.Last edited by maxemilian (2026-07-25 17:08:42)
Offline
What does pvscan output ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I've removed quit and splash parameters and updated above emergency error.
root@archiso /boot # nano loader/entries/arch.conf
"loader/entries/arch.conf" 37L, 1183B written
root@archiso /boot # hexdump -C /dev/mapper/cryptlvm | head
00000000 c6 fd ae ae 90 40 00 18 f9 fa f9 b1 c2 ff fb b9 |.....@..........|
00000010 9b 18 18 18 83 02 8c fb 54 4c 06 de f4 0c cf 84 |........TL......|
00000020 8d f6 d1 e3 02 84 4b d3 37 7f 0a 53 f9 9e db 50 |......K.7..S...P|
00000030 18 18 18 18 74 12 ac 6e ae 5c 4a 94 d6 10 64 4e |....t..n.\J...dN|
00000040 b5 84 b6 4a 8d fa 58 87 cc 23 a6 e4 bd d7 d8 47 |...J..X..#.....G|
00000050 61 41 b6 f9 82 a8 de c1 98 02 94 bf 84 91 41 ce |aA............A.|
00000060 d9 96 bc 3e e6 9f 0c b2 df |...>.....|What does pvscan output ?
root@archiso /boot # pvscan
No matching physical volumes found.ls -la /dev/mapper/
total 0
drwxr-xr-x 2 root root 80 Jul 25 17:18 .
drwxr-xr-x 19 root root 4400 Jul 25 17:18 ..
crw------- 1 root root 10, 236 Jul 25 16:47 control
lrwxrwxrwx 1 root root 7 Jul 25 17:18 cryptlvm -> ../dm-1Last edited by maxemilian (2026-07-25 17:21:02)
Offline
I've updated yesterday
First time since when?
Did you cross the switch from busybox to systemd?
https://bbs.archlinux.org/viewtopic.php?id=310004
Offline
I've updated yesterday
First time since when?
Did you cross the switch from busybox to systemd?
https://bbs.archlinux.org/viewtopic.php?id=310004
I've been updating in two weeks(at most in a month) regularly and reboot. Maybe before LTS 6.18.x i've using LTS 6.12.x as first kernel then it automatically passed to the latest 6.18.x LTS. I didn't exactly remember system lifetime btw. At least 6 months old. Uptime was ~11 days.
Never used busybox/init just systemd on the pc. At most installed docker -crops/poky/qemux86-64 sth like things.
cat arch.conf
title Arch Linux LTS
linux /vmlinuz-linux-lts
initrd /amd-ucode.img
initrd /initramfs-linux-lts.img
options rd.luks.name=7495a2bf-0498-4c25-a940-84d7309c1aa6=cryptlvm rd.luks.options=discard root=/dev/MyVolGroup/root rw loglevel=3 systemd.show_status=auto rd.udev.log_level=3 8250.nr_uarts=0 amdgpu.dc=1 udev.settle_timeout=10 nvme_core.io_timeout=30 pcie_aspm=defaultand
pwd && tree
/boot
.
├── EFI
│ ├── BOOT
│ │ └── BOOTX64.EFI
│ ├── Linux
│ └── systemd
│ └── systemd-bootx64.efi
├── amd-ucode.img
├── initramfs-linux-lts.img
├── loader
│ ├── entries
│ │ └── arch.conf
│ ├── entries.srel
│ ├── keys
│ ├── loader.conf
│ └── random-seed
└── vmlinuz-linux-ltsEDIT:
I've tracked myself back and found.
This is my latest problem with zen kernel
I had similar problem with zen kernel then I got fresh start with the LTS kernel for overall -LVM2- stability.
ls -la loader/entries/arch.conf
-rwxr-xr-x 1 root root 371 Jul 25 16:40 loader/entries/arch.confpossibly the Jul 25 date is correct.
Last edited by maxemilian (2026-07-25 20:56:05)
Offline
So you can open the container but there's no LVM… ![]()
head -c8K /dev/mapper/cryptlvm | hexdump -C(LVM header is the second 512 bytes, let's just look at the 1st 8K whether it's anywhere there)
Offline