Bug 383641
Summary: | mdadm.conf incorrect, prevents boot after upgrade with 2 raid devices | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jon Burgess <jburgess777> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | bbaetz, pza |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-07 13:58:48 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: |
Description
Jon Burgess
2007-11-15 00:44:40 UTC
I can confirm this bug when upgrading from FC7 to FC8. I have 3 raid devices (md0 - raid 1, md1 - raid 5 and md2 - raid 0). anaconda somehow missed out md1 from my mdadm.conf, causing an unbootable system. Not sure why you think this is a low priority bug - I would have thought it should be medium or high. this is a duplicate of 242334. |