OVM2.1.2 with device-mapper-multipath is not finding the root partition
680720Apr 2 2009 — edited Aug 14 2009We are using multipathing (with mpath as a installation option), FC disks, and we are booting from an external SAN. After OVM2.1.2 installation, the system is not booting because of not being able to mount the root partition. Grub loads initrd and kernel image successfuly from the /boot disk (it's a SAN disk too), but, when the kernel loads the multipathing module (included in OVM installation), and then, tries to mount the root partition, device-mapper is not working as expected.See the following extract of the server's output:
device-mapper: multipath round-robin: version 1.0.0 loaded
Waiting for driver initialization.
Can't have a partition outside the disk!
device-mapper: table: device 67:192 too small for target
device-mapper: table: 253:1: multipath: error getting device
device-mapper: ioctl: error adding target to table
device-mapper: reload ioctl failed: Invalid argument
...
device-mapper: table: 253:3: multipath: error getting device
device-mapper: ioctl: error adding target to table
device-mapper: reload ioctl failed: Invalid argument
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
...
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
Hardware details: ProLiant BL480c G1, with QLogic QMH2462 4Gb FC HBA and an external EVA8000 SAN. Every LUN is seen by 8 different paths.
We've installed an OEL5u2, OEL5u3, RH5u3 in the same machine/SAN disks: all of them were working OK. For testing purposes, I've reinstalled the OVM servers, but now I'm using direct-attached disks to store the /boot and / partitions. Device-mapper is still not working with the SAN disks (but, right now, the system boots). I've installed OEL5u3 device-mapper and device-mapper-multipath rpms. Although I understand is not a supported/certified configuration (because of the different kernel versions), mpath is now working. I conclude, then, that we are affected by a device-mapper bug, present in the OVM shipped versions.
Any ideas? Do you know where can i find an OVM2.1.2 compatibility matrix?
Thanks!!
Daniel Caballero