It seems that you are using EFI and something corrupted the installation.

The fastest approach is to delete the oVirt node from the UI, reinstall and readd it back via the UI.

I suspect something happened with your OS FS, but it could be a bug in the OS.

If it was a regular CentOS Stream system, I wiuld follow https://access.redhat.com/solutions/3486741

Best Regards,
Strahil Nikolov


On Tue, Mar 8, 2022 at 8:25, dean--- via Users
<users@ovirt.org> wrote:
Rebooting oVirt fails on a RAID array installed on a Cisco UCS C220 M5.  It fails using either legacy BIOS or UEFI with the error…

error: ../../grub-core/fs/fshelp.c:258:file `//ovirt-node-ng-4.4.10.1-0.20220202.0+1/vmlinuz-4.18.0-358.el8.x86_64’ not found.
Error: ../../grub-core/loader/i386/efi/linux.c:94:you need to load the kernel first.

Press any key to continue…

    Failed to boot both default and fallback entries.

Press any key to continue…


Any attempts to recover using the installation/rescue ISO also fails and locks up.


All Googled solutions I've tried so far have not worked.

Does anyone know how to prevent this from happening and the correct method to recover when it does?

Thanks!

... Dean
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UYCJWN4AZZRWDQ47VBA6K37T3W46OF32/