1. Please describe the problem:
Kernel hangs in initramfs when trying to assemble a Soft-Raid that has been created by the Intel BIOS/UEFI.
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
Yes, it worked previously and the problem appeared with kernel-5.8.8-100.fc31.
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
- get a machine with Intel Mainboard and VROC softraid capability
- create a RAID1 with two suitable disks and install Fedora on this volume with a kernel previous to kernel-5.8.8-100.fc31 (suppress updates by cutting the network connection, else you might already get problems at first boot and have trouble to switch back and forth between old, functioning and new, defective kernel)
- upgrade to kernel-5.8.8-100.fc31
- the kernel hangs at boot
- manually switch back and forth between old and new kernel in grub to see the difference
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``:
The new kernel-5.8.9-101.fc31 does *not* have this problem.
6. Are you running any modules that not shipped with directly Fedora's kernel?:
VirtualBox and nvidia driver
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.
Without successful boot there is no easy way to get to a log.
I document this symptom here, as at first sight it's very different from the known bug https://bugzilla.redhat.com/show_bug.cgi?id=1878858.
The problem in connection with the Intel-RAIDs is confirmed also elsewhere:
For the ones who are affected and need a quick fix (like I did), the new kernel in testing solves the problem:
Maybe you need to force dnf to by-pass the mirrors and pull the testing kernel directly from Fedora, as at the moment none of the mirrors has synced it.
dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-5920a7a0b2 --repofrompath testing,https://dl.fedoraproject.org/pub/fedora/linux/updates/testing/31/Everything/x86_64
Good luck and thank you to the kernel team for already having a solution!
*** This bug has been marked as a duplicate of bug 1878858 ***