Description of problem:
When setting up RAID (mirroring) devices anaconda reverses the allocations made
eg at set up screen
MD0 sda1 sdb1 (Operating System) 35gb
MD1 sda2 sdb2 (data file system) 200gb
MD0 sda2 sdb2 (data file system) 200gb
MD1 sda1 sdb1 (Operating System) 35gb
After anaconda commits changes to disk
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup raid
2. commit actions
Old versions of anaconda used to similarly re arrange hard disk partition allocations, sda1,2,3 etc. This was annoying and I found confusing
The partitions now allocate logically sda1 beginning of disk through to sd? at end of disk
Seems the script to do the md devices has not been updated
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
But as documented as a known issue having a / on a mdraid mirror without a separate /boot does not work in F-13:
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.
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