Fixing automatic tpm2 unlock

[J-Kappes]

I don't know why, but the automatic tpm2 unlock has stopped working. Right before the crypt key prompt, I get the message that the "ubuntu-vg" volume isn't found.

After manually entering my crypt key, everything seems to run just fine.

I tried running tpm2-unlock.sh again, but it says it shouldn't be run twice.

[szaimen]

Hi, see nextcloud/vm#2692

[J-Kappes]

Or the outputs got changed to no longer include "2.0":

sudo dmesg | grep -i "tpm"
[    0.000000] efi: TPMFinalLog=0x78d84000 ACPI=0x78e2b000 ACPI 2.0=0x78e2b014 SMBIOS=0x75e53000 SMBIOS 3.0=0x75e51000 ESRT=0x75e3e398 MEMATTR=0x72ef7018 MOKvar=0x75e36000 RNG=0x78df5018 TPMEventLog=0x66825018 
[    0.016884] ACPI: TPM2 0x0000000078E26000 000034 (v04 HPQOEM 84D4     00000002 HP   00040000)
[    0.017236] ACPI: Reserving TPM2 table memory at [mem 0x78e26000-0x78e26033]

[szaimen]

I see. I guess the script needs to be adjusted then. Can you do so?

[J-Kappes]

Yes, I've already done so locally. Do you mean here on github?

[J-Kappes]

The automatic unlock works now. Thanks :)

[szaimen]

Yes, I've already done so locally. Do you mean here on github?

Yes :)

[boraozgen]

My auto unlock broke today after years of use. Re-running the script fixed it, but I don't understand how it could break. What are possible causes? There was a power outage today, can it be related? Can a software update break this? Is there any way to debug this?