Re: Goldimage Redhat 7.1

[Kumar]

I am past the initial errors but it still fails to complete the
installation, i get below errors. I cannot ssh to it using 'install' user
id. But can ssh to it using 'root' id

Error

The following error occurred while installing.  This is a fatal error and
instal
lation will be aborted.

error populating transaction after 10 retries: failure:
Packages/perl-HTTP-Tiny
-0.033-3.el7.noarch.rpm from anaconda: [Errno 256] No more mirrors to try.


Regards,
Kumar

On Fri, Dec 23, 2016 at 2:33 PM, Kumar  wrote:

> Hi Mike and Berry,
>
> Thank you for the responses.
>
> There is indeed 'IPL 00C CLEAR' , I missed to copy it in my first email.
>
> I followed Mike's update and added  the pipe in the line  'PIPE CP PURGE
> RDR ALL  HOLE'
> I also added 'CP QUERY * READER ALL' and re-tried the SETUP and it took a
> while and when i came back and saw my session i see below screen
>
> dracut://#
>
> I will retry again today and see what happens.
>
>
> Regards,
> Kumar
>
>
>
>
> On Thu, Dec 22, 2016 at 8:05 PM, van Sleeuwen, Berry <
> berry.vansleeu...@atos.net> wrote:
>
>> Hi Kumar,
>>
>> The HCP232E error is an IPL error. What device are you trying to IPL? You
>> didn't specify the IPL command after the punch of the linux images. Since
>> you punch the files, you would like to IPL from the RDR device 00C.
>>
>> My (SLES) exec looks like:
>> /**/
>> 'CLOSE RDR'
>> 'PURGE RDR ALL'
>> 'SPOOL PUNCH * RDR'
>> 'PUNCH SLES122 IMAGE A (NOH'
>> 'PUNCH SLES122 PARMFILE  A (NOH'
>> 'PUNCH SLES122 INITRD A (NOH'
>> 'CHANGE RDR ALL KEEP NOHOLD'
>> 'IPL 00C CLEAR'
>>
>>
>>
>> Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
>> Berry van Sleeuwen
>>
>> -Original Message-
>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>> Kumar
>> Sent: Thursday, December 22, 2016 3:15 PM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Goldimage Redhat 7.1
>>
>> Hi,
>>
>> We are trying to build a gold image for Redhat 7.1 and it fails with
>> below error.
>>
>> *1
>> *
>>
>> *DMSFOR732I 6676 cylinders formatted on Z(201)
>>*
>>
>> *DMSACR723I I (AB:LINUX999.RHEL71)
>> R/O *
>>
>> *00: RDR FILE 0058 SENT FROM LINUX999 PUN WAS 0058 RECS 047K CPY  001 A
>> NOHOLD NOKEEP  *
>>
>> *00: RDR FILE 0059 SENT FROM LINUX999 PUN WAS 0059 RECS 0006 CPY  001 A
>> NOHOLD NOKEEP  *
>>
>> *00: RDR FILE 0060 SENT FROM LINUX999 PUN WAS 0060 RECS 329K CPY  001 A
>> NOHOLD NOKEEP  *
>>
>> *HCPVMJ232E IPL UNIT ERROR; IRB 01404417 0010 00202101
>> 0080*
>>
>> *00: HCPGIR450W CP entered; disabled wait PSW 000E 0232 *
>>
>>
>> I have ftp'd the INITRD, KERNEL and PRM file over to z/VM and the files
>> seem to be good
>>
>>
>> SETUP parms from the EXEC is as below
>>
>>
>> *Setup:
>>*
>>
>>
>>
>>
>> *'PIPE CP DETACH 201 C12 | HOLE'
>> *
>>
>> *'PIPE CP LINK * C12 201 | HOLE'
>> *
>>
>>
>>
>>
>> */*×
>> ׯ
>> *
>>
>> *| Format the disk which will form the one-pack LVM  |
>> *
>>
>> *¿××
>> */
>> *
>>
>> *'MAKEBUF'
>> *
>>
>> *Push 'RH-7.1'
>> *
>>
>> *Push '1'
>>*
>>
>> *'FORMAT 201 Z ( BLKSIZE 4K'
>> *
>>
>> *'DROPBUF'
>> *
>>
>>
>>
>>
>> */*×
>> ׯ
>> *
>>
>> *| Swap space is now included in the 201 LVM.  The 200 must be NOT   |
>> *
>>
>> *| exist at installation or /boot will be written to the disk.  See the  |
>> *
>>
>> *| SharePoint document on installing RH7 for zSeries!|
>> *
>>
>> *¿××
>> */
>> *
>>
>> *'PIPE CP DETACH 200 | HOLE'
>> *
>>
>>
>>
>>
>> *|...+1+2+3+4+5+
>> 6+7+8+.*
>>
>> *'PIPE CP CLOSE RDR | HOLE'
>>*
>>
>> *'PIPE CP PURGE RDR ALL  HOLE'
>> *
>>
>> *'PIPE CP SPOOL PUNCH * RDR | HOLE'
>>*
>>
>> *'PIPE CP CHANGE RDR ALL KEEP NOHOLD | HOLE'
>> *
>>
>> *'CP TERM HOLD OFF'
>>*
>>
>> *'CP TERM MORE 10 5'
>> *
>>
>>
>>
>>
>> *'ACCESS CA:LINUX024.RHEL71. I'
>>*
>>
>>
>>
>>
>> *'PUNCH KERNEL   IMGI (NOH'
>>*
>>
>> *'PUNCH RH7  PRMI (NOH'
>>*
>>
>> *'PUNCH INITRD   IMGI (NOH'   *
>>
>>
>> Please let me know if any assistance on this.
>>
>>
>>
>>
>>
>>
>> Regards,
>>
>> Kumar
>> This e-mail and the documents attached are confidential and intended
>> solely for the addressee; it may also be privileged. If you receive this

