Hi Vencent, The initial ramdisk includes modules, configuration files, and scripts needed to boot the system. Since everything works post-boot, I suspect that some initialization is the problem.
After looking through your information I am almost certain this is because during the init process LVM is grabbing the block devices BEFORE multipath gets the chance. Do you see that after the boot your volume groups are using scsi major numbers (8) instead of multipath (252)? It doesn't explain everything.. I would expect this to be a problem even for the second partition, not only when you create an LVM on partition 1. Nor does it explain why the volume group doesn't come up, yet it found it's PVs (directly instead of using the correct multipath). Take a look at this bug report, it is a familiar problem. You might have to recreate an initrd with the correct multipath and lvm config files, and also make sure the kernel modules you need are loaded. https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/246324 Sorry I do not have 11.10 installed or I would try to dig a bit deeper. Canonical does have a Technical Partner Program for vendors that want to have a formal relationship (technical partner manager) to make their devices work well out-of-the-box with Ubuntu. David -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/985741 Title: multipath can't show device on which is setup lvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/985741/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
