The problem arises when the Raspberry Pi boots up. Instead of unlocking the partition automatically using the TPM it does it via "software" and the boot process takes too long, and the LUKS partition is not well linked.
I have performed additional tests and the cryptographic functionalities appear to be operating properly. This problem arises when there is a loss of voltage in the Raspberry that takes longer than normal to start up
I would greatly appreciate it if you could provide guidance or assistance in resolving this issue. I am willing to provide additional details, such as commands used and system configuration, if necessary to diagnose the problem.
The partition is encrypted with LUKS and for automatic unlocking I have used clevis.
The problem arises when the Raspberry Pi boots up. Instead of unlocking the partition automatically using the TPM it does it via "software" and the boot process takes too long, and the LUKS partition is not well linked.
I have performed additional tests and the cryptographic functionalities appear to be operating properly. This problem arises when there is a loss of voltage in the Raspberry that takes longer than normal to start up
I would greatly appreciate it if you could provide guidance or assistance in resolving this issue. I am willing to provide additional details, such as commands used and system configuration, if necessary to diagnose the problem.
The partition is encrypted with LUKS and for automatic unlocking I have used clevis.