Installing 18.04 LTS on existing Partition

[Jens Holeczek]

Downloaded ISO 18.04 LTS from 22 February 2018 to try the new 18.04 LTS.

Have got a system with a SCSI Raid (sdc) and two SAS drives.

Actualy there are two installations on sdc1 and sdc3 with 16.04 LTS. Grub working fine to change from System sdc1 to sdc3

I booted from CD (Iso burned to disc) and following the steps to install 18.04 LTS.

First steps working fine. But at the Filesystem setup the installation stucks.

First Question Choose guided or manual partitioning I only got the two Options:
* Use an entire Disk
* Manual

No Option Other there

When Choosing Manual I got the File System Summary: No Disks or partitions mounted.
I can see al three Disks (sda, sdb and sdc) but only got the choice to "Add first Partition".

When Choosing "Use an entire Disk" a Python Script starts and stops with last two lines:
"File /snap/subiquity/233/lib/python3.6/site-packages/subiquitycore/ui/form.cy, line 303 in remove_field for bf in self._fields:
AttributeError: 'PartitionFOrm' object has no attribute '_fields' "
and the Progress jumps back to First Step ob Installation (Choosing Language)

Maybe the Lines before are able to help: Script seems to be a part of Package subiquity
I have no idea how to install on sdc3 to test 18.04 LTS.

Input of "fdisk -l /dev/sdc" on running system 16.04 shows:

Disk /dev/sdc: 136 GiB, 145999527936 bytes, 285155328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000b67ed

Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 136720797 136718750 65,2G 83 Linux
/dev/sdc2 276770814 285153279 8382466 4G 5 Extended
/dev/sdc3 * 136722432 276768767 140046336 66,8G 83 Linux
/dev/sdc5 276770816 285153279 8382464 4G 82 Linux swap / Solaris

Partition table entries are not in disk order.

Seems to be a Bug

[Ubuntu Foundations Team Bug Bot (crichton)]

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/1751656/+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.]

[Jens Holeczek (jenshol)]

Added Package could be the buggy one

[Michael Hudson-Doyle (mwhudson)]

Ah yes, I think this is fixed in git but not in the latest ISOs. Thanks for the report!

[Jens Holeczek (jenshol)]

It had been my first report, will the status be changed when solved in daily build iso?

[Steve Langasek (vorlon)]

Unlikely to be fixed before 18.04 GA, but this is important to address.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Matthias Hryniszak (padcom)]

This is absolutely unacceptable! This ticket has been there for ages, it forces users to re-format their drives even if there are pre-existing partitions thus inflicts complete data loss! It is absolutely outrageous that it has not been yet addressed. Great work, Canonical! Time to move to Arch?