You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
The issue: the grubx64.efi resides under EFI/centos/ but installer configures uefi on EFI/fedora/shim.efi
On my system gigabyte j1900n d3v, it is possible to boot via usb3.0 and it works fine when configuring uefi after installation via efibootmgr. I have to chroot into /mnt/sysimage efibootmgr -v -c -L"Rockstor" -d /dev/sdc -p1 -l "EFI/centos/grubx64.efi"
Although i have to grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg
The Rockstor-Installer configures efibootmgr as:
EFI/fedora/shim.efi
which is not existing and failes to write grub config.
/EFI/BOOT/BOOTX64.EFI is existing as well but ignored by my board, dont know wy! The reason could be in booting from usb3.0. Debian/Centos/Gentoo/Arch isos are booting fine on USB3.0 I only wanted to tell you about the fedora bootentry which is not correct.
The text was updated successfully, but these errors were encountered:
The issue: the grubx64.efi resides under EFI/centos/ but installer configures uefi on EFI/fedora/shim.efi
On my system gigabyte j1900n d3v, it is possible to boot via usb3.0 and it works fine when configuring uefi after installation via efibootmgr. I have to chroot into /mnt/sysimage
efibootmgr -v -c -L"Rockstor" -d /dev/sdc -p1 -l "EFI/centos/grubx64.efi"
Although i have to grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg
The Rockstor-Installer configures efibootmgr as:
EFI/fedora/shim.efi
which is not existing and failes to write grub config.
/EFI/BOOT/BOOTX64.EFI is existing as well but ignored by my board, dont know wy! The reason could be in booting from usb3.0. Debian/Centos/Gentoo/Arch isos are booting fine on USB3.0
I only wanted to tell you about the fedora bootentry which is not correct.
The text was updated successfully, but these errors were encountered: