Description of problem: Version-Release number of selected component (if applicable): RHEL5.1 DVD How reproducible: everytime Steps to Reproduce: 1. do a kickstart install to SAN boot a system with two SAN drives presented over two HBA paths and 1 local disk array cciss/c0d0 2. sda has redundant path sdc and sdb had redundant path sdd 3. in kickstart file, specify --ignoredisks=sdc,sdd and /boot and root install to sda Actual results: system isn't installed to sda as directed and grub is installed on the local disk array, cciss/c0d0, when booting, stop as a "grub>" prompt. Expected results: system installed with grub in sda. Additional info: I am able to work around this by having our SAN disabled the second path, so only sda and sdb are seen during install
Created attachment 302143 [details] example ks file
Wonder if the san devices are getting added to DiskSet.skippedDisks?
Why aren't you using multipath instead of specifying "sda" here?
is mpio supported for SAN booting? wasn't able to find that documented. Our current solution is to use EMC's PowerPath after the initial kickstart is complete, but I'd much rather go with mpio, if you can point me in the right direction.
With RHEL 5.2, the multipath device should be autodetected and show up as /dev/mapper/mpath0 (with partitions being mpath0p1, mpath0p2, etc.). Is that not working?
no, that is not occurring. I just tried replacing the sda references in the ks file with mpath0 and it wouldn't install. This is red hat 5.1. I'll download the 5.2 beta and see if I get the mpio devices.
NAKing as we are likely not going to have the capacity to get this fixed in 5.3. Please do try out 5.2 and see if it's working better for you, though, as we think that should be the case.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.