Missing initramfs due to forced shutdown on release upgrade

Ask Fedora
1

Fedora, I’ve been waiting to say this for a long time. That elegance, that blue colour deeply affected me. I’ve known you for about five months now. From the moment I first saw you, from the moment I first installed you on my computer, I knew you were the best distribution. I love you, Fedora. But please, in the next update, let initramfs be installed automatically. I don’t want to have to install it manually every time. If the end-user wants to use the latest kernel version, they’ll have to do it via the terminal, and that’s a hassle for them.

2

It’s been automatic since… probably forever? I have no clue why you are having trouble. You certainly shouldn’t need to do anything.

3 Likes
3

The initramfs file is built by dracut - should be automatic.

If it’s failing to build for you, we can assist - you should have zero hassle in installing a new kernel other than the inconvenience of a reboot.

2 Likes
4

When I try to open the new kernel in the GRUB menu, it says initramfs is missing. This happened in the prerelease KDE Plasma version as well as in the workstation version I just installed. It is resolved when created manually with the --kver command. This also happened in 42, but in 43 it automatically boots from the old kernel.

I wrote this with the help of a translator; I would be grateful if you could overlook any mistakes.

I also updated it from the graphical interface and each time it took hours at 97%.
I performed a forced shutdown

5

Using a forced shutdown is strongly discouraged as it can result in major issues, specifically if this happens during a system upgrade.

In the worst case, the filesystem may become corrupted and you should be prepared to lose the data and be ready to reinstall the system.

Even if you are lucky to avoid the worst case scenario, interrupted system upgrade still leads to inconsistent RPM database, unfinished transactions, duplicates, dependency related issues, possibly even SELinux labeling issues, all of which need to be properly diagnosed and addressed.

You should start with post upgrade tasks and see how it goes:
Post-upgrade tasks :: Fedora Docs

Also take care of the following to avoid future problems:
Possible upgrade issues on systems with <=1 GB /boot partition