[Bug 2146873] Re: Custom partitioning on DASD ECKD (s390x) can lead to a failed installation

Frank Heimes 2146873 at bugs.launchpad.net
Tue Apr 21 06:59:01 UTC 2026


** Summary changed:

- Try default 26.04/s390x installation on z/VM using DASD
+ Custom partitioning on DASD ECKD (s390x) can lead to a failed installation

** Description changed:

+ Using custom partitioning for DASD ECKD disk devices on s390x can lead
+ to a failed installation and crash, due to the way the disk/partitioning
+ is handled today.
+ 
+ This happens in case the root partition is not the only partition that
+ is specified and not the last one (of the up to three possible
+ partitions on a DASD ECKD disk), an installation may fail in case an
+ ext4 filesystem is used for root.
+ 
+ A workaround is to ensure that the root partition is specified as the **last** (or only) partition, like for example:
+ 1st partition: /boot
+ 2nd partition: swap
+ 3rd partition: / (root)
+ _____
+ 
  Please try a 26.04 beta (or daily) test installation (using largely the
  defaults) on z/VM with DASD disks.
  
  (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20260329/ or better
  latest daily:)
  
  https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/

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

Title:
  Custom partitioning on DASD ECKD (s390x) can lead to a failed
  installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in curtin package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  New

Bug description:
  Using custom partitioning for DASD ECKD disk devices on s390x can lead
  to a failed installation and crash, due to the way the
  disk/partitioning is handled today.

  This happens in case the root partition is not the only partition that
  is specified and not the last one (of the up to three possible
  partitions on a DASD ECKD disk), an installation may fail in case an
  ext4 filesystem is used for root.

  A workaround is to ensure that the root partition is specified as the **last** (or only) partition, like for example:
  1st partition: /boot
  2nd partition: swap
  3rd partition: / (root)
  _____

  Please try a 26.04 beta (or daily) test installation (using largely
  the defaults) on z/VM with DASD disks.

  (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20260329/ or
  better latest daily:)

  https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/

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





More information about the foundations-bugs mailing list