Hum, that's kind of weird. You should see disks being picked up by multipath if they should, even if they are detected *after* multipath scripts run (because multipathd...). They wouldn't be detected before multipath runs, because then they would most likely be remapped anyway (unless something else claims them).
Could you file a new bug for this, including the output of multipath -v4 taken from the initramfs? You may stop the boot process by adding "break=pre-multipath" to break boot just before the multipath scripts. At that point, you'll need to modprobe dm_multipath; and then you should be able to run multipath -v4. If you exit from there boot should complete (hopefully succesfully, since there will have been some extra delay).
Hum, that's kind of weird. You should see disks being picked up by multipath if they should, even if they are detected *after* multipath scripts run (because multipathd...). They wouldn't be detected before multipath runs, because then they would most likely be remapped anyway (unless something else claims them).
Could you file a new bug for this, including the output of multipath -v4 taken from the initramfs? You may stop the boot process by adding "break= pre-multipath" to break boot just before the multipath scripts. At that point, you'll need to modprobe dm_multipath; and then you should be able to run multipath -v4. If you exit from there boot should complete (hopefully succesfully, since there will have been some extra delay).