Raring amd64 Ubiquity to existing partition "Can't have a partition outside the disk!"

[jerrylamos]

Raring amd64 daily builds 20130116 (and 20130115) select an existing partition to install to - was previously raring running O.K.
Same size. No change.
ext4 or ext3 (either, same bug)
format (it actually does the format)
/
churns for a while and then says "Can't have a partition outside the disk!" which makes no sense, that partition previously had a running Raring in it.

Any way to get around this bug? Ubiquity doesn't seem to be able to proceed. I have installed Raring amd64 on this 80 GB Intel SSD every couple weeks or so.

Thanks for any hints.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubiquity 2.13.9
ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
ApportVersion: 2.8-0ubuntu1
Architecture: amd64
CasperVersion: 1.330
Date: Wed Jan 16 20:53:27 2013
InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/raring-desktop-amd64.iso noprompt noeject
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[jerrylamos (jerrylamos)]

Next message after the "can't have a partition outside the disk" message:

Assertion (metadata_length > 0) at ../../../libparted/labels/dos.c:2178 in function add_logical_part_metadata() failed.

Next message:

"ERROR!"

Sits there spinning, the / in the Format box never appears.

Previous Raring amd64 installs O.K. Linux mint 14 (quantal base) installed fine.

[jerrylamos (jerrylamos)]

Still failing at daily build 23 January raring deskgop amd64.iso

Partition being installed into exists, was previously a running raring.

Ubiquity insists it can't install into a partition that is outside the disk.

The partition is NOT outside the disk. It does exist. When ubiquity is marked to format the paritition it does. No problem.

There is a note about an existing bug 1103213 which must be marked as private because Launchpad won't let me access it. Do note 1103213 must have been written after this bug, 1100466.

Any ideas how to get around this Ubiquity partitioner bug?

[jerrylamos (jerrylamos)]

26 January Daily Build still fails complaining can't install to a partition outside the disk.

I'm not changing partition in any way, already formatted. Somehow Ubiquity Partitioner claims the partition is outside the disk when raring is quite happy to format the partition no errors.

During install, apport tries to report the bug which it says already exists as

Bug #1103213

which Launchpad won't let me access.

Must be a "secret" bug.

What's the use of Launchpad bugs we can't even view?

Any ideas how to install Ubuntu amd64?

[jerrylamos (jerrylamos)]

Note this bug occurs if install is to the last partition on the disk.

Deleted pangolin LTS that was in the first partition, re-installed in aother partition.

Raring installed in first partition with no complaint about the partition being outside the disk.

Sure looks like partitioner tries to access the disk above the last partition.

Won't work. Don't even try.

Partitioner should be updated to access the partition selected not somewhere else.

[jerrylamos (jerrylamos)]

My wide screen notebook has six partitions.

Raring amd64 will not install in partition 6, last one on the 80 GB disk.

The partitioner complains it cannot install to a partition "outside the disk". The partition exists. I'm not asking to change partition size or anything else.

Raring amd64 will install on the 1st partition of the disk.

Pangolin will install on both the 1st and the last, the 6th, no problem.

Boils down to a problem with the Raring partitioner, which is a "regression" since the Pangolin partitioner has no such problem.

What was on the 6th partition was an early version of Raring. I no longer have that .iso to try.

Note part way thru Raring there was a change in the partitioner. Acid test would be to try Raring install to the last partition on the disk with Raring just before and just after the partitioner change.

[Simon Quigley (tsimonq2)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1100466

and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]