kys-fedora at ilzey.net
Thu Jul 3 08:12:59 UTC 2008
On Wed, 2008-07-02 at 19:50 -0400, jeff at bubble.org wrote:
> I've been successfully running RAID1 since the Fedora 7 days on this system.
> This morning I processed the new "updates" on the system (Fedora 9 x86_64),
> since one of the updates was a new kernel I rebooted the machine (first
> time in about a month which may be a clue to other software updates!)
> At this point the system does not reboot and fails with the RAID partitions.
> Specifically I get to the point in the bootup "Waiting for driver
> initialization" and then it follows with
> I have tried removing my /etc/mdadm.conf to allow it to automatically find
> the devices but no change.
> After some searching I found two bugzillas that seem to be appropriate but
> I am still unable to boot the system. The links are:
There is also my bug listed against mkinitrd:
The initrd only appears to start the first md device, no matter what is
in your /etc/mdadm.conf (the one in the initrd is correct and has all my
The init script only does this:
mdadm -As --auto=yes --run /dev/md0
Rather than, as I think it should:
mdadm --assemble --scan
Luckily my first raid device contains all the partitions I need to boot,
the second is my home dir and data partitions, so I can get to single
user mode and start everything by hand.
More information about the fedora-list