Bug 744217
Summary: | kernel-2.6.40-4.fc15.x86_64 fails to boot due to failure to start MD RAID | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Doug Ledford <dledford> |
Component: | mdadm | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | agk, awilliam, bugzilla, conrad.leonard, dev, dledford, Jes.Sorensen, mbroz, michael.wuersch, msmsms10079, pb, rhbugzilla, sandro, serge |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | AcceptedBlocker | ||
Fixed In Version: | mdadm-3.2.2-12.fc16 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 736387 | Environment: | |
Last Closed: | 2011-10-25 03:30:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 713568 |
Description
Doug Ledford
2011-10-07 14:07:51 UTC
mdadm-3.2.2-11.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mdadm-3.2.2-11.fc16 Using the version from koji 3.2.2-10.fc15 the behavior looks good again, after 2nd boot it starts syncing from the last position (like old version did) and device is detected proper in verify state. Package mdadm-3.2.2-11.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mdadm-3.2.2-11.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-14682 then log in and leave karma (feedback). Neil Brown (mdadm maintainer) spotted a bug in one of my fixes. I'll update and push a fixed version. mdadm-3.2.2-12.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mdadm-3.2.2-12.fc16 Package mdadm-3.2.2-12.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mdadm-3.2.2-12.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-14767 then log in and leave karma (feedback). Suggest blocker for F16. This one is really painful for people who get bitten by it and it can prevent booting and/or install. Jes Failed QA test criteria: "This install verifies that installing on a BIOS RAID device works properly.", i.e. "System boots successfully recognizing filesystems created on the BIOS RAID device(s)", see https://fedoraproject.org/wiki/QA:Testcase_Install_to_BIOS_RAID Discussed at 2011-10-24 blocker review meeting. As we understand this bug, it causes the system to fail to boot properly if a RAID array is degraded: as such, we accept it as a blocker under the intersection of criteria "The installer must be able to create and install to software, hardware or BIOS RAID-0, RAID-1 or RAID-5 partitions for anything except /boot" and "Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied" - a system with a degraded RAID array should boot and allow you to rebuild the array, not fail to boot. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers mdadm-3.2.2-12.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |