Red Hat Bugzilla – Bug 157680
mkinitrd fails to setup partitionable md device and uses deprecated autorun facility
Last modified: 2007-11-30 17:11:06 EST
Description of problem: Raidautorun is deprecated and doesn't start all possible
md array configurations properly. Also, the detection of valid md devices is
broken for partitionable md devices.
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. Create a partionable md device using a raid level not used in any regular md
2. Run mkinitrd
mkinitrd will fail to load the raid level module for the partitionable device
and will fail to start the device
Patch to fix problem attached. Patch does two things. 1) it corrects the
detection of partitionable md device in the /proc/mdstat file so that they get
processed properly. 2) it replaces raidautorun with mdadm -A --scan which will
read the various arrays from the newly installed mdadm.conf file and attempt to
start all arrays that it can find by scanning the available devices.
Created attachment 114348 [details]
This patch needs to conditionalize use of raidautorun vs mdadm.static based on
<dledford> pjones: This is a "well formed" /etc/mdadm.conf file:
<dledford> MAILADDR root
<dledford> DEVICE partitions
<dledford> ARRAY /dev/md0 level=multipath num-devices=2
<dledford> ARRAY /dev/md1 level=multipath num-devices=2
<dledford> ARRAY /dev/md2 level=multipath num-devices=2
<dledford> ARRAY /dev/md3 level=multipath num-devices=2
<dledford> ARRAY /dev/md_d0 level=raid0 num-devices=4
(This is a mass update of bugs which have been in the NEEDINFO state unmodified
for over a year and have not been confirmed for a still supported version of
Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.