Public bug reported:
This is an old one a a really totally destroying showstopper, it leads
to this:
Users after installing a new version of Ubuntu on a new hard disk can
not access their files on the old hard disk because the lvm volume has
THE SAME NAME! The procedure to rename the vg is absolutely not doable
by an average user, much too complicated with editing grub.cfg etc.
I am really disappointed by this. The installer makes it easy for users
to encrypt their hard drives - but then this comes with such an annoying
time bomb, leaving people with an unsolvable problem, not able to access
their data.
The installer should of course create lvm names with some random part,
so it is no problem to mount your old disk and copy your data.
Thinking about it one more question comes up: why on earth is LVM not
able to mount volumes with the same name? It is using that user given
string as an ID? Really? What are people with hundreds of archive disks
doing? They have a notebook with all the volume names, so they now which
name not to pick for a new hard disk? come on...
** Affects: base-installer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759962
Title:
Can not mount old hd after new installation because of multiple VGs
found with the same name skipping xubuntu-vg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1759962/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
