Is there a way to fix Grub in Fedora?
EFI + grub2-install don’t go well, I one can trust the red box in the Fedora wiki article. So I installed grub2-efi, created a new config file (just to be sure) and the boot was fixed! (grub2-efi will install a proper version of grubx64.efi which loads the GRUB config from the correct location.
Why is my Fedora bootloader not loading Grub?
(grub2-efi will install a proper version of grubx64.efi which loads the GRUB config from the correct location. The grubx64.efi generated by the grub2-install command tried to load the config from a file that did not exist and therefore caused the issue with the grub> command line.)
Where do I find the GRUB 2 configuration file?
The GRUB 2 configuration file, grub.cfg, is generated during installation, or by invoking the /usr/sbin/grub2-mkconfig utility, and is automatically updated by grubby each time a new kernel is installed.
Why is grub.cfg called initrd in Fedora?
This directive is called initrd because the previous tool which created initial RAM disk images, mkinitrd, created what were known as initrd files. The grub.cfg directive remains initrd to maintain compatibility with other tools.
What should I do if I forgot to install GRUB2 EFI x64?
Run this command to reinstall all the important boot related packages that were removed by accident: And that’s basically it! Your system should be fine, again. Exit the chroot, unmount all the drives and reboot: Though, when I was busy with my repair, I obviously missed to install grub2-efi-x64 so I ended up with this message after a reboot:
What to do when you get error message when installing Fedora?
If you get an error message saying that the target is busy, change your working directory to outside the mount (for example, / ). The log files from the installation are now saved on the USB flash drive. On the system you are installing, press Ctrl + Alt + F2 to access a shell prompt.