mdadm (2.4.1-6ubuntu5) edgy; urgency=low
* Modify initrafms scripts to wait for devices to appear if they are not there
yet when the script is executed on boot:
- copy generated mdadm.conf in the initramfs (we need the UUIDs)
- modify local-top script to wait for all UUIDs to appea
** Changed in: initramfs-tools (Ubuntu)
Sourcepackagename: initramfs-tools => mdadm
--
[EDGY] Regression: can't boot from lvm root on raid anymore
https://launchpad.net/bugs/52740
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Yes i found the reason finally yesterday. It's a race condition between
devices that forms the raid and contain the lvm root to appear in /dev
and the time when mdrun and lvm are executed in the initramfs. lvm is
already partially fixed (for root on lvm only). I need to integrate a
more general fix
I have the same issue but my solution isn't as simple.
Using hints from the 'init' script I can bring my system up with:
# modprobe dm_mod
# /scripts/locat-top/lvm
1 logical volume(s) in volume group "foobar" now active
# mount -t ext3 /dev/mapper/foobar-vg /root
[ 134.664391] kjournald sta
