#641264 debian-installer: cannot install to already encrypted partitions

#641264#5
Date:
2011-09-12 08:08:21 UTC
From:
To:
I am trying to re-install Debian wheezy to an already encrypted root partition (in order to migrate from i386 to amd64). Now, when I just boot the installer CD, and
choose "partition manually", the existing partitions (both encrypted and unencrypted) are not shown in the list of file systems. To solve this, I took inspiration from
wiki.debian.org/DebianInstaller/Rescue/Crypto i.e. I switched to the VT, ran "anna-install crypto-modules cryptsetup-udeb ; depmod -a ; modprobe dm-mod ; modprobe aes".

After that I was able to manually set up the devices using cryptsetup.

Switching back to the first VT and choosing set up hard disks, the cryptsetup partitions were now being offered, however, the unencrypted partitions remained missing
from the list of file system. This is, of course, very unfortunate, because I need to use the unencrypted boot partition in order to get a bootable system.

My computer is a dell latitude e6420 laptop.


Thanks,

Johannes

#641264#10
Date:
2011-09-12 08:45:43 UTC
From:
To:
reassign 641264 partman-crypto
forcemerge 451535 641264
thanks

I'm working on this; see #451535 for more detail.

Regards,

#641264#23
Date:
2012-02-23 20:20:33 UTC
From:
To:
Hello,

Today I downloaded an installation-CD for debian wheezy, and I ran
into the same problem.  You gave a great tip with anna-install, but I
ran into other troubles.  When I try to decrypt my encrypted
partition, I get the message

device-mapper: reload ioctl failed: Invalid argument
Failed to setup dm-crypt key mapping for device /dev/sda6.
Check that kernel supports aes-xts-plain64 cipher (check syslog for more info).
Failed to read from key storage.

I tried to modprobe xts, but that didn't fix it.  Do I need another
module, or is this cipher just not supported by the wheezy-installer?

Thanks,
Johan

#641264#32
Date:
2018-01-13 15:22:07 UTC
From:
To:
Package: debian-installer
Version: debian-9.3.0
Severity: normal

I was led to this bug report by similar output in speech synthesis + expert mode, while attempting to select the correct components to achieve a cryptsetup.

My route to success was to load the rescue component and then execute ‘depmod -a’ in a shell before the cryptsetup command. (Message #5 taught me the depmod bit; thank you.)