Unfortunately, this bug is still alive. Here’s the workaround update for Silverblue 31:
chroot /mnt/sysimage/ostree/deploy/fedora/deploy/<deploy_id>.0 /bin/sh
mv /boot/efi/EFI/EFI/BOOT/* /boot/efi/EFI/BOOT/
mv /boot/efi/EFI/EFI/fedora /boot/efi/EFI/
rm -r /boot/efi/EFI/EFI
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
This is a real pain. I’m not even able to do the workaround since my keyboard is bluetooth one and we have no bluetooth here in Anaconda!
So let’s please file this bug in the end if it wasn’t already. Anyone aware of the situation?
PS: also, the installer seem doesn’t allow to continue the installation, so not sure if workaround is enough…
Apparently, there are a lot of this bug reports already, starting from 2017, but the bug is still there:
Ok I found the issue and provided the fix:
Not sure why is should had to take 3 years if one is really care…
Wow! Just that to solve an x-years problem?!
Silly, yeah? Actually, I’m just going to test it
Did you test it with Fedora Silver Blue 31? Did you test dual boot with Windows?
Hi, I’m testing right now. Still see the problem with the
grub error, but maybe it’s because I’m trying to reinstall Fedora to itself. Will see.
Anyway, the patch above is for sure necessary. Maybe it just not enough
How are you testing it? Is it just changing an installation script?
Maybe I can test on my secondary machine.
I’m testing on Virtualbox. Yes the file being patched is writable so anyone can try too.
patch util is absent
The grub error seems occurs only when grub.cfg was present somewhere in /EFI/… on ESP before. If it’s not the case - install should finish flawlessly with the patched script (and hopefully boot).
Would it work with Systemd-Boot?
I hope so. But grub supports BLS also, so not a real problem
Nope, I just installed normal Fedora. Too many problems with silverblue…
It is sort of the issue when using something new, not everything has come together for every use case equally. On the upside, you’re still a Fedora user!
Yes, I love fedora since years, and I love the Silverblue concept, but you know, it’s a workstation and I need things working…
I guess I’ll try again after one or 2 versions if it’s more stable.
Systemd-Boot works but you’ll have to tune it’s .conf files manually after every rpm-ostree upgrade. This is due OSTree doesn’t support Systemd-Boot yet, unfortunately.
So for now I came up with default Grub BLS solution, which works rather good also.