Bug#917117: grub-efi-amd64-signed: doesn't mount cryptodisk

[Colin Watson]

On Sun, Dec 23, 2018 at 12:13:08AM +0300, Alexander Batischev wrote:
> I'm running a UEFI system. I have GRUB_ENABLE_CRYPTODISK=y in my 
> /etc/default/grub. Ever since 2.02+dfsg1+6, each GRUB2 update removes 
> cryptomount call from /boot/efi/EFI/debian/grub.cfg, and thus breaks the 
> boot: GRUB drops into a recovery shell, unable to find my root partition 
> (which is on LVM inside LUKS). /boot/efi is where I mount the ESP 
> partition. I don't recall if the problem existed before 2.02+dfsg1+6.
> 
> This has been reported in #908162 before (against 2.02+dfsg1+6). 
> Ostensibly fixed in 2.02+dfsg1+7, but I still experience the bug.

Could you please see if 2.02+dfsg1-10 fixes this?  A couple of people
pointed out that I forgot to add the luks module to the output of
build-efi-images, which may have caused this.

(It may take a little while for the corresponding -signed version to
show up, if you need that, but in theory it should be on its way; I'm
not entirely familiar with all the archive-side plumbing that produces
that as yet.)

Thanks,

-- 
Colin Watson                                       [cjwatson at debian.org]