Red Hat Bugzilla – Bug 174559
Enhancement+Patch: Use mdadm with mkinitrd
Last modified: 2008-03-09 21:11:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.7.12) Gecko/20050929
Description of problem:
This patch causes mkinitrd to add mdadm.static to <initrd>/bin and to have <initrd>/init run mdadm instead of raid0run.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. The initrd doesn't work with RAID1.
2. Patch mkinitrd to use mdadm
3. mkinitrd produces a working initrd.
Created attachment 121621 [details]
Patch to modify mkinitrd to use mdadm
What do you mean by "the initrd doesn't work with RAID1"? It works fine for me
with raid 1.
Even so, why would we want to add a 700k binary to the initrd as the "solution"?
Well, I tried it with RAID1 and it didn't work until I changed the script to use
You would add a 700k binary because, AFAIK, the tools it currently uses are
deprecated. mdadm is the new standard. Also, mdadm doesn't depend on the RAID
members being detected. They are specified on the command line. Of course I
recognize the flip-side, which is that the mkinitrd won't know how to wake up in
a modified RAID environment.
Fedora Core 4 is no longer maintained.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.