The 6.5.8 kernel booted to a dracut emergency shell because all but the first of its kernel command line parameters were removed #24

New issue

Open

opened 2024-09-30 17:49:04 +00:00 by humaton · 0 comments

humaton commented

2024-09-30 17:49:04 +00:00

Member

Please describe the problem: I updated a Fedora 39 KDE Plasma installation running the 6.5.7-300.fc39.x86_64 using a dnf offline-upgrade with updates-testing enabled. The upgrade contained kernel-6.5.8-300.fc39. The offline upgrade completed normally. On the first boot of 6.5.8, the Plymouth screen didn't appear. All the systemd and kernel messages were shown as when rhgb quiet was removed from the kernel command line. 6.5.8 kernel booted to a dracut emergency shell with the following errors shown. Failed to start initrd-switch-root.service - Switch Root. See 'systemctl status initrd-switch-root.service' for details Generating /run/initramfs/rdsosreport.txt Entering emergency mode. Exit the shell to continue. The journal showed the further errors with the switch root process. [ 14.221886] localhost.localdomain systemd[1]: Reached target initrd-switch-root.target - Switch Root. [ 14.232684] localhost.localdomain systemd[1]: Starting initrd-switch-root.service - Switch Root... [ 14.244150] localhost.localdomain @ystemctl[532]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. [ 14.245337] localhost.localdomain systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE [ 14.245580] localhost.localdomain systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. [ 14.256682] localhost.localdomain systemd[1]: Failed to start initrd-switch-root.service - Switch Root. [ 14.257352] localhost.localdomain systemd[1]: Startup finished in 4.840s (firmware) + 31.314s (loader) + 2.267s (kernel) + 0 (initrd) + 11.989s (userspace) = 50.412s. [ 14.257573] localhost.localdomain systemd[1]: initrd-switch-root.service: Triggering OnFailure= dependencies. [ 14.271724] localhost.localdomain systemd[1]: Started emergency.service - Emergency Shell. [ 14.272278] localhost.localdomain systemd[1]: Reached target emergency.target - Emergency Mode. The journal showed that the kernel command line only had its first parameter remaining. [ 0.000000] localhost.localdomain kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.5.8-300.fc39.x86_64 My normal kernel command line parameters which worked with 6.5.7 and earlier were BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.5.8-300.fc39.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rhgb quiet rdrand=force When I added the rest of my normal kernel command line parameters to 6.5.8 in grub, the system booted normally. Therefore, 6.5.8 booted to a dracut emergency shell because all but the first of its kernel command line parameters were removed by something likely in the update process. 2. What is the Version-Release number of the kernel: kernel-6.5.8-300.fc39 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 : Yes kernel-6.5.7-300.fc39.x86_64 worked normally. The problem appeared with kernel-6.5.8-300.fc39 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: 1. boot a Fedora 39 KDE Plasma installation running the 6.5.7-300.fc39.x86_64 kernel 2. log in to Plasma on Wayland 3. Start Konsole 4. Update to the kernel-6.5.8-300.fc39 with a dnf offline-upgrade with updates-testing enabled. sudo dnf offline-upgrade download sudo dnf offline-upgrade reboot 5. After the offline upgrade completes, boot 6.5.8 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: I haven't tried the latest Rawhide kernel. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with journalctl --no-hostname -k > dmesg.txt. If the issue occurred on a previous boot, use the journalctl -b flag. Reproducible: Always

1. Please describe the problem: I updated a Fedora 39 KDE Plasma installation running the 6.5.7-300.fc39.x86_64 using a dnf offline-upgrade with updates-testing enabled. The upgrade contained kernel-6.5.8-300.fc39. The offline upgrade completed normally. On the first boot of 6.5.8, the Plymouth screen didn't appear. All the systemd and kernel messages were shown as when rhgb quiet was removed from the kernel command line. 6.5.8 kernel booted to a dracut emergency shell with the following errors shown. Failed to start initrd-switch-root.service - Switch Root. See 'systemctl status initrd-switch-root.service' for details Generating /run/initramfs/rdsosreport.txt Entering emergency mode. Exit the shell to continue. The journal showed the further errors with the switch root process. [ 14.221886] localhost.localdomain systemd[1]: Reached target initrd-switch-root.target - Switch Root. [ 14.232684] localhost.localdomain systemd[1]: Starting initrd-switch-root.service - Switch Root... [ 14.244150] localhost.localdomain @ystemctl[532]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. [ 14.245337] localhost.localdomain systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE [ 14.245580] localhost.localdomain systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. [ 14.256682] localhost.localdomain systemd[1]: Failed to start initrd-switch-root.service - Switch Root. [ 14.257352] localhost.localdomain systemd[1]: Startup finished in 4.840s (firmware) + 31.314s (loader) + 2.267s (kernel) + 0 (initrd) + 11.989s (userspace) = 50.412s. [ 14.257573] localhost.localdomain systemd[1]: initrd-switch-root.service: Triggering OnFailure= dependencies. [ 14.271724] localhost.localdomain systemd[1]: Started emergency.service - Emergency Shell. [ 14.272278] localhost.localdomain systemd[1]: Reached target emergency.target - Emergency Mode. The journal showed that the kernel command line only had its first parameter remaining. [ 0.000000] localhost.localdomain kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.5.8-300.fc39.x86_64 My normal kernel command line parameters which worked with 6.5.7 and earlier were BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.5.8-300.fc39.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rhgb quiet rdrand=force When I added the rest of my normal kernel command line parameters to 6.5.8 in grub, the system booted normally. Therefore, 6.5.8 booted to a dracut emergency shell because all but the first of its kernel command line parameters were removed by something likely in the update process. 2. What is the Version-Release number of the kernel: kernel-6.5.8-300.fc39 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 : Yes kernel-6.5.7-300.fc39.x86_64 worked normally. The problem appeared with kernel-6.5.8-300.fc39 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: 1. boot a Fedora 39 KDE Plasma installation running the 6.5.7-300.fc39.x86_64 kernel 2. log in to Plasma on Wayland 3. Start Konsole 4. Update to the kernel-6.5.8-300.fc39 with a dnf offline-upgrade with updates-testing enabled. sudo dnf offline-upgrade download sudo dnf offline-upgrade reboot 5. After the offline upgrade completes, boot 6.5.8 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``: I haven't tried the latest Rawhide kernel. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Reproducible: Always