Solved Fedora 31 stuck in a boot loop
-
-
managed to boot into recovery mode and get an IP from a USB ethernet dongle.
I ran through the instructions fine on that link, but then step 5 was a link to another page that stated to run
grub2-install /dev/sdaWell that puked on the nowEFI thing. Google told me I needed to
dnf install grub2-efi-x64-modules.Now it dies and says
grub2-install: error: cannot find EFI directory -
@JaredBusch said in Fedora 31 stuck in a boot loop:
managed to boot into recovery mode and get an IP from a USB ethernet dongle.
I ran through the instructions fine on that link, but then step 5 was a link to another page that stated to run
grub2-install /dev/sdaWell that puked on the nowEFI thing. Google told me I needed to
dnf install grub2-efi-x64-modules.Now it dies and says
grub2-install: error: cannot find EFI directoryThese look to be more up to date with more details.
https://docs.fedoraproject.org/en-US/quick-docs/bootloading-with-grub2/
https://fedoraproject.org/wiki/GRUB_2 -
@JaredBusch said in Fedora 31 stuck in a boot loop:
Now I am trying to boot up and it simply goes back to bios.
Obviously something is crashing in the boot cycle. But what?
Kernel 5.3.12-300 is current.I dont know why you love that Distro at ML ... Ubuntu 19.10 and POP OS looks similar in software updates and more stable
-
@Emad-R said in Fedora 31 stuck in a boot loop:
@JaredBusch said in Fedora 31 stuck in a boot loop:
Now I am trying to boot up and it simply goes back to bios.
Obviously something is crashing in the boot cycle. But what?
Kernel 5.3.12-300 is current.I dont know why you love that Distro at ML ... Ubuntu 19.10 and POP OS looks similar in software updates and more stable
That's not helpful for his situation.
-
@black3dynamite said in Fedora 31 stuck in a boot loop:
@JaredBusch said in Fedora 31 stuck in a boot loop:
managed to boot into recovery mode and get an IP from a USB ethernet dongle.
I ran through the instructions fine on that link, but then step 5 was a link to another page that stated to run
grub2-install /dev/sdaWell that puked on the nowEFI thing. Google told me I needed to
dnf install grub2-efi-x64-modules.Now it dies and says
grub2-install: error: cannot find EFI directoryThese look to be more up to date with more details.
https://docs.fedoraproject.org/en-US/quick-docs/bootloading-with-grub2/
https://fedoraproject.org/wiki/GRUB_2well, I totally broke something in
grub. Laptop no longer sees any boot partition.So, clean reinstall time.
Just really annoyed that I couldn't figure this out with everyone's help.
-
Clean install from the live media. All good after multiple reboots.
dnf upgrade --refresh --exclude kernel*And hmmmmm
-
What the heck.
-
@JaredBusch said in Fedora 31 stuck in a boot loop:
Clean install from the live media. All good after multiple reboots.
dnf upgrade --refresh --exclude kernel*And hmmmmm
Is something wrong with SELinux permissions?
-
@black3dynamite said in Fedora 31 stuck in a boot loop:
@JaredBusch said in Fedora 31 stuck in a boot loop:
Clean install from the live media. All good after multiple reboots.
dnf upgrade --refresh --exclude kernel*And hmmmmm
Is something wrong with SELinux permissions?
It is a 100% new install. Second time in fact because I installed the first time, ran updates and rebooted before looking. And it wouldn’t reboot. So I did it again.
-
@JaredBusch efibootmgr is clean?
-
@warren-stanley said in Fedora 31 stuck in a boot loop:
@JaredBusch efibootmgr is clean?
at this point, yes, because it was a clean install. twice.
-
doing it again (clean install) and this time excluding grub but updating the kernel
-
So no idea what the exact fail combo is, but I am fully updated, and working, on a clean install.
- Installed Fedora 31 Cinnamon from USB.
- Rebooted, I have only kernel 5.3.7-301
- Removed dnf dragora GUI
sudo dnf remove dnfdragora* -y - Rebooted.
- Upgraded all but grub2
sudo dnf upgrade --refresh -y --exclude grub2* - Rebooted, not I now have kernel 5.3.13-300 available and default.
- Upgraded grub2
sudo dnf upgrade --refresh -y, I did receive the above SELinux errors again, they may be normal? - Rebooted, system working normally.
