1. Please describe the problem: The system have Linux software raid (md) raid 1. One of the disk is missing or have problem. The raid is degraded. When the OS boot, it hangs at the message for outputting to kernel at about three seconds. There is no descriptive message that the RAID is degraded. I know the problem because I had wrote zero to one of the disk of the raid 1. If I don't know the problem (maybe cable is loose or disk failure), it is confusing. 2. What is the Version-Release number of the kernel: 5.4.12-200.fc31.x86_64 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 : N/A 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Having an OS with Linux raid1, then remove one of the disk from the array or writing zero to one of the disk in order to make the raid to be degraded. 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``: 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. Related log: [ 2.917387] sd 32:0:0:0: [sda] 56623104 512-byte logical blocks: (29.0 GB/27.0 GiB) [ 2.917446] sd 32:0:1:0: [sdb] 56623104 512-byte logical blocks: (29.0 GB/27.0 GiB) [ 2.917499] sd 32:0:0:0: [sda] Write Protect is off [ 2.917516] sd 32:0:0:0: [sda] Mode Sense: 61 00 00 00 [ 2.917557] sd 32:0:1:0: [sdb] Write Protect is off [ 2.917575] sd 32:0:1:0: [sdb] Mode Sense: 61 00 00 00 [ 2.917615] sd 32:0:0:0: [sda] Cache data unavailable [ 2.917636] sd 32:0:0:0: [sda] Assuming drive cache: write through [ 2.917661] sd 32:0:1:0: [sdb] Cache data unavailable [ 2.917677] sd 32:0:1:0: [sdb] Assuming drive cache: write through [ 2.927076] sd 32:0:0:0: [sda] Attached SCSI disk [ 2.927458] sdb: sdb1 sdb2 sdb3 sdb4 [ 2.929018] sd 32:0:1:0: [sdb] Attached SCSI disk [ 3.060855] vmxnet3 0000:0b:00.0 ens192: intr type 3, mode 0, 3 vectors allocated [ 3.061826] vmxnet3 0000:0b:00.0 ens192: NIC Link is Up 10000 Mbps [ 139.411464] md/raid1:md125: active with 1 out of 2 mirrors [ 139.412176] md125: detected capacity change from 0 to 1073676288 [ 139.433441] md/raid1:md126: active with 1 out of 2 mirrors [ 139.434182] md126: detected capacity change from 0 to 314507264 [ 139.436894] md126: [ 139.455511] md/raid1:md127: active with 1 out of 2 mirrors [ 139.456739] md127: detected capacity change from 0 to 27582726144 So there are about 130 seconds without any descriptive messages. I thought the system had hanged. Which component is responsible to display error messages?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those.
The problem persisted in kernel 5.5.7-200.fc31.
Would someone take a look on the ticket? Please help or comment instead of waiting for the next message like: *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 32 kernel bugs. Fedora 32 has now been rebased to 5.x.x-xxx.fc32. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 33, and are still experiencing this issue, please change the version to Fedora 33. If you experience different issues, please open a new bug report for those.
You are most likely to get some traction on this by pushing upstream. This is not a bug so much as a feature request.