Solved Fedora 31 stuck in a boot loop
-
@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.
-
@stacksofplates said in Fedora 31 stuck in a boot loop:
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.
Mine goes to sleep when I unplug it from power
-
Here's an example of my Grub setting using UEFI on Fedora
sudo cat /boot/efi/EFI/fedora/grubenv # GRUB Environment Block saved_entry=a0a0a0b0a0000000a0a000000a00aaaa-5.3.12-300.fc31.x86_64 menu_auto_hide=1 boot_success=1 kernelopts=root=/dev/mapper/fedora_user-root ro rd.lvm.lv=fedora_user/root rd.luks.uuid=luks-0aa0aa00-341a-0000-000a-a000a0a0aa70 rhgb quiet boot_indeterminate=0 -
@black3dynamite said in Fedora 31 stuck in a boot loop:
Here's an example of my Grub setting using UEFI on Fedora
sudo cat /boot/efi/EFI/fedora/grubenvThere we go..
grubenvis missing on my laptop. -
@JaredBusch said in Fedora 31 stuck in a boot loop:
@black3dynamite said in Fedora 31 stuck in a boot loop:
Here's an example of my Grub setting using UEFI on Fedora
sudo cat /boot/efi/EFI/fedora/grubenvThere we go..
grubenvis missing on my laptop.That can also be missing if you are not using UEFI. In fact, there shouldn't be nothing in
/boot/efi/EFI/fedora/if you using BIOS instead of UEFI.sudo find /boot/ -name grub.cfgwill output one of the following:BIOS
/boot/grub2/grub.cfgUEFI
/boot/efi/EFI/fedora/grub.cfg -
@black3dynamite said in Fedora 31 stuck in a boot loop:
@JaredBusch said in Fedora 31 stuck in a boot loop:
@black3dynamite said in Fedora 31 stuck in a boot loop:
Here's an example of my Grub setting using UEFI on Fedora
sudo cat /boot/efi/EFI/fedora/grubenvThere we go..
grubenvis missing on my laptop.That can also be missing if you are not using UEFI. In fact, there shouldn't be nothing in
/boot/efi/EFI/fedora/if you using BIOS instead of UEFI.sudo find /boot/ -name grub.cfgwill output one of the following:BIOS
/boot/grub2/grub.cfgUEFI
/boot/efi/EFI/fedora/grub.cfgIt is (was) UEFI for certain. BIOS config is set to UEFI boot.
