Bug 603297
Summary: | Anaconda reverses MD0/1 allocations | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Wayne Carruthers <bugs> |
Component: | anaconda | Assignee: | Hans de Goede <hdegoede> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | anaconda-maint-list, jonathan, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-24 10:48:40 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
Wayne Carruthers
2010-06-12 08:41:00 UTC
Hi, Thanks for the bug report. I've tried to reproduce this, and during the installation the different md-raid sets got the same md# as indicated in the UI, and the written /etc/mdadm.conf also had the proper UUID's there to make the numbering stick after reboot. But as documented as a known issue having a / on a mdraid mirror without a separate /boot does not work in F-13: https://fedoraproject.org/wiki/Common_F13_bugs#Booting_from_an_mdraid_mirror_without_a_separate_.2Fboot_fails I then boot into rescue mode, and look and behold md0 and md1 got swapped. This is a known issue, where we give pre-existing mdraid's a random md# number instead of taking the number they had before from their superblock This is fixed by this commit which will be in F-14. http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=b213dceca01acfedf97afdc917c8cc7a871417c3 So summarizing: 1) Doing an mdraid mirror install without a separate /boot does not work in F-13, this is a known issue which is fixed for F-14. To work around this do an install with a separate /boot 2) When starting anaconda with pre-existing mdraid sets (such as when booting rescue mode after the failure caused by 1.) The mdraid sets do not always get the correct minor number. this also is a known issue which is fixed for F-14. Thank you for your efforts, they are appreciated |