Description of problem: After upgrading (Fedora 31 to Fedora 32) using Gnome Software, I cannot boot from any of the available kernels (nor grub rescue). Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing From the emergency shell, I see that /sysroot is empty.
Not sure what went wrong with the upgrade, but I'm pretty sure it's not gnome-software fault. Moving to rpm-ostree.
I that it is obvious that I have little idea of what I am looking at, my apologies for that. Looking more in detail, I think that this might be closer to the issue: systemd-gpt-auto-generator: EFI loader partition unknown, exiting. (The boot loader did not set EFI variable LoaderDevicePartUUID) My apologies also for not providing logs, but I have to type these by hand...
> From the emergency shell, I see that /sysroot is empty. Note systemd will unmount everything when it enter emergency.target. From the emergency shell, does `systemctl status ostree-prepare-root.service` report an error?
It seems that my issue was a duplicate of this: https://bugzilla.redhat.com/show_bug.cgi?id=1765297
I pray I am not adding fuzz to this issue and will omit my failures with this on Workstation. Log into the emergency shell and view the log with `journalctl` Within the first few lines is a line with 'Command line: BOOT_IMAGE=' In my case only the path and kernel are listed, there is no 'root=' parameter listed or anything from /etc/default/grub (GRUB_CMDLINE_LINUX="quiet rhgb" is default I believe). I upgraded more than one machine from fc31 to fc32. Only one exhibits this issue. This machine will boot off the kernel/initrd created on fc32 upgrade. New kernels fail as described. For me, from the emergency shell: `mount --source /dev/sdH# --target /sysroot;exit` where sdH# is the root partition of Fedora (sda2 is perhaps common) continues the boot as normal.
SOLVED – For me at least. Short answer: Reinstall GRUB2 (BIOS based system) fedoraproject.org/wiki/GRUB_2 states in part: “The configuration format has evolved over time, and a new configuration file might be slightly incompatible with the old bootloader. It is therefore a good idea to first run grub2-install whenever you would need to run grub2-mkconfig. “ AND “grub2-install shouldn’t be used on EFI systems.” Apparently on my system, files from the installation of GRUB2 were no longer completely compatible with updated GRUB2 rpm packages. Backup your system, and reference the above wiki page and elsewhere if necessary, then reinstall GRUB2. Do not execute commands below without understanding (and a look at the wiki), but my specific commands for the impacted BIOS system (booted up from the emergency shell with the `mount` command in Comment Five) were: grub2-mkinstall /dev/sda; grub2-mkconfig -o /boot/grub2/grub.cfg If you are installing from a USB rescue environment, additional options likely will be needed for grub2-mkinstall (info grub2). If you are on a EFI booting system, a reinstall of GRUB2 may still be the solution to this issue. Side Note: I have a GRUB2 Fedora boot menuentry from prior to the switch to Boot Loader Specification in /etc/grub.d/40_custom, which does not use the kernelopts variable. It booted without issue while dealing with this problem. It must be manually maintained as new kernels are installed. ~
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.