Fedora failing to boot after attempting to update to from 42 to 43

Ask Fedora
, , ,
23

Related topics:

Seeing the latter, if you have a /boot/efi/loader rename it also, before re-installing kernel-core

24

You are correct, and the software output was misleading since it was run on windows and incorrect results reported.

I will note, however, that with the btrfs file system showing 78% full it is probably time to consider how to manage when the system gets closer to full. Linux file systems, and especially btrfs, do not play well when there is limited free space.

2 Likes
25

Perfect, I now have a boot option labelled as Fedora 43! Appreciate the help.

26

Thanks, but for the record, can you tell what directories you renamed among:

  • /boot/$(cat /etc/machine-id)
  • /boot/efi/$(cat /etc/machine-id)
  • /boot/efi/loader

Now that you were able to reboot, you can safely remove those (renamed) directories.

27

For the record also, it would be nice to explicit how this problem happened.

How did you started the update from Fedora 42 to Fedora 43 ?
With Gnome Software, Discover (KDE/plasma) or dnf system-upgrade ?

You said:

during the update process, my laptop restarted automatically

This is the expected behavior with dnf.
Do you think it was an error in your case ?

28

It would be nice to keep the actual dnf5 logs before they expire.
Can you send them with: fpaste $(ls -rt /var/log/dnf5.log*)
then paste here the URL given by fpaste (https://paste.centos.org/view/XXX)

29

@philtilldawn: please do that ASAP otherwise those logs will lbe lost (because rotated):

Execute: fpaste $(ls -rt /var/log/dnf5.log*)

then paste here the URL given by fpaste (https://paste.centos.org/view/XXX)

30

  1. Windows will report a Linux drive as ā€œ100%ā€ full because, as far as Windows is concerned, it is. An ā€œunknownā€ (Linux) filesystem(s) is taking all of the space; Windows has no way of looking at the actual btrfs data and see how much space is used.

  2. I know this is marked as ā€œsolvedā€ butā€¦ one thing stuck out to me, and that is a) you are using Nvidia binary blob drivers and b) you have secure boot enabled. This shouldnā€™t work, and should result in a black screen, until you have signed the drivers (detailed here Making sure you're not a bot!) I know this was marked as solved, but Iā€™m wondering, are you sure your NVIDIA binary blob is actually working?