I recently upgraded my system from F44 to F45 beta. After that, the default highlighted boot item is the kernel of F44 (as shown attached) and the booting is failed (as shown in the second figure). When I move the highlighting to the F45 kernel, The booting is failed again (as shown by the third one). What can I do?
Maybe reinstall f44, pre-beta isn’t suitable for newbs
Thank you for your reply. I tried the same for several time. This is the first time that this problem appears.
Booting from the F44 kernel (7.1.13) reports that “You are in emergency mode, … Cannot access to console, the root account is locked”. Booting from the F45 kernel reports that imitramfs-7.2.0-61.fc45.x86_64.img not found.
How can I reinstall F44 with my data intacted?
Is /home on a separate partition?
ATM, that’s a common issue with upgrades to f45. And it’s easy to resolve post upgrade. If you can’t, you should probably stick to a supported release for a bit longer.
EDIT: common issue is the failed dracut run for the new kernel. The old – in your case – 7.1.13 kernel should still boot.
I upgraded my test/recovery system OS (booting an ext. ssd ) to F45 and also encountered the same issue updating two VMs F44 and F43 to F45.
In all three cases, the old default kernel was able to boot the system and then you would take the necessary steps to make the new 7.2 kernel bootable. Looks like something is really off with your system.
Everyone tinkering with F45, especially with upgrades from F44 to F45 should please keep an eye on this thread:
Too late, I have already deployed F45 on my workstation as soon as it branched, this workstation is also used to host the only rpmfusion power builder.
My media PC upgrade is blocked by proton-vpn lack of python-3.15 support needed for it’s GUI 
Their tech support told me it isn’t planed until final release 
No, it seems the btrfs file system doesn’t allow a separate /home partition.
btrf supports subvolumes so /home is typically a subvolume separate from the root. If you want to do a fresh install and keep the data in /home you need to remove the root subvolume and create new one.
Where can I creat a new root subvolume on a partitioned file system?
I cannot boot into F44 with kernel 7.1.13, with error shown in the second figure.
Does the system boot if you just wait for the default kernel to be booted? For some reason grub would just bomb out if I manually tried to boot the 7.1.x kernel.
But def. not running into emerg. mode. Trying to upgrade to a pre-beta system with root account locked is brave 
The system doesn’t boot, as shown in the second figure above.
You only would do that when doing a clean re-install. For an upgrade that is irrelevant.
To this question you just run the command lsblk -f and show the results. I am not sure why the question was asked, though.
It’s too late. Any suggestion to me?
You can still create a /home subvolume and move your volume to it, but if you slip there is a risk of losing your data, so be careful.
Here is how you do, very roughly:
- boot a recovery usb key
- mount the / disk of the broken installation somewhere (es. in /mnt)
- create a temporary btrf volume for home (es. btrfs subvolume create /mnt/home2)
- move all the /mnt/home stuff in /mnt/home2 then delete /mnt/home and mv /mnt/home2 to /mnt/home
- optionally, you can create a subvolume for the broken root filesystem and move all the rest there. Otherwise, you can delete everything that isn’t in home. Do not leave it there as it will interfere with the next step
- Reinstall the system. Specify choose the “broken” disk a root disk, DO NOT FORMAT IT (uncheck the “format” box if it is checked) and in the advanced options of btrfs filesystem set the correct subvolumes. This is doable with the “custom” partitioning option but not very intuitive, and I don’t remember exactly what had to be chosen.
As long as you do not format the partition you will not lose your data, you may even want to keep the subvolume as “home2” or something until the system is cimpletely installed to be sur that in no case the setup decides to overwrite it.
