On Sat, May 16, 2020 at 1:03 AM <bjkelley@us.ibm.com> wrote:

Trying to use my dell 2850 as ovirt node the install does not show the raid0 disk pair that ovirt-node-4.3.9 was able to use as install destination. The Installer shows no disk at all in system it has 6 seen by 4.3.9.

Thanks Bryan

Hi, oVirt 4.4. is based on CentOS 8, where megaraid_sas driver (the one driving PERC5) has been removed, being a rebuild of Red Hat 8: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/htm... You can try install using DUD method: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/htm... providing the megaraid_sas dd-megaraid_sas-07.707.51.00-1.el8_1.elrepo.iso from elrepo: https://elrepo.org/linux/dud/el8/x86_64/ When you complete your install before rebooting you can switch to Ctrl+Alt+F2 and go to a shell to verify some things chroot /mnt/sysimage lsinitrd /boot/initramfs-4.18.0-147.8.1.el8_1.x86_64.img | grep megaraid --> you should see the megaraid_sas module listed and also, as oVirt actually starts the initrd image under the layer, you should have an identical copy of the initrd here: lsinitrd /boot/ovirt-node-ng-4.4.0-0.20200506.0+1/initramfs-4.18.0-147.8.1.el8_1.x86_64.img | grep megaraid ---> you should see the megaraid_sas module listed if all is ok, you can exit the chroot environment, then Ctrl+Alt+F6 to come back to the graphical installer and click the reboot button and see if it is correctly seen by the os at restart. It works with plain CentOS 8, not tried with oVirt, but one guy reported he had problem at reboot: the system went into a dracut emergency shell not seeing the disk and so the LVM structures needed for proper start. You could try and report. Keep in mind that in case of deployment of the 4.4. GA you would have the same problem and also during upgrades. HIH, Gianluca