Re: IBM / SUSE Issues udev name change

[Waite, Dick (External)]

Grand Foggy Day in Darmstadt,

I wanted to know who's bright idea it was to change between SP-1 and SP-2 the 
format of the udev... This amend and "zypper migration" gives you a good SP-2 
but where is the /boot/zipl ? it's got a SP-1 udev interface so can not be 
found and it's a real PITA to get your system back. IBM I thinks it's pints all 
round. From a company who's z/OS JCL from the 1970's still run you blow a hole 
in a SP update  Makes one think, "how was this tested by IBM ?" not using 
standard end user tools like zypper migration that for sure.

Now I'm all in favour of making better interfaces, but the old interface should 
still work, at least between SP's Maybe between SLES 12 and SLES 13 with a loud 
drum roll so that local folk know it's happening, but an interface change like 
this at SP time, Big Blue you should be ashamed...


http://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lhdd/lhdd_c_scsi_nodes.html

An IBM paper that says:

SCSI device names are assigned in the order in which the devices are detected. 
In a typical SAN environment, this can mean a seemingly arbitrary mapping of 
names to actual devices that can change between boots. Therefore, using 
standard device nodes of the form /dev/ where  is the 
device name that the SCSI stack assigns to a device, can be a challenge.

SUSE Linux Enterprise Server 12 SP2 provides udev to create device nodes for 
you. Use the device nodes to identify the corresponding actual device.

Device nodes that are based on bus IDsEnd of changeStart of changeudev creates 
device nodes of the form

/dev/disk/by-path/ccw--fc--lun-

for whole SCSI device and

/dev/disk/by-path/ccw--fc--lun--part

for the th partition, where  is the worldwide port number of the 
target port and  is the logical unit number that represents the target 
SCSI device.
Note: The format of these udev-created device nodes has changed and now matches 
the common code format. Device nodes of the prior form, 
ccw--zfcp-: or 
ccw--zfcp-:-part, are no longer created.

__R

From: Waite, Dick (External)
Sent: 29 December 2016 21:44
To: Linux on 390 Port
Subject: RE: SUSE Issues udev name change

For interest to good people migrating from SLES12 SP-1 to SP-2 I have looked at 
the Release Notes of SP-2 for key word "udev" and did not find any words. If 
you do not do one of the options below your migration runs grand until the new 
IPL and your boot disk is not there any more.

Grand work by a West Coast SUSE support chap.


OkI see what the problem is now.   In SP1 udev named the devices in 
/dev/disk/by-path like this:
fc15-zfcp-0x500507630413d46b:0x40eb4002-part1

In SP2 it's named like this:
ccw-0.0.fc15-fc-0x500507630413d46b-lun-0x40eb4002-part1

There are 2 ways to fix this on your existing SP1 servers:
1. Since you are using scsi devices and not DASD you could use the 
/dev/disk/by-id device in the /etc/fstab instead of the /dev/disk/by-id
So you would replace the 
/dev/disk/by-path/fc15-zfcp-0x500507630413d46b:0x40eb4002-part1with 
/dev/disk/by-id/scsi-36005076304ffd46beb02-part1

or

2. Before the update edit the /etc/fstab and change the name of the by-path 
device by replacing the ":" in the name with "-lun-"

__R

From: Waite, Dick (External)
Sent: 23 December 2016 12:18
To: Linux on 390 Port
Subject: RE: Goldimage Redhat 7.1

Good Morning,

I have SR 101040685023 with SUSE, open against issues with /dev not there 
after, in my case, an update/migration from SP-1... but I understand from 
support it can occur under other circumstance. Seem you have found one of the 
circumstances...

It's not just /dev/root this is missing, it's /dev

I was told by support yesterday morning then have repro'ed the issue and are 
working on it...

We have seen this with RHEL but not so often as with SUSE  With SUSE and a 
LVM environment with /usr as part of "/" it can happen each time you migrate a 
SP-1 to SP-2. In our case a new install does work Okay, only update/migration 
has this missing /dev

Have a grand day.

__R


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Kumar 
[kumarsyste...@gmail.com]
Sent: 23 December 2016 11:54
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Goldimage Redhat 7.1

I retried the installation and i didnt miss all messages this time

*[ [32m  OK   [0m] Started Show Plymouth Boot Screen.
  *
*[ [32m  OK   [0m] Reached target Paths.
   *
*[ [32m  OK   [0m] Reached target Basic System.
 *
* Starting Dracut Emergency Shell...
 *
*dracut-initqueue[680]: Warning: Could not boot.
 *
*dracut-initqueue[680]: Warning: /dev/root does not exist
*
*Warning: /dev/root does not exist
 *


*Generating