We have reinstalled two Proxmox 3.x machines to 4.3 and on both machines, after the install, they come up with this error when booting:
Loading, please wait...
Volume group "pve" not found
Cannot process volume group pve
Unable to find LVM volume pve/root
Gave up waiting for root device. Common problems:
...
ALERT! /dev/mapper/pve-root does not exist. Dropping to a shell!
Upon investigation, the volumes are inactive:
(initramfs) lvm
lvm> lvscan
inactive '/dev/pve/swap' [3.62 GiB] inherit
inactive '/dev/pve/root' [7.25 GiB] inherit
inactive '/dev/pve/data' [15.20 GiB] inherit
lvm> vgchange -a y pve
/sbin/modprobe failed: 1
Cannot read thin-pool target version.
Can't process LV data: thin-pool target support missing from kernel?
2 logical volume(s) in volume group "pve" now active
lvm> exit
Exiting.
(initramfs) exit
(The machines boot normally at this point. Until next boot, when the volumes are inactive again.)
The boot device for both is a small (32GiB) SATA SSD.
Is this a bug with 4.3? It has never occurred with any previous 3.x or 4.1 version on this same hardware. (We have four others just like these running 4.1 with no problem.)
Nothing unique or custom was done during the install.
Loading, please wait...
Volume group "pve" not found
Cannot process volume group pve
Unable to find LVM volume pve/root
Gave up waiting for root device. Common problems:
...
ALERT! /dev/mapper/pve-root does not exist. Dropping to a shell!
Upon investigation, the volumes are inactive:
(initramfs) lvm
lvm> lvscan
inactive '/dev/pve/swap' [3.62 GiB] inherit
inactive '/dev/pve/root' [7.25 GiB] inherit
inactive '/dev/pve/data' [15.20 GiB] inherit
lvm> vgchange -a y pve
/sbin/modprobe failed: 1
Cannot read thin-pool target version.
Can't process LV data: thin-pool target support missing from kernel?
2 logical volume(s) in volume group "pve" now active
lvm> exit
Exiting.
(initramfs) exit
(The machines boot normally at this point. Until next boot, when the volumes are inactive again.)
The boot device for both is a small (32GiB) SATA SSD.
Is this a bug with 4.3? It has never occurred with any previous 3.x or 4.1 version on this same hardware. (We have four others just like these running 4.1 with no problem.)
Nothing unique or custom was done during the install.