1. Please describe the problem: I can boot 6.4.10 just fine, the issue appeared with 6.4.11 and persists with 6.4.12. The boot fails with a message about initrd-switch-root.service and it being unable to find sysroot. 2. What is the Version-Release number of the kernel: 6.4.12 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : First in 6.4.11 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Any reboot to the current 6.4.12 kernel reproduces the issue 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: My workaround is to instruct grub to boot 6.4.10 until this gets fixed. I tried running dracut --force --regenerate-all while running 6.4.10, then tried the reboot again to 6.4.12 but this did not fix things (and it filled up my /boot with all kinds of images for old 5.x.y kernels). Reproducible: Always
Here is the tail end of the rdsosreport.txt file. the entire file can be viewed here: http://cholla.mmto.org/fedora/rdsosreport.txt [ 3.145368] trona.mmto.org systemd[1]: Finished initrd-udevadm-cleanup-db.service - Cleanup udev Database. [ 3.146912] trona.mmto.org systemd[1]: Reached target initrd-switch-root.target - Switch Root. [ 3.160432] trona.mmto.org systemd[1]: Starting initrd-switch-root.service - Switch Root... [ 3.168212] trona.mmto.org @ystemctl[543]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. [ 3.169287] trona.mmto.org systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE [ 3.169565] trona.mmto.org systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. [ 3.180338] trona.mmto.org systemd[1]: Failed to start initrd-switch-root.service - Switch Root. [ 3.180833] trona.mmto.org systemd[1]: Startup finished in 1.565s (kernel) + 0 (initrd) + 1.615s (userspace) = 3.180s. [ 3.180901] trona.mmto.org systemd[1]: initrd-switch-root.service: Triggering OnFailure= dependencies. [ 3.192372] trona.mmto.org systemd[1]: Started emergency.service - Emergency Shell. [ 3.192637] trona.mmto.org systemd[1]: Reached target emergency.target - Emergency Mode.
Well, let's see. It has been over a month now and this has gotten no attention whatsoever. I am a bit surprised. I keep trying new kernels as they come along in the updates, but they all fail in the same way. The latest I have tried was just now -- 6.5.5. My hope was this would just "get fixed" but I am not getting lucky. But the only way I can run my system is to use the Grub menu and manually select the 6.4.10 kernel, which does run, and is what I am using now. Does anyone know what I can do to be able to run an update later that 6.4.10 withou initrd-switch-root.service being unable to find sysroot ?
The kernel is likely not your issue. It appears (as is typically the case with failed switch-root) that your grub command line is missing a lot of things it should have. Compare your grub command line for the working kernel to the command line for the non-working kernel. If you are missing some parameters, such as root= add the missing ones back and see if that fixes things.
Thank you! I am sure you are correct, the kernel per se is not my issue. All I know is that I run dnf-cron, new packages arrive, and now when I reboot the system to the current package set (i.e. "the new kernel") things no longer work. So it doubtless is not the kernel itself, but something that came along for the ride with the new kernel packages. I'll investigate your tip about the grub command line. Why am I the only one experiencing this? Indeed I have not done a from scratch install in years (I always do dnf upgrades), so perhaps I have accumulated some unique cruft that I am not clever enough to sort out.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.