Upgrade from 7 to 8, system can't see boot volume

[gotadmin]

We've performed a number of the upgrades from 7 to 8 without issue, but we have one server where there is a problem. The upgrade seemed to go fine, but when it goes to boot into the 6.x kernel, it cannot see the LVM that has the boot volume on it. The grub loader loads fine. And it can see the storage LVM without issue which is a different disk and I believe a different controller in the system.

If we go into advanced options and boot into the 5.x kernel it sees the boot volume fine and comes up and VMs start.

I do not love the fact that we are running version 8 on a version 7 kernel and would like to see if we can resolve this but I don't know where to start on this.

Anyone have any thoughts on this or seen this before?

 

[Moayad]

Hi,

Could you please post the output of `/etc/fstab`?

 

[gotadmin]

Sure thank you!

# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
/dev/sda1 /satastorage ext4 defaults 0 0
/dev/sdc1 /ssdraid10 ext4 defaults 0 0

 

[gotadmin]

Also FWIW here is some more data. I should note that the boot in the 6.x kernel can see the raidlvm but it cannot see pve-root

root@x1:~# ls -alh /dev/disk/by-uuid/
total 0
drwxr-xr-x 2 root root 140 Jun 27 05:56 .
drwxr-xr-x 7 root root 140 Jun 27 05:56 ..
lrwxrwxrwx 1 root root 10 Jun 27 05:56 2142cf52-4cde-453b-9d70-5501a47c5332 -> ../../dm-3
lrwxrwxrwx 1 root root 10 Jun 27 05:56 a3772b0e-d07d-443d-ae5d-8a4ecedd5bbe -> ../../sda1
lrwxrwxrwx 1 root root 10 Jun 27 05:56 A946-A9D7 -> ../../sdd2
lrwxrwxrwx 1 root root 10 Jun 27 05:56 aeb5ad00-e902-4e39-9627-fd82560b73f0 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jun 27 05:56 b6755c64-e0c0-4d46-9bbc-ca26a42571f8 -> ../../dm-2

root@x1:~# ls -alh /dev/mapper/
total 0
drwxr-xr-x 2 root root 200 Jun 27 05:56 .
drwxr-xr-x 21 root root 4.4K Jun 27 06:27 ..
crw------- 1 root root 10, 236 Jun 27 05:56 control
lrwxrwxrwx 1 root root 7 Jun 27 05:56 pve-data -> ../dm-6
lrwxrwxrwx 1 root root 7 Jun 27 05:56 pve-data_tdata -> ../dm-5
lrwxrwxrwx 1 root root 7 Jun 27 05:56 pve-data_tmeta -> ../dm-4
lrwxrwxrwx 1 root root 7 Jun 27 05:56 pve-root -> ../dm-3
lrwxrwxrwx 1 root root 7 Jun 27 05:56 pve-swap -> ../dm-2
lrwxrwxrwx 1 root root 7 Jun 27 05:56 raidlvm-vm--100--disk--0 -> ../dm-0
lrwxrwxrwx 1 root root 7 Jun 27 05:56 raidlvm-vm--101--disk--0 -> ../dm-1

 

[Moayad]

May you try to use `nofail` and `_netdev` (see man fstab) on your lvm and boot from the latest Proxmox VE kernel?

 

[gotadmin]

I will give this a try, however, this client suffered a major outage this weekend and will be reluctant to engage in another reboot for a little while I think. So it may be a bit before we hear the results.