Description of problem: On IBM blades and other systems using qla2xxx adapter the following description comes from IBM: Unfortunately mkinitrd does not think that for dm root device scsi_dh_rdac is needed. Hence in the stack of loaded modules scsi_dh_rdac is falling below the qla2xxx. Because of this, there will be TONs of error messages for each lun on each path. This causes long boot times, and sometimes random luns get only one path.
talk a bit with jvrao about this and it seems that if we use the --preload= option to mkinitrd things will work fine. We probably need to modify the specfile code for building the initrd to use --preload=scsi_dh_rdac whenever we see that qla2xxx is in use.
*** Bug 491323 has been marked as a duplicate of this bug. ***
Created attachment 360998 [details] dmesg output of bad boot RHEL5.3+ MRG 101
------- Comment From dvhltc.com 2010-03-31 12:40 EDT------- This is likely addressed for SAN-only systems by updates available in RHEL5.5 from Bug 47343. We need to test a multipath SAN install on RHEL5.5.
------- Comment From dvhltc.com 2010-03-31 18:17 EDT------- I have tested a RHEL 5.5 GA (RC2) install on elm9m84 (LS21) using "mpath" on the kernel boot parameter and the system installed fine to an mpath device during the installer. RHEL 5.5 is required, so we still have to use workarounds for RHEL5.[1234], but we have a solution if a customer wants it : move to RHEL5.5. Marking as closed.