You are not logged in.
I'm duplicating here this topic from artix forum as the same problem occurs also on arch.
I installed a fresh arch linux on lvm over luks. My boot and swap are on regular logical volumes and root is on thinly provisioned volume.
my mkinitcpio.conf:
MODULES=(i915 ext4)
FILES=(/path/to/my/crypto.key)
HOOKS=(base udev autodetect keyboard block encrypt lvm2 fsck)
Here is what I see at initramfs boot stage:
[ 0.282501] x86/cpu: SGX disabled by BIOS.
:: running early hook [udev]
Starting systemd-udevd version 252.5-1-arch
:: running hook [udev]
:: Triggering uevents...
:: running hook [keymap]
:: loading keymap...done.
:: running hook [encrypt]
Waiting 10 seconds for device /dev/matrix/archlinux ...
ERROR: device '/dev/matrix/archlinux' not found. Skipping fsck.
:: mounting '/dev/matrix/archlinux' on real root
mount: /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
Then in rescue shell I find that only boot and swap non-thin volumes are initialized but root and other thin volumes are not.
[rootfs ]# ls /dev/matrix
boot boot_snap boot_snap2 swap
[rootfs ]# lvm vgscan
Found volume group "matrix" using metadata type lvm2
[rootfs ]# lvm vgchange -y a matrix
Check of pool matrix/qubes_pool failed (status:64). Manual repair required!
Check of pool matrix/system_pool failed (status:64). Manual repair required!
4 logical volume(s) in volume group "matrix" now active
I don't know what status:64 means.
lsmod shows that all necessary kernel modules are loaded (dm_thin_pool module specifically).
I replicated this behaviour on artix with hardened kernel, artix with lts kernel and arch with standard kernel.
I also tried a few different and more general hooks/modules setup for mkinitcpio.conf without any effect.
I found this similar topic but It doesn't refer to initramfs boot stage and it was lvm2 bug that was fixed in version 2.02.177-5. I installed lvm2 version 2.03.18-4 and mkinitcpio 34-2
My thin pools and volumes are not corrupted because they initialize properly on another systems, like arch or artix live installation media for example.
Last edited by Feasuro (2023-02-14 16:02:57)
Offline
It' a bug in thin-provisioning-tools. Report on the issue: https://bugs.archlinux.org/task/77416
Offline