Bug#381181: mdadm fix affects root-on-LVM-on-RAID

[John Gruenenfelder]

Hello,

I set my system up some time ago to use root on LVM on RAID.  Not just root,
actually, but all filesystems are on LVM on RAID with the exception of /boot
which is just on RAID.

With the latest update to mdadm, my system could no longer boot properly.
Before I found this bug report, I managed to trace the problem on my own.

Now that udev no longer creates the /dev/md* devices, the lvm startup script
cannot find my volume groups.  Without those I am missing most of my
filesystems and cannot boot.

As a quick fix, I can boot into single user mode, create /dev/md0 and /dev/md3
(the two which I need), run /etc/init.d/lvm, and then mount my filesystems.
At that point I can continue the normal boot process.

Now, I roll my own kernel via make-kpkg and the initrd I created on my own to
get this setup working, so perhaps there is some Debian specific way of
handling this that I am not doing correctly.

So... what is the best fix for this?  Is there some fix I'll need to make to
my initrd?  Or will removing /etc/udev/mdadm.rules be enough to cause udev to
go back to the old behavior?


-- 
--John Gruenenfelder    Research Assistant, UMass Amherst student
                        Systems Manager, MKS Imaging Technology, LLC.
Try Weasel Reader for PalmOS  --  http://gutenpalm.sf.net
"This is the most fun I've had without being drenched in the blood
of my enemies!"
        --Sam of Sam & Max