[Bug 1251688] [NEW] Ubuntu installer chooses non-unique name of lvm volume group, which makes it impossible to mount the second one
Tomasz Bartczak
1251688 at bugs.launchpad.net
Fri Nov 15 16:38:03 UTC 2013
Public bug reported:
Having two drives on my computer it happened to me to install ubuntu
once on one drive and again on the other.
In both situations I picked a typical installation using whole drive
with LVM and disk encryption.
Effect is that I got two Logical Volumes both named ubuntu-vg
Consequence of that is when I boot any of the drives - In Unity I can
click the other drive, put a password to unlock it, but after unlocking
- it disappears at least from Nautilus perspective.
Workaround I found after googling is to run vgrename on one, and after
that it is possible to mount it using standard nautilus tools.
Ubuntu installer should check if there is another Volume with the same
name and create a new one with unique name.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1251688
Title:
Ubuntu installer chooses non-unique name of lvm volume group, which
makes it impossible to mount the second one
Status in “ubiquity” package in Ubuntu:
New
Bug description:
Having two drives on my computer it happened to me to install ubuntu
once on one drive and again on the other.
In both situations I picked a typical installation using whole drive
with LVM and disk encryption.
Effect is that I got two Logical Volumes both named ubuntu-vg
Consequence of that is when I boot any of the drives - In Unity I can
click the other drive, put a password to unlock it, but after
unlocking - it disappears at least from Nautilus perspective.
Workaround I found after googling is to run vgrename on one, and after
that it is possible to mount it using standard nautilus tools.
Ubuntu installer should check if there is another Volume with the same
name and create a new one with unique name.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1251688/+subscriptions
More information about the foundations-bugs
mailing list