Re: Can't mount crypted RAID1 disks after stable install from buster netinstall

[Rory Campbell-Lange <rory@campbell-lange.net>]

On 18/05/19, Cyril Brulebois (kibi@debian.org) wrote:
> Rory Campbell-Lange <rory@campbell-lange.net> (2019-05-15):
> > I've installed a system with / on two disks in software RAID1 with
> > dm_crypt on top from a buster netinstall disk 20190429-03:57.
> > 
> > I'm using a buster netinstall disk because the machine's ixgbe network
> > adapters aren't supported under stable.
> > 
> > After a stable install and rebooting, it isn't possible to unencrypt
> > the RAIDed volume. 
...
> > * could there be a problem in the stable component of the installer
> >   for grub or other mising support for dm_crypt?


> If you're installing stretch with a buster image, you're using
> cryptsetup-udeb from buster during the installation, which forcibly uses
> type luks2 for created encrypted devices; which then can't be opened by
> stretch's cryptsetup (that only knows about luks1).
> 
> Incidently, offering an option to stick to luks1 is something I'm
> working on right now; you might try your luck without waiting for me, by
> patching the running installation system this way: once partman-crypto
> has been installed, locate lib/crypto-base.sh and apply this:
> 
> -       /sbin/cryptsetup -c $cipher-$iv -d $pass -h $hash -s $size create $mapping $device
> +       /sbin/cryptsetup --type luks1 -c $cipher-$iv -d $pass -h $hash -s $size create $mapping $device

Hi Cyril

Thanks very much for that information. I'll give it a go.

Regards
Rory