Installer doesn't support mounting existing encryption volumes

Bug #155987 reported by Tony Yarusso on 2007-10-22
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
partman-crypto
New
Unknown
partman-crypto (Ubuntu)
High
Unassigned

Bug Description

Binary package hint: debian-installer

With my current setup, I like to have two separate installations of Ubuntu (the stable release and current development version), which I share everything but the root system for. In other words, I have two separate / installations, but my partitions for /home, /boot, /var, /tmp, and swap are all shared (mounted in both).

During the installation process, I chose to make encrypted volumes for /home and swap, with the new installer encryption options in Gutsy (alternate CD). When I went to install the second time (for what will become my Hardy system), it forced me to re-create the filesystem on those, overwriting the data from the first installation.

While this is not a problem at this time, since I was installing identical Gutsy systems on a clean hard drive, it will prevent things such as testing Hardy alpha release installers, as doing so would wipe the data from my /home partition.

Instead, debian-installer should have the ability to mount existing encrypted volume partitions in the same way that it does for unencrypted ones. The "Configure encrypted volumes" menus should have the "Format it / Keep existing data" choice as normal partitions do.

Matthew Caron (matt-mattcaron) wrote :

This bug just bit me too.

- Had an Xubuntu 8.04 instance loaded off the alternate CD and created /boot and the rest as an encrypted volume. That volume was used for LVM, which contained all the partitions for my system.
- Upgrade 8.04 to 8.10
- Want to upgrade to 9.04. Decide to do a fresh reload of Ubuntu 9.04.
- Partitioner sees /boot, but doesn't recognize that there is an encrypted filesystem there. I had to manually mark that it was an ecrypted filesystem, but that apparently causes it to kill the encrypted partition and recreate it (or rewrite the crypto headers, or something).

tmerriam (tmerriam87) wrote :

Confirmed in Jaunty, I gave up on the alternate install disc because of this.

Roy Jamison (xteejx) wrote :

Marking Confirmed, High. Thank you.

Changed in partman-crypto (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Changed in partman-crypto:
status: Unknown → New
Roy Jamison (xteejx) wrote :

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 the current Ubuntu version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

Changed in partman-crypto (Ubuntu):
status: Confirmed → Incomplete
Matthew Caron (matt-mattcaron) wrote :

Problem persists with Ubuntu 10.10. The partitioner allows for setting a volume as a "physical volume for encryption", but when you go to "Configure encrypted volumes" it only allows creation of a new volume, not unlocking and use of an existing volume.

Roy Jamison (xteejx) wrote :

Thank you for the update, marking Triaged and will update the upstream bug report. Don't forget that you can track it and add comment there, it is linked at the top of the report. Thank you again.

Changed in partman-crypto (Ubuntu):
status: Incomplete → Triaged
Colin Watson (cjwatson) wrote :

I fixed this in Ubuntu 11.10. See bug 420080 (sorry, I evidently hadn't noticed that a rather earlier bug existed).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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