Hello,
According to [1][2][3] and [5]:
If you reset your tpm, you will loose the ability to access data stored in the tpm and used for your system (if used).
By the way, you can upgrade your installation because systemd packages has been updated in the last weeks.
Hope this helps.
--
[1] systemd - systemd-tpm2-setup-early fails when PIN set for owner hierarchy #32898
[2] systemd - tpm2-setup: Don't fail if we can't access the TPM due to authorization failure #32899
[3] patch - tpm2-setup: Don't fail if we can't access the TPM due to authorization failure #32899
[4] systemd - Setting up DA lockout configuration / manually recovering from DA lockout mode
[5] Error on TPM2 and Ubuntu 19.04
--
Some interesting documentation:
So, you have already manually modified your tpm configuration.I'm pretty sure i reset the SRK a couple months ago when I was first trying to figure this all out. After a reboot, I don't see the 0x0902 error every 10s but, iirc, it starts later at some point, i guess after running out of memory for whatever reason! Yep after 5 hours uptime, it started like this:Code:
[Dec19 01:22]tpm tpm0: A TPM error (357) occurred flushing context[Dec19 01:23]tpm tpm0: tpm2_load_context: failed with a TPM error 0x0902
According to [1][2][3] and [5]:
0x9a2 error means that the authorization failed. Seems like there is a auth (password) setup for the owner hierarchy and by […] tpm2_createprimary use an empty auth. You can change the auth to an empty one:("") -means empty passCode:
$ tpm2_changeauth -c o -p <OLD_PASS> ""
and after that both the tpm2_createprimary [..]should work with the default.
[..]
Whenever I run into this 0x9a2 issue, it is a problem with the TPM, not the tools.
My "solution" is to go into the BIOS, and clear the TPM. This will delete everything stored in it. Be careful!
If you reset your tpm, you will loose the ability to access data stored in the tpm and used for your system (if used).
By the way, you can upgrade your installation because systemd packages has been updated in the last weeks.
Hope this helps.
--
[1] systemd - systemd-tpm2-setup-early fails when PIN set for owner hierarchy #32898
[2] systemd - tpm2-setup: Don't fail if we can't access the TPM due to authorization failure #32899
[3] patch - tpm2-setup: Don't fail if we can't access the TPM due to authorization failure #32899
[4] systemd - Setting up DA lockout configuration / manually recovering from DA lockout mode
[5] Error on TPM2 and Ubuntu 19.04
--
Some interesting documentation:
- TPM2.0 in Linux - Enabling the TPM2.0 Ecosystem in Linux
- Using the TPM - It's Not Rocket Science (Anymore)
- Using the tpm its not rocket science anymore slides (pdf)
- systemd and TPM2 - Lennart Poettering
- grub2 - Measuring boot components
Statistics: Posted by Aki — 2024-12-21 19:58