Installation on z14 LPAR via FTP load fails

[bugproxy]

Installation on z14 LPAR via FTP load fails. The installer breaks with error message

"An installation step failed. You can try to run the failing item again from the menu, or skip it and choose something else. The failing step is: Install the ZIPL boot loader on a hard disk"

When opening a shell:
~ # chroot target/ bash
root@m35lp54:/# zipl
Using config file '/etc/zipl.conf'
Error: Config file '/etc/zipl.conf': No such file or directory

After creating a working zipl.conf the boot loader can be written to disk on the shell and the disk becomes bootable. The Installer however still fails with the same error message.

---uname output---
Linux m35lp54 5.2.0-15-generic #16-Ubuntu SMP Fri Aug 23 20:15:30 UTC 2019 s390x GNU/Linux

Vendor ID: IBM/S390
Machine type: 3906

---Point of failure---
Installation of zipl on hard disk.

[bugproxy (bugproxy)]

Default Comment by Bridge

[Frank Heimes (fheimes)]

I can recreate this on z13 (LPAR install using zFCP/SCSI) with latest Eoan daily image from today:
664262656 Sep 8 06:49 eoan-server-s390x.iso

attached my installer logs

zipl itself is there (in d-i shell), but zipl.conf isn't created in /target:

~ # find / -name "zipl"
/target/usr/sbin/zipl

~ # find / -name "zipl.conf"
~ #

but should be (at the end of the installation):

~ # find / -name "zipl"
/target/usr/sbin/zipl

~ # find / -name "zipl.conf"
/target/etc/zipl.conf

[Dimitri John Ledkov (xnox)]

we probably need to trace d-i's zipl-installer postinst as it's probably failing during lvm & btrfs probing. (which is between sysconfig-hardware installation and writing zipl.conf)

[Dimitri John Ledkov (xnox)]

This should work now with:
- debian-installer 20101020ubuntu585 or later
- mirror with zipl-installer 0.0.35ubuntu2 or newer

Note, that v5.3 is in -proposed and s390-tools v2.11.0 is not yet available as it is awaiting signing. Please be mindful of the bugs that are thus still present in eoan's snapshot of s390-tools v2.10+patches.

[Frank Heimes (fheimes)]

I successfully verified that this zipl install issue is solved.
Changing project entry to Fix Committed.

[Frank Heimes (fheimes)]

I ran into this issue again today, since 20101020ubuntu585 became outdated and I moved over to 20101020ubuntu586 / current.

On DASD selection I now get again:
     ┌──────┤ [!!] Configure direct access storage devices (DASD) ├──────┐
     │ │
     │ Installation step failed │
     │ An installation step failed. You can try to run the failing item │
     │ again from the menu, or skip it and choose something else. The │
     │ failing step is: Configure direct access storage devices (DASD) │
     │ │
     │ <Continue> │
     │ │
     └───────────────────────────────────────────────────────────────────┘

syslog one can see:

Sep 23 11:01:37 anna[1615]: 2019-09-23 11:01:37 URL:http://us.ports.ubuntu.com/ubuntu-ports//pool/main/z/zipl-installer/zipl-installer_0.0.35ubuntu2_s390x.udeb [4616/4616] -> "/var/cache/anna/_fetch-url_zipl-installer_0.0.35ubuntu2_s390x.udeb.3800" [1]
Sep 23 11:01:38 main-menu[422]: INFO: Menu item 'driver-injection-disk-detect' selected
Sep 23 11:01:39 main-menu[422]: (process:3899): File descriptor 3 (pipe:[132]) leaked on pvs invocation. Parent PID 3903: /bin/sh
Sep 23 11:01:39 main-menu[422]: (process:3899): File descriptor 4 (/dev/pts/0) leaked on pvs invocation. Parent PID 3903: /bin/sh
Sep 23 11:01:39 main-menu[422]: (process:3899): File descriptor 5 (/dev/pts/0) leaked on pvs invocation. Parent PID 3903: /bin/sh
Sep 23 11:01:39 main-menu[422]: (process:3899): File descriptor 6 (/dev/pts/0) leaked on pvs invocation. Parent PID 3903: /bin/sh
Sep 23 11:01:39 main-menu[422]: (process:3899): File descriptor 3 (pipe:[132]) leaked on pvs invocation.
Sep 23 11:01:39 main-menu[422]: (process:3899): Parent PID 3961: /bin/sh
Sep 23 11:01:39 main-menu[422]: (process:3899): File descriptor 4 (/dev/pts/0) leaked on pvs invocation.
Sep 23 11:01:39 main-menu[422]: (process:3899): Parent PID 3961: /bin/sh
Sep 23 11:01:39 main-menu[422]: (process:3899): File descriptor 5 (/dev/pts/0) leaked on pvs invocation.
Sep 23 11:01:39 main-menu[422]: (process:3899): Parent PID 3961: /bin/sh
Sep 23 11:01:39 main-menu[422]: (process:3899): File descriptor 6 (/dev/pts/0) leaked on pvs invocation.
Sep 23 11:01:39 main-menu[422]: (process:3899): Parent PID 3961: /bin/sh
Sep 23 11:01:39 main-menu[422]: INFO: Menu item 'user-setup-udeb' selected
Sep 23 11:01:56 main-menu[422]: INFO: Menu item 'clock-setup' selected
Sep 23 11:01:58 main-menu[422]: INFO: Menu item 's390-dasd' selected
Sep 23 11:01:58 net/hw-detect.hotplug: Detected hotpluggable network interface enc600
Sep 23 11:01:58 net/hw-detect.hotplug: Detected hotpluggable network interface lo
Sep 23 11:01:58 s390-dasd[4562]: DEBUG: PRESEED: No preseed data available
Sep 23 11:02:01 kernel: [ 153.590510] ctcm.151d85: CTCM driver initialized
Sep 23 11:02:01 kernel: [ 153.628223] lcs.4fa72b: Loading LCS driver
Sep 23 11:02:01 s390-dasd[4562]:...

