[Bug 1843226] Re: Installation on z14 LPAR via FTP load fails

Frank Heimes 1843226 at bugs.launchpad.net
Tue Sep 24 07:38:12 UTC 2019


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_mod dasd_eckd_mod dasd_mod qeth_l2 pkey crc32_vx_s390 qeth qdio ccwgroup zcrypt_cex4 zcrypt
Sep 24 07:13:22 kernel: [  116.773571] CPU: 3 PID: 4561 Comm: chzdev Not tainted 5.3.0-10-generic #11-Ubuntu
Sep 24 07:13:22 kernel: [  116.773572] Hardware name: IBM 2964 N63 400 (z/VM 6.4.0)
Sep 24 07:13:22 kernel: [  116.773573] Krnl PSW : 0704c00180000000 0000000065627372 (module_put.part.0+0xe2/0xe8)
Sep 24 07:13:22 kernel: [  116.773575]            R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
Sep 24 07:13:22 kernel: [  116.773577] Krnl GPRS: 0000000000000004 0000000000000006 0000000000000024 0000000000000007
Sep 24 07:13:22 kernel: [  116.773578]            0000000000000007 000000007f2ce800 fffffffffffffffb 000003ff8015d578
Sep 24 07:13:22 kernel: [  116.773579]            00000000fffffffb 000003ff8007edf8 000003ff8015d900 0000000077394400
Sep 24 07:13:22 kernel: [  116.773580]            0000000077115500 0000000000000bf8 000000006562736e 000003e003e0bb08
Sep 24 07:13:22 kernel: [  116.773586] Krnl Code: 0000000065627362: c0200048859a	larl	%r2,65f37e96
Sep 24 07:13:22 kernel: [  116.773586]            0000000065627368: c0e5fffe16a4	brasl	%r14,655ea0b0
Sep 24 07:13:22 kernel: [  116.773586]           #000000006562736e: a7f40001		brc	15,65627370
Sep 24 07:13:22 kernel: [  116.773586]           >0000000065627372: a7f4ffb1		brc	15,656272d4
Sep 24 07:13:22 kernel: [  116.773586]            0000000065627376: 0707		bcr	0,%r7
Sep 24 07:13:22 kernel: [  116.773586]            0000000065627378: c00400000000	brcl	0,65627378
Sep 24 07:13:22 kernel: [  116.773586]            000000006562737e: ec280006007c	cgij	%r2,0,8,6562738a
Sep 24 07:13:22 kernel: [  116.773586]            0000000065627384: c0f4ffffff86	brcl	15,65627290
Sep 24 07:13:22 kernel: [  116.773597] Call Trace:
Sep 24 07:13:22 kernel: [  116.773599] ([<000000006562736e>] module_put.part.0+0xde/0xe8)
Sep 24 07:13:22 kernel: [  116.773610]  [<000003ff8007edf8>] dasd_generic_free_discipline+0x68/0x80 [dasd_mod] 
Sep 24 07:13:22 kernel: [  116.773614]  [<000003ff800895ba>] dasd_delete_device+0x122/0x1c8 [dasd_mod] 
Sep 24 07:13:22 kernel: [  116.773617]  [<000003ff80085cfa>] dasd_generic_set_online+0x2ea/0x310 [dasd_mod] 
Sep 24 07:13:22 kernel: [  116.773621]  [<0000000065bb1b48>] ccw_device_set_online+0x110/0x528 
Sep 24 07:13:22 kernel: [  116.773623]  [<0000000065bb1fb0>] online_store_recog_and_online+0x50/0x130 
Sep 24 07:13:22 kernel: [  116.773624]  [<0000000065bb3042>] online_store+0x1b2/0x2e0 
Sep 24 07:13:22 kernel: [  116.773627]  [<000000006586f7a0>] kernfs_fop_write+0xd8/0x1f8 
Sep 24 07:13:22 kernel: [  116.773630]  [<00000000657bc5f8>] vfs_write+0xb0/0x1b8 
Sep 24 07:13:22 kernel: [  116.773631]  [<00000000657bdeb8>] ksys_write+0x68/0xf8 
Sep 24 07:13:22 kernel: [  116.773635]  [<0000000065db04b8>] system_call+0xdc/0x2c8 
Sep 24 07:13:22 kernel: [  116.773635] Last Breaking-Event-Address:
Sep 24 07:13:22 kernel: [  116.773637]  [<000000006562736e>] module_put.part.0+0xde/0xe8
Sep 24 07:13:22 kernel: [  116.773637] ---[ end trace 9c8a4f2c516f68c0 ]---

(same as in previous comment)

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1843226/+attachment/5290861/+files/syslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to zipl-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1843226

Title:
  Installation on z14 LPAR via FTP load fails

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in debian-installer package in Ubuntu:
  Fix Committed
Status in zipl-installer package in Ubuntu:
  Fix Released

Bug description:
  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 at 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1843226/+subscriptions



More information about the foundations-bugs mailing list