running update-grub suddenly started failing to detect other LVs: ( all LVs used to get activated automatically on boot )
LVM:LSBLK:a workaround is a manual activation before running update-grub ( this was not required before )troubleshooting done:
i have downgraded the recently updated util-linux package back to:recreated all the initramfs ( should recreate just one )
no improvement after rebooting only the main/booted linvg LVs are active, update-grub fails
there is no recent changes applied that I'm aware of that could influence the way update-grub "detects" the filesystems, or LVM scan/activation during boot.
Other than util-linux, gcc, and and 6.1.0-20-amd64 kernel update applied recently...
booting the older kernels results in the same problem ( but, i've recreated all initramfs's - by mistake - making the comparison between kernels and the boot process invalid )
i do not remember seeing update-grub/lsblk failing like this before before
thanks all!
Code:
deb10 ~ # update-grubGenerating grub configuration file ...Found linux image: /boot/vmlinuz-6.1.0-20-amd64Found initrd image: /boot/initrd.img-6.1.0-20-amd64Found linux image: /boot/vmlinuz-6.1.0-18-amd64Found initrd image: /boot/initrd.img-6.1.0-18-amd64Found linux image: /boot/vmlinuz-6.1.0-17-amd64Found initrd image: /boot/initrd.img-6.1.0-17-amd64Found linux image: /boot/vmlinuz-6.1.0-10-amd64Found initrd image: /boot/initrd.img-6.1.0-10-amd64Found linux image: /boot/vmlinuz-6.1.0-9-amd64Found initrd image: /boot/initrd.img-6.1.0-9-amd64Adding boot menu entry for UEFI Firmware Settings ...Found memdisk: /memdiskImagepath /boot/images not foundWarning: os-prober will be executed to detect other bootable partitions.Its output will be used to detect bootable binaries on them and create new boot entries.lsblk: /dev/mapper/spvg1-root: not a block devicelsblk: /dev/mapper/spvg1-var: not a block devicelsblk: /dev/mapper/vg1-root: not a block devicelsblk: /dev/mapper/vg1-varlog: not a block deviceFound Windows Boot Manager on /dev/nvme1n1p1@/EFI/Microsoft/Boot/bootmgfw.efidonedeb10 ~ # uname -aLinux deb10 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 GNU/Linuxdeb10 ~ #
Code:
deb10 ~ # vgs VG #PV #LV #SN Attr VSize VFree linvg 1 3 0 wz--n- 171.82g <16.20g spvg1 1 2 0 wz--n- <100.47g <51.47g vg1 1 2 0 wz--n- 666.63g 259.91gdeb10 ~ # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert linlog linvg -wi-ao---- 4.00g linroot linvg -wi-ao---- 139.62g rootsrc linvg -wi-a----- 12.00g root spvg1 -wi------- 45.00g var spvg1 -wi------- 4.00g root vg1 -wi------- 403.00g varlog vg1 -wi------- 3.72g
Code:
deb10 ~ # lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTSnvme1n1 259:0 0 1.8T 0 disk ├─nvme1n1p1 259:1 0 500M 0 part /boot/efi├─nvme1n1p2 259:2 0 892.8G 0 part ├─nvme1n1p3 259:3 0 863M 0 part ├─nvme1n1p4 259:4 0 787G 0 part ├─nvme1n1p5 259:5 0 10G 0 part /boot└─nvme1n1p6 259:6 0 171.8G 0 part ├─linvg-linroot 254:2 0 139.6G 0 lvm / ├─linvg-linlog 254:5 0 4G 0 lvm /var/log └─linvg-rootsrc 254:6 0 12G 0 lvm nvme0n1 259:7 0 1.8T 0 disk ├─nvme0n1p1 259:8 0 10G 0 part ├─nvme0n1p2 259:9 0 666.6G 0 part ├─nvme0n1p3 259:10 0 512M 0 part ├─nvme0n1p4 259:11 0 100.5G 0 part ├─nvme0n1p5 259:12 0 299M 0 part └─nvme0n1p6 259:13 0 16M 0 part
Code:
deb10 ~ # vgchange -ay 2 logical volume(s) in volume group "spvg1" now active 2 logical volume(s) in volume group "vg1" now active 3 logical volume(s) in volume group "linvg" now active
i have downgraded the recently updated util-linux package back to:
Code:
util-linux-extra_2.38.1-5+b1_amd64.debutil-linux-locales_2.38.1-5_all.debutil-linux_2.38.1-5+b1_amd64.deb
no improvement after rebooting only the main/booted linvg LVs are active, update-grub fails
there is no recent changes applied that I'm aware of that could influence the way update-grub "detects" the filesystems, or LVM scan/activation during boot.
Other than util-linux, gcc, and and 6.1.0-20-amd64 kernel update applied recently...
booting the older kernels results in the same problem ( but, i've recreated all initramfs's - by mistake - making the comparison between kernels and the boot process invalid )
i do not remember seeing update-grub/lsblk failing like this before before
thanks all!
Statistics: Posted by ksu — 2024-04-14 15:27 — Replies 1 — Views 42