Hide Forgot
Created attachment 498108 [details] anaconda log Description of problem: I have some systems that have SAN data disks attached. When they were installed with 6.1 the SAN disks were part of the VG that contained the boot disk etc. Now that I am trying to install 5.7 on those systems, the install fails when it tries to create the VG/LV for the install. This seems to happen on every system that had RHEL 6.1 installed and did an LVM install. logs will be attached.
Created attachment 498109 [details] console log
Created attachment 498110 [details] kick start file
Created attachment 498112 [details] lvm log
Created attachment 498113 [details] sys log
Barry can you lend me one of the machines where you see this in beaker? If you restart the rhel5 installation, does it succeed the second time? Also, do you mean multipath by SAN? Because if multipath was used in RHEL6 for the PV then RHEL5 might be confused when it sees five devices with the same UUID. If you think that might be the case, try with 'multipath' on the kernel command line before starting the rhel5 installation.
I just loaned you storageqe-07.lab.bos.redhat.com
Barry, I tried the default beaker install of 0510 rhel5 nightly on the machine and it indeed fails. However I found that the drives /dev/sde through /dev/sdk are the same multipath device. In those cases the rhel5 installer needs to be told to switch to 'multipath mode', by the mpath boot parameter: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/ch-bootopts-x86.html I think if this particular machine keeps the multipath device connected the 'mpath' command line boot option should be added to the default options in beaker. I think we can close this as not a bug.
I thought I had tried that but clearly not. thanks,
(In reply to comment #10) > I thought I had tried that but clearly not. thanks, maybe because I misinformed you in comment 5. the kernel option is "mpath" not "multipath".