Installation on ppc64le stuck when trying to setup LVM

Bug #1702792 reported by Guilherme Tiaki Sato
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Ubuntu-power-systems project
Invalid
Medium
Unassigned
debian-installer (Ubuntu)
Triaged
Medium
Canonical Foundations Team

Bug Description

I’am using Ubuntu 16.04 Netboot installer.

During the disk partitioning:

I have two disks, create an empty partition table on both and set both to be used entirely as physical volume for LVM.

Select "Configure the Logical Volume Manager".
Create a volume group using the two disks.
Create two logical volumes: one 8MB and the other using the rest of the space.
Finish configuring LVM.

Set the first logical volume "Use as" to "Use the partition as a PowerPC PReP boot partition".

This is followed by an error screen (attached).

After this I get stuck in the partitioning and can no longer continue the installation or change the partitioning.

Revision history for this message
Guilherme Tiaki Sato (guilhermetiaki) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1702792/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → debian-installer (Ubuntu)
Revision history for this message
Breno Leitão (breno-leitao) wrote :

Hello Guilherme, could you please attach the installation logs? You can do it by exiting to shell, at d-i, and grabbing the logs at /var/log.

Changed in debian-installer (Ubuntu):
assignee: nobody → Taco Screen team (taco-screen-team)
Revision history for this message
Guilherme Tiaki Sato (guilhermetiaki) wrote :
Revision history for this message
Guilherme Tiaki Sato (guilhermetiaki) wrote :
Revision history for this message
Guilherme Tiaki Sato (guilhermetiaki) wrote :
Manoj Iyer (manjo)
Changed in debian-installer (Ubuntu):
assignee: Taco Screen team (taco-screen-team) → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Changed in ubuntu-power-systems:
assignee: nobody → Canonical Foundations Team (canonical-foundations)
Revision history for this message
Steve Langasek (vorlon) wrote :

This is certainly a bug, but it is user error to configure an LVM volume as the prep partition; the prep partition must be a disk partition visible from firmware.

I believe this bug does not occur when using guided partitioning.

Changed in debian-installer (Ubuntu):
assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) → Canonical Foundations Team (canonical-foundations)
importance: Undecided → Medium
Changed in ubuntu-power-systems:
assignee: Canonical Foundations Team (canonical-foundations) → nobody
Revision history for this message
Guilherme Tiaki Sato (guilhermetiaki) wrote :

Yes, you're right. It works fine when using guided partitioning.

Manoj Iyer (manjo)
tags: added: triage-g
Changed in debian-installer (Ubuntu):
status: New → Invalid
Changed in ubuntu-power-systems:
status: New → Invalid
importance: Undecided → Medium
Revision history for this message
Guilherme Tiaki Sato (guilhermetiaki) wrote :

Steve Langasek said "This is certainly a bug". Why was the status changed to invalid?

Steve Langasek (vorlon)
Changed in debian-installer (Ubuntu):
status: Invalid → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.