Hi Brandon
On 2024/07/04 12:33, Brandon Werner wrote:
On Wed, Jul 3, 2024, at 7:38 PM, Brandon Werner wrote:
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
I found the solution. The luksbootkeyfile calamares module which generates the
/crypto_keyfile.bin file, must now be run before the fstab calamares module.
This change needs to be made in settings.conf in the calamares-settings-debian
package. This is because the fstab module now checks for the existence of
/crypto_keyfile.bin, and uses that information to influence the generation of
/etc/crypttab. For a one liner like this, its probably easier for me to just
let you all make the change and tag a release, rather than me making a PR.
I first moved luksbootkeyfile up to right before fstab, but it seems
that there is some race condition, so I moved it up to right after the
filesystem is extracted, and that seems to do the trick. I uploaded
calamares-settings-debian 13.0.8 a few minutes ago, so it will be
published in the archive with this a bit later.
Thanks for digging into it and sharing what you've found!
-Jonathan
