Ubiquity detects LVM and LUKS devices as "unknown"

Bug #1060383 reported by komputes
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

In 12.10 Beta 2 Ubiquity offers to preform an installation using LVM (with encrypted option). Unfortunately it does not give the ability to recover a current LVM system. Under the "Something Else" disk formatting selection, it sees my encrypted LVM as well as my LUKS partition as "unknown".

Ideally it would allow side by side as well as recovery options (such as reinstall while preserving /home).

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity 2.12.5
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
CasperVersion: 1.324
Date: Tue Oct 2 17:54:25 2012
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
komputes (komputes) wrote :
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

First bug: no way to activate existing lvm/luks partitions. Workaround start a live session and assemble those by hand (double clicking on the disk icon).

Second bug: "Ideally it would allow side by side as well as recovery options (such as reinstall while preserving /home)." is a duplicate of bug 1046779 and it is "WON'T FIX", as automatic partitioning recipes in these case are ambigious (do you want side-by-side inside crypt, inside lvm, resize lvm volumes or add new volumes. And some of these operations are currently not supported by the underlying partitioning technology - partman.)

Changed in ubiquity (Ubuntu):
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: New → Confirmed
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.