Public bug reported:
Binary package hint: debian-installer
I have (or rather: had) a working LUKS device on /dev/sdb6. The
partition type was set to x8E (LVM) since the encrypted volume was used
as an LVM physical volume.
Now I wanted to set up a second installation on the same system. I
created partitions /dev/sda3 and /dev/sdb3, both with type LVM. I did
not perform any initialization. Then I booted the Jaunty alternate
installation cd. I chose "Manual Partitioning" and directly switched
into the LVM setup. There I added the /dev/sda3 and /dev/sdb3 partitions
as volume groups. I never touched /dev/sdb6. I created some logical
volumes and saved this setup. Back in the partitioning menu, I noted
that the logical volumes were set as "linear" rather than "striped".
Since I had not seen any option to change this, I decided to do the LVM
setup in the existing system and rebooted the computer.
Unfortunately the system does not boot anymore, since it cannot find the
encrypted source device. When booting from the Live CD, I found that the
volume has apparently been damaged:
# cryptsetup luksDump /dev/sdb6
Command failed: /dev/sdb6 is not a LUKS partition
Any ideas on how to recover the data are also greatly appreciated.
** Affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
--
Installer garbled unrelated LVM partition
https://bugs.launchpad.net/bugs/380059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
