On Mon, Apr 25, 2011 at 22:17, Donald Russell <russell....@gmail.com> wrote:
> 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. > <snip> The Reader's Digest version of this is I put /boot on a 3390 minidisk, and / on mapper/mpath0 and specified all the paths on the FCP_n= statements in the parm file. Kickstart was happy, and the firstboot worked correctly. /boot cannot be on an mpath device. This changes in RHEL 6 apparently, but I've not had the opportunity to try that yet. ---------------------------------------------------------------------- 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/
