my storage domains are GlusterFS. I will boot in rescue to see the LVM version on the VMs
Yet, the 2 VMs I tested with, have a different LVM version (EL7 vs EL8).
When I "ls" from the grub rescue I see only:
(hd0) ) (hd0,msdos2) (hd0,msdos1) (md/boot)
As only hd0 is visible (I have 10 disks and at least 4 in the device.map), this indicates
to me that it is the problem the colleagues from Proxmox has hit. Now I'm wondering
how to bypass it , so I can power up the RHEL8 VM.
Strahil Nikolov В петък, 7 януари 2022 г., 13:33:01 Гринуич+2, Vojtech Juranek
I recently migrated from 4.3.10 to 4.4.9 and it seems that booting from
software raid0 (I have multiple gluster volumes) is not possible with
Cluster compatibility 4.6 . I've tested creating a fresh VM and it also
suffers the problem. Changing various options (virtio-scsi to virtio,
chipset, VM type) did not help . Booting from rescue media shows that the
data is still there, but grub always drops to rescue. Any hints are
Host: CentOS Stream 8 with qemu-6.0.0oVirt 4.4.9 (latest)VM OS:
RHEL7.9/RHEL8.5 Best Regards,Strahil Nikolov
What is the lvm version? There was recently issue  with specific lvm version
(lvm2-2.03.14-1.el8.x86_64) which could cause boot failures.