Package: lvm2
Version: 2.03.16-2
Some of our bookworm VMs reboots often were interrupted with panic "Gave
up waiting for root file system device.". rootfs stored on
LV /dev/mapper/myvg-root, system with two separate VGs. After manually
running "vgchange -ay" and "exit" in initramfs shell, booting was
finishing fine.
After turning on debug in
/usr/share/initramfs-tools/scripts/init-top/udev with
-SYSTEMD_LOG_LEVEL=$log_level /lib/systemd/systemd-udevd --daemon
--resolve-names=never
+/lib/systemd/systemd-udevd --debug --resolve-names=never >
/dev/.udev.debug 2>&1 &
and updating initramfs
update-initramfs -u -k `uname -r`
we noticed the following errors in /dev/.udev.debug after panic:
vda3: '/sbin/lvm vgchange -aay --autoactivation event myvg'(err) ' '
vda3: '/sbin/lvm vgchange -aay --autoactivation event myvg'(err)
'/dev/mapper/control: mknod failed: File exists'
vda3: '/sbin/lvm vgchange -aay --autoactivation event myvg'(err) ' '
vda3: '/sbin/lvm vgchange -aay --autoactivation event myvg'(err)
'Failure to communicate with kernel device-mapper driver.'
vda3: '/sbin/lvm vgchange -aay --autoactivation event myvg'(err) ' '
vda3: '/sbin/lvm vgchange -aay --autoactivation event myvg'(err)
'Check that device-mapper is available in the kernel.'
vda3: '/sbin/lvm vgchange -aay --autoactivation event myvg'(err) ' '
vda3: '/sbin/lvm vgchange -aay --autoactivation event myvg'(err)
'Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver
(unknown version).'
vda3: '/sbin/lvm vgchange -aay --autoactivation event myvg'(out) '
0 logical volume(s) in volume group "myvg" now active'
Patching LVM2 packages with
https://github.com/lvmteam/lvm2/commit/7e14835a46a6c9e66087d6502d23df53c2a9954f
resolved this issue for us.
Please fix it in bookworm.
--
Regards,
Paweł Bogusławski
E:pawel.boguslaw...@ib.pl
