For quite some time I have had the issues dual booting that /boot/efi partition being only 100 MB filled up pretty quickly dual booting between Windows and keeping 2 or 3 kernels, so I decided to face the challenge of enlarging /boot/efi partition, I did it pretty much following this guide: https://superuser.com/questions/1230741/how-to-resize-the-efi-system-partition, which at the beginning I tried to use the gparted method, which failed as it did to most, then I used the space that was already freed and put in the ESP (but not allocated) to format the new partition, after that I changed the uuid and ran grub2-mkconfig with chroot from gparted live USB and upon rebooting everything went well and fedora opened.
The reason I did that is also because one time I accidentally turned off my pc during a windows update thinking stupidly it was over, after that bootmgrw.efi in /boot/efi/EFI/Microsoft disappeared and through a USB with win11 I managed to restore it through bcdboot, it went well and I could get back in windows fully functioning, but when I tried to re do the download something went wrong again and I remembered that prior to that in fedora the /boot/efi partition was full with 0 bytes remaining, so I thought that this probably would be the issue.
I did the bcdboot process again and for some time I went without updating win11, every time I did the bcdboot process after getting back to fedora and generating grub2-mkconfig file it all went smooth and the boot menu appeared after the generation.
This time though after enlarging ESP and restoring bootmgwr.efi and changing the uuid in /etc/fstab, first of all when I first ran the mkconfig it looked like just the Windows entry was generated, not giving any other message about linux kernels even though they were present in /boot/loader/entries directory. After setting: GRUB_ENABLE_BLSCFG=“false”
the mkconfig successfully sees and generates in theory all of the entries, however the boot menu still doesnt appear during boot, the timeout is already set to 20 as it was already before the issues happened as well as timeout_style=menu, I unset auto_hide_menu env variable from grub2-editenv and upon boot pressing shift key doesnt force the menu to appear, pressing the ESC key makes a bunch of terminal-like lines appear with [ OK ] at the end, I dont know what else to do:
/etc/default/grub
yeah you’re right I worded it badly, I didn’t mean that the linux kernels were occupying all the space in /boot/efi, but still the files in it were too big and taking all of the 100 MB, the biggest ones were Microsoft/Boot and /boot/efi/EFI/fedora, but also on /boot/efi/EFI/Linux the .efi files were taking very much space, in fact now that it is enlarged, with 2 kernels Linux folder is weighing a massive 203 MB, that behaviour doesn’t seem normal since you hold 4 kernels + windows easily.
These are the files that I have in there, prior to the enlarging I arrived to keeping only 1 kernel, which was weighing around 50 MB if I remembered correctly
Very interesting. These look like UKIs (Unified Kernel Images), though I’m not sure what would make those appear on a normal Fedora desktop edition. (I believe the Fedora Cloud server editions use them to some extent.)
That looks like you installed some kernel packages you don’t need. For example kernel-uki-virt.x86_64 and kernel-debug-uki-virt.x86_64 is some test packages for testing uki kernels on virtual machines.
I actually have those packages installed, I have no idea how they finished there, are they included in some general purpose kernel package? So I am just safe to sudo dnf removing them right?
Interesting, your first-choice default boot is supposed to be into Fedora GRUB (0001) but in your current session you booted into the UKI image (BootCurrent is 0000), bypassing GRUB.
I would be inclined to try efibootmgr --delete-bootnum 0000 so that the only Fedora item there is the EFI that loads GRUB.
Mh, that is interesting, the boot 0 has been the default option since know, when I pasted @anotheruser answer to claude to check which partuuid he was talking about (because I already updated the one in /etc/fstab before this thread, so I wanted to double check if I missed one) Claude gave me this command: sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -L "Fedora" -l '\EFI\fedora\shimx64.efi
Which when I executed it created this entry, so I’m gonna try to do that, should I also run grub2-mkconfig -o /boot/grub2/grub.cfg?
Upon rebooting, it jumps me directly to windows Lol, so that boot entry is not working properly, I guess now I have to write a live USB to boot back in fedora right?