Bug 1835101
| Summary: | arrays are considered as degraded during boot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | hw |
| Component: | mdadm | Assignee: | Jes Sorensen <jes.sorensen> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 32 | CC: | agk, dledford, jes.sorensen, xni |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-25 16:15:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: After installing Fedora server, booting takes rather long, and there messages on the console about waiting for jobs involving disks by uuid. There is a bunch of messages in /var/log/messages about this: May 13 06:56:58 himinbjorg kernel: Adding 16776188k swap on /dev/md127. Priority:-2 extents:1 across:16776188k SSFS May 13 06:56:58 himinbjorg systemd[1]: Activated swap /dev/disk/by-uuid/0b027ec3-d496-4ed8-91f7-e41312af7aac. [...] May 13 06:58:54 himinbjorg kernel: md/raid1:md100: active with 2 out of 2 mirrors May 13 06:58:54 himinbjorg kernel: md100: detected capacity change from 0 to 8001428979712 May 13 06:58:57 himinbjorg systemd[1]: Started Timer to wait for more drives before activating degraded array md100.. May 13 06:58:58 himinbjorg systemd[1]: systemd-udev-settle.service: Main process exited, code=exited, status=1/FAILURE May 13 06:58:58 himinbjorg systemd[1]: systemd-udev-settle.service: Failed with result 'exit-code'. May 13 06:58:58 himinbjorg audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:> May 13 06:58:58 himinbjorg systemd[1]: Failed to start udev Wait for Complete Device Initialization. May 13 06:58:58 himinbjorg systemd[1]: Reached target System Initialization. May 13 06:58:58 himinbjorg systemd[1]: Started dnf makecache --timer. [...] May 13 06:59:03 himinbjorg kernel: md/raid1:md126: active with 2 out of 2 mirrors May 13 06:59:03 himinbjorg kernel: md126: detected capacity change from 0 to 537853952 May 13 06:59:03 himinbjorg kernel: md126: May 13 06:59:03 himinbjorg systemd[1]: Started Timer to wait for more drives before activating degraded array md126.. [...] May 13 06:59:27 himinbjorg systemd[1]: Condition check resulted in Activate md array md100 even though degraded being skipped. [...] May 13 06:59:35 himinbjorg systemd[1]: Condition check resulted in Activate md array md126 even though degraded being skipped. Version-Release number of selected component (if applicable): Fedora server, freshly installed today cat /proc/mdstat Personalities : [raid1] md126 : active raid1 sdb2[1] sda2[0] 525248 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk md100 : active raid1 sdd[1] sdc[0] 7813895488 blocks super 1.2 [2/2] [UU] bitmap: 0/59 pages [0KB], 65536KB chunk md127 : active raid1 sda1[0] sdb1[1] 16776192 blocks super 1.2 [2/2] [UU] unused devices: <none> md127, which is used for swap, is not mentioned in the error messages. None of the arrays seem to be actually degraded. When the login prompt finally appears, the arrays seem ok. I don't know how to reproduce this other than installing Fedora and creating some mdraid partitions with the installer. md100 was created with Centos 7 and has been working fine there. Maybe this is a problem with systemd or udev or the kernel and not so much with mdadm ...