[SOLVED] LVM broken after update: Can't find volume group and can't find pve-root

[TheFuzzyFish]

So I did a routine update yesterday. I noticed that some system packages were available for updates, particularly the pve-kernel 4.15.15-6 (at least, I think it was 4.15.15-6. But when I went onto a testing PVE, the update lists it as 4.15.15-1. I'm not sure anymore, and I can't check because it won't boot properly).

I rebooted after the update, and suddenly it won't start. It complains a whole bunch about the pve volume group not being found, then the pve-root logical volume not being found (the server is configured with LVM), followed by repeated errors of kworker and udev timing out after 120 seconds. Not really sure what to make of it. Did I accidentally screw something up?

I currently have the system booted from the installation rescue disk, so it's running under kernel 4.13.16-2. I'd like to make it apparent that my file system is still intact, nothing is missing. I still have my volume group, and I still have my logical volumes. For some reason, LVM just isn't starting properly, so the system can't properly boot with the root filesystem.
I've tried adding root-delay to my grub configuration file, but no dice.
I'm honestly just not sure if this is my fault, or if this is an actual bug with the update.

I updated from the pve-no-subscription repository. Unforunately, I don't have before/after logs of what exactly updated, but here is my current list of package versions while it's running under the rescue disk:

proxmox-ve: 5.1-43 (running kernel: 4.13.16-2-pve)
pve-manager: 5.1-52 (running version: 5.1-52/ba597a64)
pve-kernel-4.13: 5.1-44
pve-kernel-4.15: 5.1-3
pve-kernel-4.15.15-1-pve: 4.15.15-6
pve-kernel-4.13.16-2-pve: 4.13.16-47
pve-kernel-4.13.16-1-pve: 4.13.16-46
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-2-pve: 4.13.13-33
pve-kernel-4.13.13-1-pve: 4.13.13-31
pve-kernel-4.13.8-3-pve: 4.13.8-30
pve-kernel-4.13.8-2-pve: 4.13.8-28
pve-kernel-4.13.8-1-pve: 4.13.8-27
pve-kernel-4.13.4-1-pve: 4.13.4-26
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-30
libpve-guest-common-perl: 2.0-15
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-19
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-2
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-15
pve-cluster: 5.0-26
pve-container: 2.0-22
pve-docs: 5.1-17
pve-firewall: 3.0-8
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-3
qemu-server: 5.0-25
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.7-pve1~bpo9​

 

[martin]

Can you test with latest kernel?

See https://forum.proxmox.com/threads/4...or-pve-5-x-available.42097/page-4#post-208402

 

[TheFuzzyFish]

Can you test with latest kernel?

See https://forum.proxmox.com/threads/4...or-pve-5-x-available.42097/page-4#post-208402

I'll need to get back to you in a few hours. I'm not home at the moment.

 

[TheFuzzyFish]

Can you test with latest kernel?

See https://forum.proxmox.com/threads/4...or-pve-5-x-available.42097/page-4#post-208402

YES! The update to 4.15.17-1-pve fixed the problem. Everything is booting fine now, my VMs are fully functional, and I'm not noticing any problems. Thank you!