1. Please describe the problem:
I cannot boot with kernel 5.10 on Fedora Silverblue.
The boot process is stuck on attempt to mount root filesystem:
"A start job is running for /dev/disk/by-uuid/..."
2. What is the Version-Release number of the kernel:
3. Did it work previously in Fedora? If so, what kernel version did the issue
*first* appear? Old kernels are available for download at
All 5.9.x works for me. Any 5.10 kernel from koji is broken.
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
rpm-ostree override replace kernel-5.10.4-200.fc33.x86_64.rpm kernel-core-5.10.4-200.fc33.x86_64.rpm kernel-devel-5.10.4-200.fc33.x86_64.rpm kernel-modules-5.10.4-200.fc33.x86_64.rpm kernel-modules-extra-5.10.4-200.fc33.x86_64.rpm
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 tested 5.11 rawhide kernels yet.
6. Are you running any modules that not shipped with directly Fedora's kernel?:
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.
I don't have saved logs since rootfs isn't mounted.
* This is silverblue specific. I can boot this on Fedora Workstation
* Behaves the same on a system with or without luks (disk encryption)
* Happens on both VM or host itself
* Can this be related to Bug 1900061 ?
Still broken for me with kernel-5.10.5-200.fc33
I can confirm this on my existing bare metal Silverblue installation and on a fresh VM Silverblue installation with disk encryption enabled. I can't reproduce it with an unencrypted installation.
The kernel comes up fine, but systemd is stuck waiting for the disk, and the disk decryption prompt is never shown.
I can also reproduce this issue using rawhide kernel 5.11.0-0.rc2.114.fc34.x86_64.
I'm no longer able to reproduce this issue in the released version of 5.10.6-200.fc33.x86_64.
(In reply to Evan Anderson from comment #4)
> I'm no longer able to reproduce this issue in the released version of
The same here. All works as expected now!