zipl-installer fails on z/KVM installation

Bug #1537942 reported by Tim Kuhlman on 2016-01-25
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
partman-partitioning (Ubuntu)
High
Unassigned

Bug Description

When attempting an install of a z/KVM vm using the latest kernel/initrd from http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-s390x/current/images/generic/ the zipl installer fails. If I drop to a shell and look at syslog the error I get is

Jan 25 11:47:27 zipl-installer: Error: Failed to read DASD label, please specify type manually: Virtblk device type not clearly determined.

The install was nearly as basic as you can get other than setting the apt archive to ports.ubuntu.com everything was done via the defaults.

The syslog reveals it is using this version of zipl-installer:

Jan 25 11:35:02 anna[1355]: DEBUG: retrieving zipl-installer 0.0.30ubuntu1
Jan 25 11:35:02 anna[1355]: 2016-01-25 11:35:02 URL:http://ports.ubuntu.com/ubuntu-ports//pool/main/z/zipl-installer/zipl-installer_0.0.30ubuntu1_s390x.udeb [4676/4676] -> "/var/cache/anna/zipl-installer_0.0.30ubuntu1_s390x.udeb" [1]

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: debian-installer (not installed)
ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
Uname: Linux 4.3.0-7-generic s390x
NonfreeKernelModules: ntfs
ApportVersion: 2.19.3-0ubuntu3
Architecture: s390x
Date: Mon Jan 25 13:16:45 2016
DiskUsage:
 Filesystem 1K-blocks Used Available Use% Mounted on
 /dev/vda1 6003912 872372 4803508 16% /
 devtmpfs 505660 0 505660 0% /dev
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MemoryUsage:
 total used free shared buff/cache available
 Mem: 1017668 60236 151356 72128 806076 859964
 Swap: 963644 424 963220
ProcEnviron:
 LANGUAGE=
 TERM=vt102
 PATH=(custom, no user)
 LANG=C
 SHELL=/bin/sh
ProcKernelCmdLine: ro locale=C
SourcePackage: debian-installer
UdevDb:

UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)

Tim Kuhlman (timkuhlman) wrote :
Tim Kuhlman (timkuhlman) wrote :

I was able to work around this by doing a simple partitioning setup, just /boot and / with no swap. Previously I was using the guided partitioning and letting it setup defaults.

Changed in debian-installer (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Dimitri John Ledkov (xnox)
affects: debian-installer (Ubuntu) → partman-partitioning (Ubuntu)
Changed in partman-partitioning (Ubuntu):
assignee: Dimitri John Ledkov (xnox) → nobody
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package partman-partitioning - 110ubuntu3

---------------
partman-partitioning (110ubuntu3) xenial; urgency=medium

  * Set s390x partitioning tables (parted label type) to dasd. LP:
    #1534629, LP: #1527328, LP: #1537942.

 -- Dimitri John Ledkov <email address hidden> Tue, 09 Feb 2016 19:32:43 +0000

Changed in partman-partitioning (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers