amanti
(Michael Amanti)
May 17, 2026, 9:05pm
1
I started years ago on Fedora 24 Workstation Edition.
I’ve been Updating and Upgrading ever since.
On Fedora 42, " dnf upgrade – refresh " resulted in . . .
SELinux Alerts and . ..
Running %posttrans scriptlet: kernel-core-0:6.19.14-101.fc42.x86_64
Non-critical error in %posttrans scriptlet: kernel-core-0:6.19.14-101.fc42.x86_64
Scriptlet output:
cp: error writing ‘/boot/efi/b6e150d317d440a487c126d143bc071d/0-rescue/initrd’: No space left on device
dracut[F]: Creation of /boot/efi/b6e150d317d440a487c126d143bc071d/0-rescue/initrd failed
/usr/lib/kernel/install.d/51-dracut-rescue.install: line 91: /boot/efi/loader/entries/b6e150d317d440a487c126d143bc071d-0-rescue.conf: No such file or directory
/usr/lib/kernel/install.d/51-dracut-rescue.install failed with exit status 2.
[RPM] %posttrans(kernel-core-6.19.14-101.fc42.x86_64) scriptlet failed , exit status 2
Complete!
root@localhost:~#
So, I went to Fedora Magazine and searched for " Fedora 42 " and found . . .
" Announcing Fedora Linux 42 " [ The answer is 42! Fedora Linux 42, that is. ]
https://fedoramagazine.org/announcing-fedora-linux-42/
The " Common Issues " link . . .
https://discussion.fedoraproject.org/tags/c/ask/common-issues/82/none/f42/981
The issue most likely applicable is . . .
" Systems with <=1 GB /boot partition may see “need more space” error during system update "
https://discussion.fedoraproject.org/t/systems-with-1-gb-boot-partition-may-see-need-more-space-error-during-system-update/170285
My Firmware Repository has always been DISABLED.
( I don’t understand any reason why it should be ENABLED ).
That said, today I enabled it today [ and I’m scared ].
The guidance provides two workarounds . . .
Removing the rescue kernel
Reducing the number of installed kernels
I did both and now . . .
$ rpm -q kernel | sort
kernel-6.19.14-104.fc42.x86_64
I had three and deleted the oldest. Shouldn’t there be two? Hmm.
The Update dnf commands { clean packages, check-update, ugrade --refresh }
completed with " Nothing To Do ".
The Upgrade’s final command, " # dnf5 offline reboot " . . .
booted to a progress bar, which apparently completed successfully.
Then it rebooted to a Black Screen with an ’ _ ’ character at the upper-left.
CTRL-ALT-F3 reveals . . .
" Fedora Linux 43 ( Workstation Edition )
Kernel 6.8.9-100.fc38 .x86_64 ( tty3 )
localhost login:
Note: Despite the workarounds, the above kernel is associated with Fedora 38 .
How do I fix this ?
You obviously did not delete the oldest since an f38 kernel appears to still be installed.
Please show us the output of ls /boot, dnf list --installed kernel*, cat /etc/fedora-release and df -h as well as lsblk -f
Michael Amanti:
No space left on device
This is your error that needs fixed, but we need more detailed info to make progress.
amanti
(Michael Amanti)
May 17, 2026, 11:21pm
3
Jeff:
I recovered / restored my Fedora 42 Workstation from a Clonezilla backup.
Now, I’m reviewing my hand written notes.
I did the Fedora 42 Update commands [ with errors ] and then applied the Workarounds.
During my next session, I will firstly apply the Workarounds and then do the Update [ and upgrade ] commands.
Michael Amanti:
51-dracut-rescue.install
please search also for the file in block quote. If it is on an other location than it was looking for:
0-rescue.conf: No such file or directory
/usr/lib/kernel/install.d/51-dracut-rescue.install failed with exit status 2.
Congratulations. We should create a Badge, for giving you when making the 20thiest upgrade with F44.
If you still had the f38 kernel in the f42 backup then it was seriously compromised as that old kernel had no reason to exist in f42.
I don’t know your backup schedule or work flow, but without detailed information it will be almost impossible to make reasonable suggestions to solve the issue.
There should be at most 4 vmlinuz files and 4 matching initramfs images in /boot for the installed kernels. – 3 working kernels and the rescue kernel & image.
I just noted the following
which tells me something is seriously wrong with the way your system is configured. There should not be a /boot/efi/MACHINEID directory on any standard fedora installation.
To identify exactly the effects of that please post sudo ls -alR /boot
@computersavvy I hope you saw the information that he upgrades since F24?
I think fedora is not able to finish the upgrade because of the to small boot partition.
I agree with Jeff, that an overview of the system would help, to being more able to help.
amanti
(Michael Amanti)
May 18, 2026, 4:25am
7
I’ve completed doing the new lab session.
Workarounds first [ and then the dnf Update & Upgrade ] commands.
After applying Workarounds,
rpm -q kernel | sort . . .
kernel-6.19.8-100.fc42.x86_64
kernel-6.8.9-100.fc38.x86_64
Dnf update commands ran smoothly.
Then # rpm -q kernel | sort
kernel-6.19.14-104.fc42.x86_64
kernel-6.8.9-100.fc38.x86
The dnf upgrade commands ran swell.
# dnf offline reboot . . . the progress bar ran to completion.
Then booted to the dreaded Black Screen.
I recovered / restored-disk from my Fedora Workstation 42 Backup [ again ].
tachi
(Aytac)
May 18, 2026, 12:57pm
8
Were you performing a normal upgrade of your packages in Fedora 42? Or were you trying to upgrade from F42 to F43?
I would suggest following to check:
the journal from the boot with the dreaded black screen and go from there;
the boot partition size and resize if needed;
if any authselect profile is active and go from there;
@computersavvy and @ilikelinux I have also a alphanumeric folder in /boot and it contains a folder named 4.13.9-300.fc27.x86_64. Is my system also seriously wrong? Saying a system is seriously wrong just based on some leftovers from older Fedora versions is quite a statement.
We are all different individuals with different view points. Based on this experiences we can see things different. I personally would not be to much irritated about that statement. @computersavvy is very active and sees a lot of different issues. In my case I saw an other Issue which might cause problems is about suppress user names on the GDM login screen.
This might have something todo with what you mention above.
I found a problem when following the Quick Docs article “Displaying a User Prompt on the GNOME Login Screen” on F44 Workstation (GNOME 50):
Problem:
After a fresh installation of F44 Workstation on a VM, I followed the “Disable User List” procedure (Steps 1-4) in the above Quick Docs article.
This resulted in the GDM login screen not being displayed, and the Greeter desktop being exposed instead. In this state, the terminal becomes unusable and no input is accepted.
Note that this problem …
The OP relates that they upgrades since F24, this might causes some issues because the installation in general changed since. I guess this installation can contain configurations which are not common anymore and we do have to take this in consideration.
@tachi please show us what the command hostnamectl displays. So we know on what your installation is based on.
tachi
(Aytac)
May 18, 2026, 3:15pm
10
Do you need it to help out @amanti better?
I’ve removed the hostname and machine id from output hostnamectl:
Static hostname:
Icon name: computer-desktop
Chassis: desktop 🖥️
Machine ID:
Boot ID: 69a9bf377336439a84f55b58b11284eb
Operating System: Fedora Linux 43 (Workstation Edition)
CPE OS Name: cpe:/o:fedoraproject:fedora:43
OS Support End: Wed 2026-12-02
OS Support Remaining: 6month 2w
Kernel: Linux 7.0.7-100.fc43.x86_64
Architecture: x86-64
Hardware Vendor: Gigabyte Technology Co., Ltd.
Hardware Model: X58A-UD3R
Hardware Version: x.x
Firmware Version: F6
Firmware Date: Tue 2010-08-24
Firmware Age: 15y 8month 3w 3d
amanti
(Michael Amanti)
May 19, 2026, 1:42am
11
It looks like that in the meantime the folder structure changed. That is why @computersavvy asked for the info’s above. So we might be able to help fixing it.
The fact that the OP still uses a F38 kernel shows that something went wrong. I would also check the change es from f38/f39/f40 might be that it shows what changed and we can do it manually.
But please @amanti deliver the info’s of:
Otherwise we can not analyze the issue ans see where the kernel update get stuck.
amanti
(Michael Amanti)
May 19, 2026, 10:18am
13
Jeff V:
I just noted the following
which tells me something is seriously wrong with the way your system is configured. There should not be a /boot/efi/MACHINEID directory on any standard fedora installation.
To identify exactly the effects of that please post sudo ls -alR /boot
/boot:
total 134752
dr-xr-xr-x. 8 root root 4096 Jul 29 2025 .
dr-xr-xr-x. 19 root root 4096 Mar 22 12:26 ..
-rw-r--r--. 1 root root 272192 May 1 2024 config-6.8.9-100.fc38.x86_64
drwx------. 5 root root 16384 Dec 31 1969 efi
drwxr-xr-x. 2 root root 4096 Mar 22 12:27 extlinux
drwxr-xr-x. 3 root root 4096 Jul 5 2017 f3603cfae66044dda9d024b8fa5aec6e
drwx------. 4 root root 4096 May 17 22:37 grub2
-rw-------. 1 root root 63749983 Jul 19 2017 initramfs-0-rescue-b6e150d317d440a487c126d143bc071d.img
-rw-------. 1 root root 41775563 Jan 27 2025 initramfs-6.8.9-100.fc38.x86_64.img
drwxr-xr-x. 3 root root 4096 Jun 4 2018 loader
drwx------. 2 root root 16384 Jul 19 2017 lost+found
-rw-r--r--. 1 root root 148992 Jan 6 2024 memtest86+x64.efi
lrwxrwxrwx. 1 root root 45 Jan 27 2025 symvers-6.8.9-100.fc38.x86_64.xz -> /lib/modules/6.8.9-100.fc38.x86_64/symvers.xz
-rw-r--r--. 1 root root 9021531 May 1 2024 System.map-6.8.9-100.fc38.x86_64
-rwxr-xr-x. 1 root root 7295064 Jul 19 2017 vmlinuz-0-rescue-b6e150d317d440a487c126d143bc071d
-rwxr-xr-x. 1 root root 15646536 May 1 2024 vmlinuz-6.8.9-100.fc38.x86_64
-rw-r--r--. 1 root root 160 May 1 2024 .vmlinuz-6.8.9-100.fc38.x86_64.hmac
/boot/efi:
total 36
drwx------. 5 root root 16384 Dec 31 1969 .
dr-xr-xr-x. 8 root root 4096 Jul 29 2025 ..
drwx------. 12 root root 4096 Mar 22 12:42 b6e150d317d440a487c126d143bc071d
drwx------. 4 root root 4096 Mar 13 2025 EFI
-rwx------. 1 root root 34 Mar 20 2025 mach_kernel
drwx------. 3 root root 4096 Mar 20 2025 System
/boot/efi/b6e150d317d440a487c126d143bc071d:
total 60
drwx------. 12 root root 4096 Mar 22 12:42 .
drwx------. 5 root root 16384 Dec 31 1969 ..
drwx------. 2 root root 4096 Mar 22 12:42 0-rescue
drwx------. 2 root root 4096 Jul 19 2017 4.11.10-300.fc26.x86_64
drwx------. 2 root root 4096 Mar 21 2018 4.15.10-300.fc27.x86_64
drwx------. 2 root root 4096 Apr 7 2018 4.15.14-300.fc27.x86_64
drwx------. 2 root root 4096 Jun 4 2018 4.16.12-200.fc27.x86_64
drwx------. 2 root root 4096 Dec 14 10:33 6.17.10-100.fc41.x86_64
drwx------. 2 root root 4096 Mar 22 12:39 6.19.8-100.fc42.x86_64
drwx------. 2 root root 4096 Jan 27 2025 7.00
drwx------. 2 root root 4096 Nov 22 09:06 7.20
drwx------. 2 root root 4096 Mar 22 12:42 8.00
/boot/efi/b6e150d317d440a487c126d143bc071d/0-rescue:
total 17800
drwx------. 2 root root 4096 Mar 22 12:42 .
drwx------. 12 root root 4096 Mar 22 12:42 ..
-rwx------. 1 root root 18217320 Mar 22 12:40 linux
/boot/efi/b6e150d317d440a487c126d143bc071d/4.11.10-300.fc26.x86_64:
total 8
drwx------. 2 root root 4096 Jul 19 2017 .
drwx------. 12 root root 4096 Mar 22 12:42 ..
/boot/efi/b6e150d317d440a487c126d143bc071d/4.15.10-300.fc27.x86_64:
total 8
drwx------. 2 root root 4096 Mar 21 2018 .
drwx------. 12 root root 4096 Mar 22 12:42 ..
/boot/efi/b6e150d317d440a487c126d143bc071d/4.15.14-300.fc27.x86_64:
total 8
drwx------. 2 root root 4096 Apr 7 2018 .
drwx------. 12 root root 4096 Mar 22 12:42 ..
/boot/efi/b6e150d317d440a487c126d143bc071d/4.16.12-200.fc27.x86_64:
total 8
drwx------. 2 root root 4096 Jun 4 2018 .
drwx------. 12 root root 4096 Mar 22 12:42 ..
/boot/efi/b6e150d317d440a487c126d143bc071d/6.17.10-100.fc41.x86_64:
total 8
drwx------. 2 root root 4096 Dec 14 10:33 .
drwx------. 12 root root 4096 Mar 22 12:42 ..
/boot/efi/b6e150d317d440a487c126d143bc071d/6.19.8-100.fc42.x86_64:
total 8
drwx------. 2 root root 4096 Mar 22 12:39 .
drwx------. 12 root root 4096 Mar 22 12:42 ..
/boot/efi/b6e150d317d440a487c126d143bc071d/7.00:
total 8
drwx------. 2 root root 4096 Jan 27 2025 .
drwx------. 12 root root 4096 Mar 22 12:42 ..
/boot/efi/b6e150d317d440a487c126d143bc071d/7.20:
total 8
drwx------. 2 root root 4096 Nov 22 09:06 .
drwx------. 12 root root 4096 Mar 22 12:42 ..
/boot/efi/b6e150d317d440a487c126d143bc071d/8.00:
total 8
drwx------. 2 root root 4096 Mar 22 12:42 .
drwx------. 12 root root 4096 Mar 22 12:42 ..
/boot/efi/EFI:
total 28
drwx------. 4 root root 4096 Mar 13 2025 .
drwx------. 5 root root 16384 Dec 31 1969 ..
drwx------. 2 root root 4096 Mar 22 12:34 BOOT
drwx------. 3 root root 4096 Mar 22 12:34 fedora
/boot/efi/EFI/BOOT:
total 1024
drwx------. 2 root root 4096 Mar 22 12:34 .
drwx------. 4 root root 4096 Mar 13 2025 ..
-rwx------. 1 root root 949424 Mar 18 2024 BOOTX64.EFI
-rwx------. 1 root root 87816 Mar 18 2024 fbx64.efi
/boot/efi/EFI/fedora:
total 6808
drwx------. 3 root root 4096 Mar 22 12:34 .
drwx------. 4 root root 4096 Mar 13 2025 ..
-rwx------. 1 root root 110 Mar 18 2024 BOOTX64.CSV
drwx------. 2 root root 4096 Aug 8 2018 fw
-rwx------. 1 root root 65824 Aug 8 2018 fwupia32.efi
-rwx------. 1 root root 77496 Aug 8 2018 fwupx64.efi
-rwx------. 1 root root 159 Jan 27 2025 grub.cfg
-rwx------. 1 root root 5728 May 11 2019 grub.cfg.rpmsave
-rwx------. 1 root root 1024 May 1 2021 grubenv.rpmsave
-rwx------. 1 root root 4037952 Jun 4 2025 grubx64.efi
-rwx------. 1 root root 848080 Mar 18 2024 mmx64.efi
-rwx------. 1 root root 949424 Mar 18 2024 shim.efi
-rwx------. 1 root root 949424 Mar 18 2024 shimx64.efi
/boot/efi/EFI/fedora/fw:
total 8
drwx------. 2 root root 4096 Aug 8 2018 .
drwx------. 3 root root 4096 Mar 22 12:34 ..
/boot/efi/System:
total 24
drwx------. 3 root root 4096 Mar 20 2025 .
drwx------. 5 root root 16384 Dec 31 1969 ..
drwx------. 3 root root 4096 Mar 20 2025 Library
/boot/efi/System/Library:
total 12
drwx------. 3 root root 4096 Mar 20 2025 .
drwx------. 3 root root 4096 Mar 20 2025 ..
drwx------. 2 root root 4096 Mar 22 12:35 CoreServices
/boot/efi/System/Library/CoreServices:
total 12
drwx------. 2 root root 4096 Mar 22 12:35 .
drwx------. 3 root root 4096 Mar 20 2025 ..
-rwx------. 1 root root 384 Mar 20 2025 SystemVersion.plist
/boot/extlinux:
total 1108
drwxr-xr-x. 2 root root 4096 Mar 22 12:27 .
dr-xr-xr-x. 8 root root 4096 Jul 29 2025 ..
-rw-r--r--. 1 root root 1780 Apr 28 2025 cat.c32
-rw-r--r--. 1 root root 25044 Apr 28 2025 chain.c32
-rw-r--r--. 1 root root 1420 Apr 28 2025 cmd.c32
-rw-r--r--. 1 root root 3844 Apr 28 2025 cmenu.c32
-rw-r--r--. 1 root root 1656 Apr 28 2025 config.c32
-rw-r--r--. 1 root root 4424 Apr 28 2025 cptime.c32
-rw-r--r--. 1 root root 4676 Apr 28 2025 cpu.c32
-rw-r--r--. 1 root root 1940 Apr 28 2025 cpuid.c32
-rw-r--r--. 1 root root 2940 Apr 28 2025 cpuidtest.c32
-rw-r--r--. 1 root root 1764 Apr 28 2025 debug.c32
-rw-r--r--. 1 root root 4188 Apr 28 2025 dhcp.c32
-rw-r--r--. 1 root root 3140 Apr 28 2025 dir.c32
-rw-r--r--. 1 root root 2188 Apr 28 2025 disk.c32
-rw-r--r--. 1 root root 8836 Apr 28 2025 dmi.c32
-rw-r--r--. 1 root root 12500 Apr 28 2025 dmitest.c32
-rw-r--r--. 1 root root 3464 Apr 28 2025 elf.c32
-rw-r--r--. 1 root root 2916 Apr 28 2025 ethersel.c32
-rw-r--r--. 1 root root 10304 Apr 28 2025 gfxboot.c32
-rw-r--r--. 1 root root 1768 Apr 28 2025 gpxecmd.c32
-rw-r--r--. 1 root root 163404 Apr 28 2025 hdt.c32
-rw-r--r--. 1 root root 3864 Apr 28 2025 hexdump.c32
-rw-r--r--. 1 root root 2016 Apr 28 2025 host.c32
-rw-r--r--. 1 root root 1952 Apr 28 2025 ifcpu64.c32
-rw-r--r--. 1 root root 4272 Apr 28 2025 ifcpu.c32
-rw-r--r--. 1 root root 4480 Apr 28 2025 ifmemdsk.c32
-rw-r--r--. 1 root root 2080 Apr 28 2025 ifplop.c32
-rw-r--r--. 1 root root 1840 Apr 28 2025 kbdmap.c32
-rw-r--r--. 1 root root 5024 Apr 28 2025 kontron_wdt.c32
-rw-r--r--. 1 root root 115036 Apr 28 2025 ldlinux.c32
-rw-r--r--. 1 root root 5260 Apr 28 2025 lfs.c32
-rw-r--r--. 1 root root 178076 Apr 28 2025 libcom32.c32
-rw-r--r--. 1 root root 67696 Apr 28 2025 libgpl.c32
-rw-r--r--. 1 root root 101860 Apr 28 2025 liblua.c32
-rw-r--r--. 1 root root 23812 Apr 28 2025 libmenu.c32
-rw-r--r--. 1 root root 25040 Apr 28 2025 libutil.c32
-rw-r--r--. 1 root root 4852 Apr 28 2025 linux.c32
-rw-r--r--. 1 root root 3144 Apr 28 2025 ls.c32
-rw-r--r--. 1 root root 7088 Apr 28 2025 lua.c32
-rw-r--r--. 1 root root 11252 Apr 28 2025 mboot.c32
-rw-r--r--. 1 root root 25756 Apr 28 2025 memdisk
-rw-r--r--. 1 root root 2660 Apr 28 2025 meminfo.c32
-rw-r--r--. 1 root root 26144 Apr 28 2025 menu.c32
-rw-r--r--. 1 root root 3612 Apr 28 2025 pci.c32
-rw-r--r--. 1 root root 3656 Apr 28 2025 pcitest.c32
-rw-r--r--. 1 root root 3172 Apr 28 2025 pmload.c32
-rw-r--r--. 1 root root 1840 Apr 28 2025 poweroff.c32
-rw-r--r--. 1 root root 3276 Apr 28 2025 prdhcp.c32
-rw-r--r--. 1 root root 1668 Apr 28 2025 pwd.c32
-rw-r--r--. 1 root root 12552 Apr 28 2025 pxechn.c32
-rw-r--r--. 1 root root 1552 Apr 28 2025 reboot.c32
-rw-r--r--. 1 root root 14020 Apr 28 2025 rosh.c32
-rw-r--r--. 1 root root 1796 Apr 28 2025 sanboot.c32
-rw-r--r--. 1 root root 3192 Apr 28 2025 sdi.c32
-rw-r--r--. 1 root root 14748 Apr 28 2025 sysdump.c32
-rw-r--r--. 1 root root 9088 Apr 28 2025 syslinux.c32
-rw-r--r--. 1 root root 3120 Apr 28 2025 vesa.c32
-rw-r--r--. 1 root root 2352 Apr 28 2025 vesainfo.c32
-rw-r--r--. 1 root root 26692 Apr 28 2025 vesamenu.c32
-rw-r--r--. 1 root root 2032 Apr 28 2025 vpdtest.c32
-rw-r--r--. 1 root root 2688 Apr 28 2025 whichsys.c32
-rw-r--r--. 1 root root 3744 Apr 28 2025 zzjson.c32
/boot/f3603cfae66044dda9d024b8fa5aec6e:
total 12
drwxr-xr-x. 3 root root 4096 Jul 5 2017 .
dr-xr-xr-x. 8 root root 4096 Jul 29 2025 ..
drwxr-xr-x. 2 root root 4096 Jul 5 2017 4.11.8-300.fc26.x86_64
/boot/f3603cfae66044dda9d024b8fa5aec6e/4.11.8-300.fc26.x86_64:
total 8
drwxr-xr-x. 2 root root 4096 Jul 5 2017 .
drwxr-xr-x. 3 root root 4096 Jul 5 2017 ..
/boot/grub2:
total 28
drwx------. 4 root root 4096 May 17 22:37 .
dr-xr-xr-x. 8 root root 4096 Jul 29 2025 ..
drwx------. 2 root root 4096 Mar 22 12:30 fonts
-rw-------. 1 root root 5728 May 11 2019 grub.cfg
-rw-------. 1 root root 1024 May 17 22:37 grubenv
drwxr-xr-x. 3 root root 4096 May 9 2012 themes
/boot/grub2/fonts:
total 2348
drwx------. 2 root root 4096 Mar 22 12:30 .
drwx------. 4 root root 4096 May 17 22:37 ..
-rwx------. 1 root root 2394108 Jun 4 2025 unicode.pf2
/boot/grub2/themes:
total 12
drwxr-xr-x. 3 root root 4096 May 9 2012 .
drwx------. 4 root root 4096 May 17 22:37 ..
drwxr-xr-x. 2 root root 4096 May 1 2021 system
/boot/grub2/themes/system:
total 8
drwxr-xr-x. 2 root root 4096 May 1 2021 .
drwxr-xr-x. 3 root root 4096 May 9 2012 ..
/boot/loader:
total 12
drwxr-xr-x. 3 root root 4096 Jun 4 2018 .
dr-xr-xr-x. 8 root root 4096 Jul 29 2025 ..
drwx------. 2 root root 4096 Jun 4 2025 entries
/boot/loader/entries:
total 20
drwx------. 2 root root 4096 Jun 4 2025 .
drwxr-xr-x. 3 root root 4096 Jun 4 2018 ..
-rw-r--r--. 1 root root 155 Mar 30 2024 b6e150d317d440a487c126d143bc071d-0-memtest86+.conf
-rw-r--r--. 1 root root 392 May 11 2019 b6e150d317d440a487c126d143bc071d-0-rescue.conf
-rw-r--r--. 1 root root 339 Jan 27 2025 b6e150d317d440a487c126d143bc071d-6.8.9-100.fc38.x86_64.conf
/boot/lost+found:
total 20
drwx------. 2 root root 16384 Jul 19 2017 .
dr-xr-xr-x. 8 root root 4096 Jul 29 2025 ..
root@localhost:\~#
amanti
(Michael Amanti)
May 19, 2026, 10:28am
14
root@localhost:\~# ls /boot
config-6.8.9-100.fc38.x86_64 initramfs-0-rescue-b6e150d317d440a487c126d143bc071d.img symvers-6.8.9-100.fc38.x86_64.xz
efi initramfs-6.8.9-100.fc38.x86_64.img System.map-6.8.9-100.fc38.x86_64
extlinux loader vmlinuz-0-rescue-b6e150d317d440a487c126d143bc071d
f3603cfae66044dda9d024b8fa5aec6e lost+found vmlinuz-6.8.9-100.fc38.x86_64
grub2 memtest86+x64.efi
root@localhost:\~#
amanti
(Michael Amanti)
May 19, 2026, 10:33am
15
root@localhost:\~# dnf list --installed kernel\*
Installed packages
kernel.x86_64 6.8.9-100.fc38 updates
kernel.x86_64 6.17.10-100.fc41 updates
kernel.x86_64 6.19.8-100.fc42 updates
kernel-core.x86_64 6.8.9-100.fc38 updates
kernel-core.x86_64 6.17.10-100.fc41 updates
kernel-core.x86_64 6.19.8-100.fc42 updates
kernel-headers.x86_64 6.19.6-100.fc42 updates
kernel-modules.x86_64 6.8.9-100.fc38 updates
kernel-modules.x86_64 6.17.10-100.fc41 updates
kernel-modules.x86_64 6.19.8-100.fc42 updates
kernel-modules-core.x86_64 6.8.9-100.fc38 updates
kernel-modules-core.x86_64 6.17.10-100.fc41 updates
kernel-modules-core.x86_64 6.19.8-100.fc42 updates
kernel-modules-extra.x86_64 6.8.9-100.fc38 updates
kernel-modules-extra.x86_64 6.17.10-100.fc41 updates
kernel-modules-extra.x86_64 6.19.8-100.fc42 updates
kernel-srpm-macros.noarch 1.0-25.fc42 fedora
kernel-tools.x86_64 6.19.8-100.fc42 updates
kernel-tools-libs.x86_64 6.19.8-100.fc42 updates
root@localhost:\~#
amanti
(Michael Amanti)
May 19, 2026, 10:37am
16
Jeff V:
cat /etc/fedora-release
root@localhost:\~# cat /etc/fedora-release
Fedora release 42 (Adams)
root@localhost:\~#
amanti
(Michael Amanti)
May 19, 2026, 10:40am
17
Jeff V:
df -h
root@localhost:\~# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 3.8G 12K 3.8G 1% /dev/shm
tmpfs 1.5G 1.8M 1.5G 1% /run
efivarfs 128K 38K 86K 31% /sys/firmware/efi/efivars
/dev/mapper/fedora-root 33G 15G 17G 48% /
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
tmpfs 3.8G 80K 3.8G 1% /tmp
/dev/sda2 974M 135M 772M 15% /boot
/dev/mapper/fedora-home 16G 14G 1.7G 89% /home
/dev/sda1 200M 26M 175M 13% /boot/efi
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service
tmpfs 762M 176K 762M 1% /run/user/1001
tmpfs 762M 68K 762M 1% /run/user/0
root@localhost:\~#
amanti
(Michael Amanti)
May 19, 2026, 10:47am
18
Jeff V:
lsblk -f
root@localhost:~# lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT16 5FA2-BA83 174.7M 13% /boot/efi
├─sda2 ext4 1.0 7e9394e6-8bee-4dc6-a6f8-af8416b12483 771.2M 14% /boot
└─sda3 LVM2_member LVM2 001 ua1SYa-VTxB-T0Ir-FZDI-kzUy-V7et-kmXD05
├─fedora-root ext4 1.0 04fac5b0-c7b5-4535-9dca-cd562d493749 16.1G 45% /
├─fedora-swap swap 1 e0e45f41-57d6-419f-a532-b654ea0d19ea [SWAP]
└─fedora-home ext4 1.0 55bd0fd8-fb2a-4f28-ac85-cf4899b9791a 1.6G 84% /home
sdb
sr0
zram0 swap 1 zram0 9a8b6a55-8788-48ac-b2c7-cace521181ec [SWAP]
root@localhost:~# lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT16 5FA2-BA83 174.7M 13% /boot/efi
├─sda2 ext4 1.0 7e9394e6-8bee-4dc6-a6f8-af8416b12483 771.2M 14% /boot
└─sda3 LVM2_member LVM2 001 ua1SYa-VTxB-T0Ir-FZDI-kzUy-V7et-kmXD05
├─fedora-root ext4 1.0 04fac5b0-c7b5-4535-9dca-cd562d493749 16.1G 45% /
├─fedora-swap swap 1 e0e45f41-57d6-419f-a532-b654ea0d19ea [SWAP]
└─fedora-home ext4 1.0 55bd0fd8-fb2a-4f28-ac85-cf4899b9791a 1.6G 84% /home
sdb
sr0
zram0 swap 1 zram0 9a8b6a55-8788-48ac-b2c7-cace521181ec [SWAP]
All of the output you provided shows that this system was installed as far back as f26. There are many files under /boot that seem to be 32 bit.
I personally would strongly suggest that you save as much as possible of your personal data under /home to a backup, then wipe out this ancient file system structure and do a new clean install of either f43 or f44 so the kernel and efi files get placed properly for the modern file system structure.
Following this the system should be able to properly install kernels and perform updates.
That is an installation from the everything ISO