Hi,
I was trying to install something onto my device. I edited some files following a tutorial, I didn't know what I was doing so I gave up the tutorial but when I rebooted now I cannot boot into fedora and it automatically boots into the bios.

I think the problem is with grub2 because before it lods the bios for 1 second it shows "error: ../../grub-core/commands/search.c:296:no such device:".

I've been trying to reinstall grep,following this tutorial https://gist.github.com/Tamal/73e65b...10c5fe81c5de14 and this https://docs.fedoraproject.org/en-US...-a-bios-system but whenever I try I get the message "/usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist".

I tried loading boot-repair-disk and this was the output.


I am using fedora 34.

Any help would be appreciated.

So you flat-out refuse to tell us what caused the problem initially, and expect us to come to your aid. Hmmm.

If it wasn't for the boot-repair log we wouldn't have any idea of what your system looks like. And it doesn't look pretty. Two installations of Fedora, possibly (probably) with the same names for vg/lv and two EFI partitions. You might be able to guess which EFI the firmware has used for this power-on cycle, but you can't guarantee it will always be so. Same probably applies to which LVM environment you get.
What happens if you choose the other Fedora entry from the boot menu ?.

So, my initial try would be to disconnect /dev/sdb - that gets rid of the clashes. Then see if you still have a boot issue. When you try to resolve it make sure you follow the [U]EFI instructions, *not* the BIOS instructions. In fact it might be better to follow this section and purge things entirely. This will not fix any dodgy EFI variables left laying aroung, but should update the default boot to itself.

1 members found this post helpful.