Solved Fedora 31 stuck in a boot loop
-
So everything was working this morning.
I shut down and left the site I was at.
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.
But both previous kernels fail also.
5.3.11-300
5.3.8-300 -
@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.
-
Are you able to boot into the rescue boot menu?
-
@black3dynamite said in Fedora 31 stuck in a boot loop:
Are you able to boot into the rescue boot menu?
It will boot to emergency mode
-
This is the list of updates applied today. Thanks
dnf-automaticfor emails!The following updates have been applied on 'lt-jared.jaredbusch.com': ================================================================================ Package Arch Version Repo Size ================================================================================ Upgrading: NetworkManager x86_64 1:1.20.8-1.fc31 updates 2.0 M NetworkManager-adsl x86_64 1:1.20.8-1.fc31 updates 26 k NetworkManager-bluetooth x86_64 1:1.20.8-1.fc31 updates 51 k NetworkManager-libnm x86_64 1:1.20.8-1.fc31 updates 1.6 M NetworkManager-team x86_64 1:1.20.8-1.fc31 updates 29 k NetworkManager-wifi x86_64 1:1.20.8-1.fc31 updates 98 k NetworkManager-wwan x86_64 1:1.20.8-1.fc31 updates 57 k bind-libs x86_64 32:9.11.13-2.fc31 updates 94 k bind-libs-lite x86_64 32:9.11.13-2.fc31 updates 1.1 M bind-license noarch 32:9.11.13-2.fc31 updates 20 k bind-utils x86_64 32:9.11.13-2.fc31 updates 236 k evince-djvu x86_64 3.34.2-1.fc31 updates 32 k evince-libs x86_64 3.34.2-1.fc31 updates 378 k fedora-obsolete-packages noarch 31-40 updates 78 k file-roller x86_64 3.32.3-1.fc31 updates 840 k gdb x86_64 8.3.50.20190824-25.fc31 updates 129 k gdb-headless x86_64 8.3.50.20190824-25.fc31 updates 3.7 M gnome-control-center-filesystem noarch 3.34.2-1.fc31 updates 11 k grub2-common noarch 1:2.02-103.fc31 updates 876 k grub2-efi-x64 x86_64 1:2.02-103.fc31 updates 458 k grub2-pc-modules noarch 1:2.02-103.fc31 updates 847 k grub2-tools x86_64 1:2.02-103.fc31 updates 1.8 M grub2-tools-efi x86_64 1:2.02-103.fc31 updates 469 k grub2-tools-extra x86_64 1:2.02-103.fc31 updates 916 k grub2-tools-minimal x86_64 1:2.02-103.fc31 updates 552 k gvfs x86_64 1.42.2-1.fc31 updates 370 k gvfs-archive x86_64 1.42.2-1.fc31 updates 25 k gvfs-client x86_64 1.42.2-1.fc31 updates 766 k gvfs-goa x86_64 1.42.2-1.fc31 updates 69 k gvfs-gphoto2 x86_64 1.42.2-1.fc31 updates 69 k gvfs-mtp x86_64 1.42.2-1.fc31 updates 70 k gvfs-smb x86_64 1.42.2-1.fc31 updates 46 k inxi noarch 3.0.37-1.fc31 updates 276 k librsvg2 x86_64 2.46.4-1.fc31 updates 1.4 M mokutil x86_64 1:0.3.0-14.fc31 updates 43 k nano x86_64 4.3-3.fc31 updates 640 k nss x86_64 3.47.1-1.fc31 updates 686 k nss-softokn x86_64 3.47.1-1.fc31 updates 444 k nss-softokn-freebl x86_64 3.47.1-1.fc31 updates 241 k nss-sysinit x86_64 3.47.1-1.fc31 updates 20 k nss-tools x86_64 3.47.1-1.fc31 updates 549 k nss-util x86_64 3.47.1-1.fc31 updates 92 k osinfo-db noarch 20191125-1.fc31 updates 203 k python3-bind noarch 32:9.11.13-2.fc31 updates 67 k quota x86_64 1:4.05-7.fc31 updates 193 k quota-nls noarch 1:4.05-7.fc31 updates 78 k simple-scan x86_64 3.34.2-1.fc31 updates 946 k tigervnc-license noarch 1.10.0-1.fc31 updates 15 k tigervnc-server-minimal x86_64 1.10.0-1.fc31 updates 1.1 M vte-profile x86_64 0.58.3-1.fc31 updates 11 k vte291 x86_64 0.58.3-1.fc31 updates 289 k xorg-x11-server-Xephyr x86_64 1.20.6-1.fc31 updates 1.0 M xorg-x11-server-Xorg x86_64 1.20.6-1.fc31 updates 1.5 M xorg-x11-server-Xwayland x86_64 1.20.6-1.fc31 updates 985 k xorg-x11-server-common x86_64 1.20.6-1.fc31 updates 37 k yelp-xsl noarch 3.34.2-1.fc31 updates 197 k Installing dependencies: glibc-devel x86_64 2.30-7.fc31 updates 1.0 M glibc-headers x86_64 2.30-7.fc31 updates 455 k kernel-headers x86_64 5.3.11-300.fc31 updates 1.1 M annobin x86_64 8.78-2.fc31 fedora 108 k cpp x86_64 9.2.1-1.fc31 fedora 9.8 M gcc x86_64 9.2.1-1.fc31 fedora 21 M isl x86_64 0.16.1-9.fc31 fedora 871 k libxcrypt-devel x86_64 4.4.10-1.fc31 fedora 36 k Installing weak dependencies: gcc-gdb-plugin x86_64 9.2.1-1.fc31 fedora 136 k Transaction Summary ================================================================================ Install 9 Packages Upgrade 56 Packages -
Can't provide any input but it's interesting to read the problems that shows up every time there is a new Fedora release out. Your customers are a forgiving bunch for sure.
That said, it's great for the open source community to have lots of people running the latest and greatest.
-
@Pete-S said in Fedora 31 stuck in a boot loop:
Can't provide any input but it's interesting to read the problems that shows up every time there is a new Fedora release out. Your customers are a forgiving bunch for sure.
That said, it's great for the open source community to have lots of people running the latest and greatest.
I don’t know what the fuck you are talking about.
This is specifically not a new fedora release.
I’ve been on Fedora 31 since release. The only fedora release upgrade I have ever had a problem with was from 29 to 30, and that was caused by a piece of software I had installed that was not updated on release day. I removed that software and it updated perfectly.
I could have also waited a few days and had zero issues.
-
My systems is using kernel 5.3.12
-
This was yesterday’s update. Which I had no problem booting into multiple times yesterday and this morning.
The following updates have been applied on 'lt-jared.jaredbusch.com': ==================================================================================================================================== Package Arch Version Repository Size ==================================================================================================================================== Installing: kernel x86_64 5.3.12-300.fc31 updates 41 k kernel-core x86_64 5.3.12-300.fc31 updates 30 M kernel-devel x86_64 5.3.12-300.fc31 updates 12 M kernel-modules x86_64 5.3.12-300.fc31 updates 28 M kernel-modules-extra x86_64 5.3.12-300.fc31 updates 1.9 M Upgrading: glib2 i686 2.62.3-1.fc31 updates 2.7 M glib2 x86_64 2.62.3-1.fc31 updates 2.6 M gmime30 x86_64 3.2.5-1.fc31 updates 221 k hplip x86_64 3.19.10-2.fc31 updates 17 M hplip-common x86_64 3.19.10-2.fc31 updates 71 k hplip-libs x86_64 3.19.10-2.fc31 updates 166 k libnfsidmap x86_64 1:2.4.1-2.rc1.fc31 updates 72 k libsane-hpaio x86_64 3.19.10-2.fc31 updates 92 k mesa-dri-drivers x86_64 19.2.6-1.fc31 updates 16 M mesa-filesystem x86_64 19.2.6-1.fc31 updates 17 k mesa-libEGL x86_64 19.2.6-1.fc31 updates 122 k mesa-libGL i686 19.2.6-1.fc31 updates 192 k mesa-libGL x86_64 19.2.6-1.fc31 updates 180 k mesa-libOpenCL x86_64 19.2.6-1.fc31 updates 339 k mesa-libgbm x86_64 19.2.6-1.fc31 updates 42 k mesa-libglapi i686 19.2.6-1.fc31 updates 54 k mesa-libglapi x86_64 19.2.6-1.fc31 updates 57 k mesa-libxatracker x86_64 19.2.6-1.fc31 updates 1.7 M mesa-vulkan-drivers x86_64 19.2.6-1.fc31 updates 2.5 M mint-x-icons noarch 1.5.3-1.fc31 updates 13 M nfs-utils x86_64 1:2.4.1-2.rc1.fc31 updates 449 k perl-Term-Table noarch 0.015-1.fc31 updates 44 k python3-rpm x86_64 4.15.1-1.fc31 updates 95 k rpm x86_64 4.15.1-1.fc31 updates 499 k rpm-build x86_64 4.15.1-1.fc31 updates 116 k rpm-build-libs x86_64 4.15.1-1.fc31 updates 97 k rpm-libs x86_64 4.15.1-1.fc31 updates 300 k rpm-plugin-selinux x86_64 4.15.1-1.fc31 updates 21 k rpm-plugin-systemd-inhibit x86_64 4.15.1-1.fc31 updates 22 k rpm-sign-libs x86_64 4.15.1-1.fc31 updates 26 k onlyoffice-desktopeditors x86_64 5.4.2-30 onlyoffice 217 M code x86_64 1.40.2-1574694258.el7 code 78 M Removing: kernel x86_64 5.3.7-301.fc31 @fedora 0 kernel-core x86_64 5.3.7-301.fc31 @fedora 67 M kernel-devel x86_64 5.3.7-301.fc31 @fedora 54 M kernel-modules x86_64 5.3.7-301.fc31 @fedora 28 M kernel-modules-extra x86_64 5.3.7-301.fc31 @fedora 1.9 M Transaction Summary ==================================================================================================================================== Install 5 Packages Upgrade 32 Packages Remove 5 Packages -
@Pete-S said in Fedora 31 stuck in a boot loop:
Can't provide any input but it's interesting to read the problems that shows up every time there is a new Fedora release out. Your customers are a forgiving bunch for sure.
That said, it's great for the open source community to have lots of people running the latest and greatest.
I've been on Fedora about 2 years on my laptop now and I know exactly what you're talking about.
-
I don't think @JaredBusch runs gnome, so that probably saves him a lot of grief.
-
@JaredBusch said in Fedora 31 stuck in a boot loop:
So everything was working this morning.
I shut down and left the site I was at.
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.
But both previous kernels fail also.
5.3.11-300
5.3.8-300What changed? Auto updates, drivers? Update logs?
-
@Obsolesce said in Fedora 31 stuck in a boot loop:
@JaredBusch said in Fedora 31 stuck in a boot loop:
So everything was working this morning.
I shut down and left the site I was at.
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.
But both previous kernels fail also.
5.3.11-300
5.3.8-300What changed? Auto updates, drivers? Update logs?
I posted the updates that were applied.
-
@JaredBusch said in Fedora 31 stuck in a boot loop:
@Obsolesce said in Fedora 31 stuck in a boot loop:
@JaredBusch said in Fedora 31 stuck in a boot loop:
So everything was working this morning.
I shut down and left the site I was at.
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.
But both previous kernels fail also.
5.3.11-300
5.3.8-300What changed? Auto updates, drivers? Update logs?
I posted the updates that were applied.
Ah I didn't see that somehow.
-
I'll have to check my laptop to compare kernels. Mine won't go to sleep. If I shut the lid and open it again it does a hard reboot instead of resuming from sleep.
-
My desktop has all the same updates applied, but has not been rebooted yet as I was out of town.
I'm home now, and will be able to mess with this. First up, I don't know where to go to look for a log since the thing is not getting to any visible boot state.
The drive appears normal. I put it in a USB housing and copied a few things off, like my SSH identity files.
Otherwise, I'm not worried about losing the information, nothing on my laptop is important, unless saved in my Nextcloud sync folder. But I would prefer to figure out what went wrong.
Obviously not risking a reboot of my desktop right now either. Because while there is no critical data on my desktop not saved elsewhere, the time to resetup my environment and Windows VMs for dev is very unappealing.
-
I did have a Fedora 31 laptop (different model Dell than mine) spun up and logged in two weeks ago. I have ran updates on that one and rebooted. it is running fine.
But it has almost nothing installed. I was only testing some Nextcloud stuff on it.
-
After it fails, doesn't journalctl give any indication of what's causing failures to boot?
-
@Obsolesce said in Fedora 31 stuck in a boot loop:
After it fails, doesn't journalctl give any indication of what's causing failures to boot?
it is in a boot loop. there is nothing to see.
if I choose to boot to recovery mode, it drops straight to emergency mode.
journalctl -xb retuns like 1200+ lines. going through that line by line was not something I felt like doing late in the day on Friday after Thanksgiving, while visiting friends.
at a glance it also looked like only the recovery mode boot was in that log.
-
waiting on something to copy off the drive that I cannot find the second copy of. then i'll have it back in my laptop and ready to fuck with.
-
The contents of
/etc/grub.dseem identical on all three systems I have here.- My Desktop - have not tried to reboot
- My Laptop - does not boot
- Spare Laptop - reboots successfully.
