Bug#980782: Info received (Bug#980782: Acknowledgement (os-prober: linux-boot-prober returning "root=/dev/dm-X" line instead of expected "root=UUID=[UUID128]))

Mirko Vogt writes: > Looking at /usr/share/initramfs-tools/scripts/local-top/lvm2 more > closely, passing a UUID also wouldn't trigger a `vgchange -ay` here. > But a path like /dev/mapper/X would. > So maybe the question is rather: how to make os-prober return a > "root=/dev/mapper/X" line

Bug#980782: Info received (Bug#980782: Acknowledgement (os-prober: linux-boot-prober returning "root=/dev/dm-X" line instead of expected "root=UUID=[UUID128]))

Looking at /usr/share/initramfs-tools/scripts/local-top/lvm2 more closely, passing a UUID also wouldn't trigger a `vgchange -ay` here. But a path like /dev/mapper/X would. So maybe the question is rather: how to make os-prober return a "root=/dev/mapper/X" line instead of one containing a

Bug#980782: Acknowledgement (os-prober: linux-boot-prober returning "root=/dev/dm-X" line instead of expected "root=UUID=[UUID128])

Just adding, this isn't only a feature request but results in non-bootable systems. If one of the os-probe'd systems e.g. is also a Debian, it will drop into an initramfs due to not finding the root device. This is due to - within the initramfs - the VGs as part of the the LVM system only get