Bug#660191: debian-installer: installer should recogise existing encrypted partitions
Hi there,
I would like to see such a feature, too. There are two situations when
it's usefull. Since I found a way dealing with it
1. Some time ago I killed my initrd during an update and had to repair
my encrypted LVM system. D-I helped repairing it in rescue mode:
- Booting D-I (Wheezy, testing around april 2012) in Rescue-Mode
- IIRC D-I allowed to enter the passphrase for the encrypted LVM
- choosed root-partition
- opened tty2:
- mount /boot
- mkinitramfs -o /boot/initrd.img-rescue 3.2.0-2-amd64
- exit and reboot
- during startup I had to change the initrd (grub).
This could be repaired by updating grub in the running system.
2. I now would like to install jessie as a second OS. I want it to live
in a seperate volume of my existing encrypted LVM, but D-I (from end October 2013) is not able
to recognize it automatically.
I found an older tutorial (german language) for a workaround at
http://blog.stefan-betz.net/2009/1/6/debian-installer-mit-bereits-vorhandenem-verschluesseltem-lvm-verwenden/
It says:
- boot D-I as usual
- after setting up networking (in partitioing menu) go back to main menu
- open tty2 (ALT+F2) and enter the following commands:
depmod -a
modprobe dm-mod
modprobe dm-snapshot
cryptsetup luksOpen /dev/sda2 sda2_crypt
vgchange -a y
...
But here is the point it doesn't work:
cryptsetup: command not found.
I tried to load the components via the d-i menu, but this doesn't work,
too. Modules are loadable but I can't find crytpsetup itself.
Of course there is a way to work around it, but my abilities comes to
its limits and it seems to be less painfull using debootstrap.
So: it would be (very) nice to have it officially supported in d-i.
Christian Meyer
Reply to: