[Bug 1578232] Re: ubuntu-installer/partman does not properly detect partitions on FBA device

[Dimitri John Ledkov]

You should really upgrade to rsa ssh keys =) given that OpenSSH 7.0
disables ssh-dss keys by default

May  4 14:02:19 sshd[7517]: userauth_pubkey: key type ssh-dss not in
PubkeyAcceptedKeyTypes

** Description changed:

- We detected following information
+ I installed Ubuntu 16.04 on an FBA device. When the partman menu appeared, I created a new partition table on DASD 0.0.ede0 (FBA), and then I created two partitions: 0.7G ext4 for /boot and 10G ext4 for /.
+ Installation proceeded ok, and the system ipled from EDEV EDE0. All fine.
  
- Manuell Installation in Standard-Mode (not Expert Mode)with following
- selection: standard system utilities, OpenSSH server, Basic Ubuntu
- server for s390-tools:
+ During a 2nd installation on the same device the following problem occured:
+ After activation of the previously installed EDEV disk, partman shows one single full size partition, which is not correct:
+ ? DASD 0.0.ede0 (FBA ) - 10.7 GB IBM S390 DASD drive ?
+ ? > #1 10.7 GB ?
+ while kernel has the correct info:
+ ~ # cat /proc/partitions |grep dasd
+ 94 0 10485760 dasda
+ 94 1 683584 dasda1
+ 94 2 9801984 dasda2
+ Continuing with the installation from here results in a system IPL that ends up in an initramfs, since the rootfs could not be mounted due to an incorrect partition table.
  
- Following information are provided by the ubuntu-support-status tool.
+ Attaching syslog.
  
- Supported until January 2017 (9m):
- libpfm4 s390-tools sysconfig-hardware 
+ Until this bug is fixed, I recommend to describe the workaround (when
+ installing on EDEV DASD it is highly recommended to create an empty
+ partition table on the entire device before partitioning) in the release
+ notes.
  
- Supported until April 2019 (3y):
- discover discover-data libdiscover2 
- 
- The assumption is, the 16.04 LTS will have 5 year support for each
- package within release/main
+ Maybe you can have a look info LTC bug 137464 / LP1548411 which
+ described a similar problem with vdisks under KVM.

** Package changed: update-manager (Ubuntu) => parted (Ubuntu)

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

Title:
  ubuntu-installer/partman does not properly detect partitions on FBA
  device

Status in Ubuntu on IBM z Systems:
  Triaged
Status in parted package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 16.04 on an FBA device. When the partman menu appeared, I created a new partition table on DASD 0.0.ede0 (FBA), and then I created two partitions: 0.7G ext4 for /boot and 10G ext4 for /.
  Installation proceeded ok, and the system ipled from EDEV EDE0. All fine.

  During a 2nd installation on the same device the following problem occured:
  After activation of the previously installed EDEV disk, partman shows one single full size partition, which is not correct:
  ? DASD 0.0.ede0 (FBA ) - 10.7 GB IBM S390 DASD drive ?
  ? > #1 10.7 GB ?
  while kernel has the correct info:
  ~ # cat /proc/partitions |grep dasd
  94 0 10485760 dasda
  94 1 683584 dasda1
  94 2 9801984 dasda2
  Continuing with the installation from here results in a system IPL that ends up in an initramfs, since the rootfs could not be mounted due to an incorrect partition table.

  Attaching syslog.

  Until this bug is fixed, I recommend to describe the workaround (when
  installing on EDEV DASD it is highly recommended to create an empty
  partition table on the entire device before partitioning) in the
  release notes.

  Maybe you can have a look info LTC bug 137464 / LP1548411 which
  described a similar problem with vdisks under KVM.

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