When I install RHEL on FCP/SCSI if I specify only FCP_1 in the CMS file parm file everything goes fine. When I specify a second (or more) path (FCP_2 etc) everything goes fine right up until the reboot after installing everything.
At that point I get CP Interrupt loop detected, and it goes to CP READ. What I'm hearing now is that zipl does not support having the boot partition on an mpath device... is that true? If so, I think I'll just create an EDEVICE for than LUN and define all the paths in VM. But, can anybody point me to some (current) doc that describes how to setup/perform a kickstart install on FCP using multiple paths, and have a working system at the end. ;-) Sorry if I sound a little terse, I've just lost a lot of time due to out-of-date and/or incorrect documentation. (Yes, I have cases open with Red Hat and they are in the process of updating/correcting the doc) So, I'm hoping somebody has blazed this trail before me and can share some insight. :-) Cheers ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
