Description of problem:
Version-Release number of selected component (if applicable):
100% Reproducable for any raid 5 sets attempted to be installed to
Steps to Reproduce:
1. Configure a RAID 5 in the BIOS
2. Attempt an install F7 to the RAID set
3. First sign of trouble is Anaconda claiming it can't open /dev/mapper/nvida_xxxxxx
4. From there hit ALT-F2 to get the console
5. dmraid -r and dmraid -s will show info on the raid set
6. dmraid -ay yields an error that 'raid45' could not be loaded
7. lsmod | grep raid shows that in fact the raid456 module is loaded (and i
assume should suffice). regardless the tool refuses to proceed further.
Apparently kernel 2.6.20 changed the name of the module, requiring an update to
dmraid as well.
dmraid will honour the raid456 module to satisfy it's dependancies.
This is preventing the installation of FC7 onto the volume completely. I assume
new media will need to be made available to correct the problem.
Some related links for other peoples bugs that reflect the same issue in
Errr - how did this get assigned to me??? Is something broken in Fedora bugzilla?
Not sure, it autofilled your address after i selected the package.
It's looking like the Core/Extras merge obliterated default owner and initial cc
list for Fedora Core bugzilla components. This was not announced so clearly it
was unintentional and should be fixed globally and mentioned in the
post-implementation review for that change, so lessons can be learned for next
time bugzilla data edits are made.
These said nothing about losing previous settings for Core packages:
Dmraid cannot use raid456 kernel module for RAID5 mapping (it is module for MD
device, not device-mapper target), it needs separate dm-raid45 kernel module
which is not yet in stable kernel.
For testing development version you can see
But this will not merged in F7 release cycle, RAID5 mapped through dmraid (i.e.
created by bios utility) is not supported yet (but you can use software MD raid5
in install process of course) .