[Frank Heimes (fheimes)]

Updated information from new QA Tracker ISO testing using:
http://cdimage.ubuntu.com/ubuntu-server/daily/20190924/eoan-server-s390x.iso

     ┌──────┤ [!!] Configure direct access storage devices (DASD) ├──────┐
     │ │
     │ Installation step failed │
     │ An installation step failed. You can try to run the failing item │
     │ again from the menu, or skip it and choose something else. The │
     │ failing step is: Configure direct access storage devices (DASD) │
     │ │
     │ <Continue> │
     │ │
     └───────────────────────────────────────────────────────────────────┘

d-i shell:

~ # lszdev dasd
TYPE ID ON PERS NAMES
dasd-eckd 0.0.0190 no no
dasd-eckd 0.0.0191 no no
dasd-eckd 0.0.019d no no
dasd-eckd 0.0.019e no no
dasd-eckd 0.0.0200 no no
dasd-eckd 0.0.0300 no no
dasd-eckd 0.0.0400 no no
dasd-eckd 0.0.0592 no no
dasd-eckd 0.0.1607 no no
~ # chzdev -e 0.0.0200
ECKD DASD 0.0.0200 configure failed
    Error: Could not write file /sys/bus/ccw/drivers/dasd-eckd/0.0.0200/online: Invalid argument
~ # chzdev -e 300
ECKD DASD 0.0.0300 configure failed
    Error: Could not write file /sys/bus/ccw/drivers/dasd-eckd/0.0.0300/online: Invalid argument
~ #

from log:

Sep 24 07:13:20 main-menu[420]: INFO: Menu item 's390-dasd' selected
Sep 24 07:13:20 net/hw-detect.hotplug: Detected hotpluggable network interface enc600
Sep 24 07:13:20 net/hw-detect.hotplug: Detected hotpluggable network interface lo
Sep 24 07:13:20 s390-dasd[4560]: DEBUG: PRESEED: No preseed data available
Sep 24 07:13:22 kernel: [ 116.707079] ctcm.151d85: CTCM driver initialized
Sep 24 07:13:22 kernel: [ 116.745052] lcs.4fa72b: Loading LCS driver
Sep 24 07:13:22 s390-dasd[4560]: ECKD DASD 0.0.0200 configure failed
Sep 24 07:13:22 s390-dasd[4560]: Error: Could not write file /sys/bus/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error
Sep 24 07:13:22 s390-dasd[4560]: Configuring devices in the active configuration only
Sep 24 07:13:22 main-menu[420]: WARNING **: Configuring 's390-dasd' failed with error code 1
Sep 24 07:13:22 main-menu[420]: WARNING **: Menu item 's390-dasd' failed.
Sep 24 07:13:22 kernel: [ 116.772425] dasd-eckd.401b68: 0.0.0200: A channel path to the device has become operational
Sep 24 07:13:22 kernel: [ 116.773539] dasd-eckd.6b7759: 0.0.0200: Reading the volume storage information failed with rc=-5
Sep 24 07:13:22 kernel: [ 116.773542] dasd.3e7d29: 0.0.0200 Setting the DASD online with discipline ECKD failed with rc=-5
Sep 24 07:13:22 kernel: [ 116.773543] ------------[ cut here ]------------
Sep 24 07:13:22 kernel: [ 116.773562] WARNING: CPU: 3 PID: 4561 at kernel/module.c:1137 module_put.part.0+0xe2/0xe8
Sep 24 07:13:22 kernel: [ 116.773562] Modules linked in: lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_m...

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1843226

[Frank Heimes (fheimes)]

With the ISO image from Sep 28th the correct zipl-installer is in use by default:
Sep 30 09:08:39 anna[1627]: DEBUG: retrieving zipl-installer 0.0.35ubuntu2
so this particular issue is solved.
Hence I mark this as fixed released.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-10-07 05:55 EDT-------
IBM Bugzilla status -> closed, Fix Released with Eoan