On Wed, Jul 3, 2024, at 3:05 PM, Brandon Werner wrote:
> Hi Roland,
> Thanks for your mail.
> On Wed, Jul 3, 2024, at 1:24 PM, Roland Clobus wrote:
>> Hello Brandon,
>>
>> Can you send the sha256sum of your ISO file? I guess that you might have
>> a slightly too old version. The current checksum is
>> 210d94a36c8b3ec5b980afb34b6f8267f864d1cab43eec0a9e6df4137af16635 for the
>> mate image.
>
> I checked my image and it has the same checksum as the one you listed
> above.
> 210d94a36c8b3ec5b980afb34b6f8267f864d1cab43eec0a9e6df4137af16635
> I think this issue regarding encryption is separate from the patches
> that landed to fix mounts. If I install without encryption, I have no
> trouble booting however, If I install with encryption, I end up at the
> initramfs busybox prompt after unlocking the drive in Grub and
> selecting Debian in the boot menu on both real hardware and in Qemu.
I have gotten a bit closer to the answer. the location of the keyfile
"/crypto_keyfile.bin" is not written to /etc/crypttab in the latest testing
images. If you manually write that to crypttab and rebuild the initramfs of the
installed image, the system boots fine. we now need to figure out why calamares
is not writing out the correct keyfile location. I confirmed that this does
work properly in 12.6.0 images
