Ever struggled to create configuration files for starting Linux on IBM Z and LinuxONE installations? Fear no more, we got you covered now: A new assistant available online will help you create parameter files!
Writing parameter files can be a challenge, with bugs triggering cycles with lengthy turnaround times. Our new installation assistant generates installer parameter files by walking you through a step-by-step process, where you answer simple questions to generate a parameter file. Comes with contextual help in every stage, so you can follow along what is happening!
Currently supports OSA and PCI networking devices, IPv4/v6, and VLAN installations.
Currently supports RHEL 9 and SLES 15 SP5 or later.
Access the assistant at https://ibm.github.io/liz/
How to define "rd.zfcp=" parameter. Above installation have only n/w parameter
ReplyDeleteHi - the rd.zfcp is not strictly required for an installation and can be entered during the Linux distribution's installer dialog. Alternatively you can add it manually to the resulting Parmfile after you are done with the installation assistant.
ReplyDeleteI have configured prm file as mentioned above, but rhel9 deployment not progressing. below are the last logs from lapr console. "[ 10.280004] sd 0:0:0:0: [sda] Write Protect is off
ReplyDelete[ 10.280229] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 10.280431] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 10.300412] sd 0:0:0:0: [sda] Attached SCSI disk
[ 10.305719] scsi 1:0:0:0: Direct-Access HP OPEN-V 8001 PQ: 0 ANSI: 3
[ 10.306288] scsi 3:0:0:0: Direct-Access HP OPEN-V 8001 PQ: 0 ANSI: 3
[ 10.306941] sd 1:0:0:0: Attached scsi generic sg2 type 0
[ 10.307085] sd 1:0:0:0: [sdc] 104857600 512-byte logical blocks: (53.7 GB/50.0 GiB)
[ 10.307191] sd 1:0:0:0: [sdc] Write Protect is off
[ 10.307409] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 10.308204] sd 3:0:0:0: Attached scsi generic sg3 type 0
[ 10.308363] sd 3:0:0:0: [sdd] 209715200 512-byte logical blocks: (107 GB/100 GiB)
[ 10.308490] sd 3:0:0:0: [sdd] Write Protect is off
[ 10.308756] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 10.310778] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 10.355120] sd 3:0:0:0: [sdd] Attached SCSI disk
[ 10.355381] sd 1:0:0:0: [sdc] Attached SCSI disk
[ 10.762183] device-mapper: multipath service-time: version 0.3.0 loaded
"
From the quoted console messages there is no clear indication why the installer is stuck. This is typically the case when either some installer data was not entered correctly (e.g. network device names, settings, IP address, server addresses) or if one of the required resources (e.g. installation server, network interface) is not working properly.
DeleteOne approach to debug scenarios like this is to add "rd.timeout=60 rd.shell" to the kernel parameters. This will result in the installer dropping into an emergency shell when any required resource is not available within 60 seconds. Inside that shell, each resource can then be manually checked (e.g. using 'ip addr' to see network configuration, or using ping to check connectivity to the server).