Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
== Comment: #0 - INDUSHREE GANGADHARA SHASTRY <igangadh.com> - 2013-06-14 01:40:55 ==
The issue is observed while installing the Feodora 19 on zvm
1. Attach the scsi adapter to zvm
2. Provide all the information about the scsi disk in rd.zfcp params files
3. Start the installation
4. Select the SCSI disk ..reclaim space and go for auto partition
5. Provide the root password
6. Once the installation completes click on reboot
3E: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and
store status from CPU 00.
3F: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and
store status from CPU 00.
00: HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000 0002885E
But if you manually IPL the scsi adapter than system comes up
[root@r3530054 anaconda]# cat /etc/issue
Fedora release 19 (Schr?dinger?s Cat)
Kernel \r on an \m (\l)
[root@r3530054 anaconda]# cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Fri Jun 14 05:25:41 2013
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/fedora_r353005400-root / ext4 defaults 1 1
/dev/mapper/fedora_r353005400-boot /boot ext4 defaults 1 2
/dev/mapper/fedora_r353005400-swap swap swap defaults 0 0
[root@r3530054 anaconda]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/fedora_r353005400-root 6.3G 2.8G 3.2G 48% /
devtmpfs 1.5G 0 1.5G 0% /dev
tmpfs 1.5G 0 1.5G 0% /dev/shm
tmpfs 1.5G 252K 1.5G 1% /run
tmpfs 1.5G 0 1.5G 0% /sys/fs/cgroup
tmpfs 1.5G 4.0K 1.5G 1% /tmp
/dev/mapper/fedora_r353005400-boot 477M 71M 381M 16% /boot
[root@r3530054 anaconda]# lszfcp -D
0.0.3c15/0x500507630508c1ae/0x402040b100000000 0:0:11:1085358112
It is caused by wrong WWPN/LUN values returned by chreipl. See program.log you attached:
...
05:31:31,606 INFO program: Running... chreipl node /dev/sda
05:31:31,618 INFO program: Re-IPL type: fcp
05:31:31,619 INFO program: WWPN: 0x00500507630508c1
05:31:31,619 INFO program: LUN: 0x00402040b1000000
05:31:31,619 INFO program: Device: 0.0.3c15
05:31:31,619 INFO program: bootprog: 0
05:31:31,619 INFO program: br_lba: 0
05:31:31,619 INFO program: Bootparms: ""
05:31:31,619 DEBUG program: Return code: 0
...
Correct values for WWPN and LUN are:
0x500507630508c1ae/0x402040b100000000
Reassigning to s390utils.