Today I start my PC as normal. There is an update that I’m trying to install, containing the new KDE version (6.7).
I cannot do the update through the UI, it fails, saying to me that “Failed to apply offline update”, something like that.
So, I open the terminal to perform the update there: sudo dnf upgrade. It looks fine, until the end where it fails to do something with “dracut”. Not so sure what happened. The DE seems broken, I cannot use it to restart the computer anymore (I’m on KDE). So, I type reboot from the terminal.
It won’t reboot. When I try the last kernel intalled it just won’t boot at all. When I use the older kernel version (previous one), it starts, but then won’t start the DE and I can only do CTRL+ALT+3 to open tty and type commands. I try to do sudo dnf upgrade again, and you can see in the below screenshots what it is telling to me:
I really don’t understand what happened. I cannot access my Fedora install anymore, and I can onnly use my PC thanks to the fact that I got Windows as dual boot. So, before reinstalling everything, I wanted to get some help.
You have a partially upgraded system - you state you’re on Fedora 44, but you have repos in there for Fedora 43.
Are you actually trying to upgrade from 43 to 44 or are you just trying to installed the latest updated? I assume the former, given that you are running on an F43 kernel.
i though i updated to fedora 44 since in system settings it said i’m on 44. But ye seems like i’m in a weird partial state.
I will try your link, thanks.
I wonder if this is just the old kernel version that is still on 43. Since I just cannot start the new kernel version, there is another error message that I can share with you later.
We probably need to clean up your system, finish off the upgrade, determine why dracut is failing to build new kernels, repair whatever you currently have in an unusable status and so on.
Definitely do this - your system is partially upgraded, you’re basically in the middle of an upgrade so cleaning up the remnants of the F43 install and finishing the upgrade to F44 will at least give us a system which we can work with.
Ok, it worked, I can now access my DE back! I need to remember this command.
However, as far as I understand, my system is still kind of broken? At least, the updates are, right? Is there any way to know (without breaking the system again, now i’m afraid of typing dnf upgrade lol).
Thanks for your help so far (both!)
(seems like it’s still broken tho’, Discord is in an endless fetching updates loop it seems)
Splendid - I assume you’re able to boot a kernel and get to your KDE desktop. Welcome back!
Let’s see what kernel you’re currently running and what you have installed:
Please post the output of uname -r, lsblk -f and ls -al /boot, all as preformatted text please, or the formatting looks like crap.
Might as well post the output from inxi -Fzxx too so we can see your kit, which drivers you’re running and so forth. You may need to install inxi with sudo dnf install inxi - don’t worry - it’ll be fine!
Don’t sweat discord, it’ll be after an update but before we run that we want to make sure that you have a system that will continue to boot and has enough space in all the relevant places, hence the request for output above.
OK - you have a little issue but one which you might be happy to let take care of itself:
-rw-------. 1 root root 88778303 Jun 24 01:10 initramfs-7.0.12-201.fc44.x86_64.img
-rw-------. 1 root root 81553656 May 24 11:54 initramfs-7.0.9-105.fc43.x86_64.img
[elided]
-rwxr-xr-x. 1 root root 18442600 Jun 10 02:00 vmlinuz-7.0.12-101.fc43.x86_64
-rwxr-xr-x. 1 root root 18688360 Jun 10 02:00 vmlinuz-7.0.12-201.fc44.x86_64
-rwxr-xr-x. 1 root root 18430312 May 21 02:00 vmlinuz-7.0.9-105.fc43.x86_64
You have three kernels installed (the vmlinuz files above) but only two initial ram file-systems. As such you will never be able to boot into 7.0.12-101, should you ever want to.
You could fix this but running a sudo dracut --kver 7.0.12-101.fc43.x64_64 --force which will build a ramdisk image for that kernel, but given that it’s the oldest, it’ll vanish with the next kernel release assuming you’ve got the default setup of “keep 3 kernels”.
Therefore, you can either ignore it and don’t try to boot it, as it’ll fail, or you can fix it, and likely never need it - your choice!
As for getting yourself fully up to date you can run a sudo dnf update --refresh from the command line, and it’ll do the needful without having to bother with the GUI.
