Created attachment 477963 [details]
storage log from install attempt
Description of problem:
software raid 10 device not assembled
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot F15A1 prerelease
2. work thru and select manual partitioning
Do not see VolGroup00 which resides on a raid 10 PV.
(also ran into the missing interface component error)
See all md devices, VGs, LVs
do not see any raid devices in tty-2 with ls /dev/m* Should see md127, md0 md127p1 md127p2
Can you also attach /tmp/syslog and /tmp/anaconda.log?
Created attachment 478121 [details]
Created attachment 478122 [details]
Adding to proposed list for F15Alpha. I don't initially think this impacts the F15Alpha criteria , which more focuses on more common, default, partition schemes. However, a case can be made that this impacts the Beta criteria . Will discuss during the meeting.
Agree with jlaska, -1 Alpha.
Per 2011-02-11 Alpha blocker meeting -
#agreed 676519 - does not impact Alpha release criteria - move to F15Beta and review RAID criteria for Beta
Redid TC1 install and noticed following:
Raid 10 device IS SEEN by the partitioner in the custom layout screen, but is marked as unknown and not identified as a PV. In tty-2, it is still not seen in /dev. If I copy the correct mdadm.conf to /etc in tty-2, do a mdadm --assemble /dev/md127, go back to tty-6 and BACK a few screens, then go forward, /dev/md127 is correctly seen as the PV and the VG/LVs are correctly displayed.
Please attach /tmp/program.log to this but report.
Created attachment 479193 [details]
From original attempt not attempt in comment 7 where I discovered anaconda did see md127 but didn't start it. Let me know if I need to redo the install and get new logs, happy to do it.
I was able to reproduce it here. Thanks.
This should definitely block the F15 Beta as it prevents us from detecting existing formatting on any md array with more than one member device.
Fixed on master, waiting on results of blocker meeting to determine whether this makes it onto f15-branch.
This may be related, if not will file a new bz:
On a different machine with Intel bios raid 10, the installer says during/after first device detection:
"Disks sdb, sdc, sdd, sde contain BIOS RAID metadata, but are not part of any recognizable BIOS RAID sets. Ignoring disks sdb, sdc, sdd, sde."
If I reboot and put the proper mdadm.conf in /etc in tty-2 and then mdadm --assemble the container and then the array, the installer then sees the raid 10 set during first device detection and properly shows it and the LVs in the partitioner.
Moving F15Beta to bug 680474, which is an F15 bug.
Clyde, your problem in comment 13 is probably unrelated, and I certainly cannot know for sure until I have seen the logs -- please file a separate report for it.