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

[Dimitri John Ledkov]

Bridge has miss-mirrored this bug report. Can you please open a new
(clean) bug report for this issue and mirror it accross? Is it still
reproducible, and isn't this a linux kernel bug rather than installer?

** Changed in: ubuntu-z-systems
       Status: Triaged => Invalid

** Changed in: parted (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to parted 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:
  Invalid
Status in parted package in Ubuntu:
  Invalid

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