ubuntu-installer/partman does not properly detect partitions on FBA device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
High
|
Dimitri John Ledkov | ||
partman-partitioning (Ubuntu) |
Fix Released
|
High
|
Dimitri John Ledkov | ||
Xenial |
Fix Released
|
Medium
|
Dimitri John Ledkov | ||
Yakkety |
Fix Released
|
Medium
|
Dimitri John Ledkov |
Bug Description
[Impact]
* multipartition installations on DASD-FBA use wrong partition table, resulting in userspace tools not recognising the partitions that kernel uses on those drives
[Testcase]
* install ubuntu using manual partitioning onto DASD-FBA drive with two partitions e.g. 500M for /boot and / for the rest.
* re-start the installer again
* observe that in manual partitioning both partitions are correctly detected and for example reuse of partition #2 is offered.
I installed Ubuntu 16.04.1 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.
Changed in ubuntu-z-systems: | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in parted (Ubuntu): | |
importance: | Undecided → High |
assignee: | Skipper Bug Screeners (skipper-screen-team) → Dimitri John Ledkov (xnox) |
milestone: | none → ubuntu-17.01 |
Changed in ubuntu-z-systems: | |
importance: | Medium → High |
Changed in parted (Ubuntu): | |
status: | New → Confirmed |
milestone: | ubuntu-17.01 → ubuntu-17.02 |
Changed in ubuntu-z-systems: | |
status: | New → Confirmed |
affects: | parted (Ubuntu) → partman-partitioning (Ubuntu) |
Changed in partman-partitioning (Ubuntu Xenial): | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in partman-partitioning (Ubuntu Yakkety): | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in partman-partitioning (Ubuntu Xenial): | |
milestone: | none → xenial-updates |
Changed in partman-partitioning (Ubuntu Yakkety): | |
milestone: | none → yakkety-updates |
Changed in partman-partitioning (Ubuntu Xenial): | |
status: | New → Confirmed |
Changed in partman-partitioning (Ubuntu Yakkety): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in partman-partitioning (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in ubuntu-z-systems: | |
status: | Confirmed → Triaged |
Changed in partman-partitioning (Ubuntu Xenial): | |
status: | Triaged → In Progress |
status: | In Progress → Triaged |
Changed in partman-partitioning (Ubuntu Yakkety): | |
status: | Triaged → In Progress |
Changed in partman-partitioning (Ubuntu Xenial): | |
status: | Triaged → In Progress |
Changed in ubuntu-z-systems: | |
status: | Triaged → In Progress |
Changed in ubuntu-z-systems: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-z-systems: | |
status: | Fix Committed → Fix Released |
------- Comment From <email address hidden> 2016-12-15 10:07 EDT-------
Canonical, please assign to correct component within LP. Thx