'partitioning disks' will not mount and use a during Installation from CD

[Lars Noodén]

When installing 10.04 RC2 from CD (alternate amd64) the "Partition Disks" step of the installation produces an error when trying to re-use an existing linux swap partition. This error occurs even when the same CD was used to create the swap and the system is only being reinstalled.

Steps:

1) Partition and install ubuntu
In this case /home and / are on different partitions, there is also a swap partition.

2) Re-install, leaving partitions intact but marking them for formatting

3) this error pops up:

  [!!] Partition disks
  The attempts to mount a file system with type swap in SCIS3 (0,1,),
   partition #5 (sda) at none failed.

   You may want to resume partitioning from the partitioning menu.

   Do you want to resume partitioning?

  <Go Back> <Yes> <No>

4) Choosing Go Back, sometimes regardless of what is done, and trying again allows the swap partition to be formatted. Deleting the partition entirely and recreating it always fixes the error.

[Monkey (monkey-libre)]

I´ve assigned this bug to the ubuquity package. Please give more information, I´ve added a link for that. Thank You for making Ubuntu better.

https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs

[Lars Noodén (larsnooden)]

Here is the media info:

Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100114)$

Attached is the hardware summary.

The ability to transfer the logs via HTTP is a godsend. Thank you to who ever added that capability!

[Lars Noodén (larsnooden)]

FWIW, karmic does not have a problem with this. I can't really recall problems from Jaunty or Hardy either or, FWIW, Debian Etch or Lenny.

[Charlie Kravetz (cjkgeek)]

Thanks for the attachments. This may have been fixed already, now. Could you please try with the latest images available at http://cdimages.ubuntu.com/daily/current/ and please let us know the date of the image you try. Let us know here if this is or is not fixed for you.

[Charlie Kravetz (cjkgeek)]

I don't actually know what fixed this, but to keep it available for the developers future reference, I am marking it fix-released. It is no longer an issue using the final release of Ubuntu 10.04.