So when i boot my device (Luks2 (unlock with TPM2 + Pin)) on systemd-boot after some wait while the system ask the pin to use the key it taken from the TPM, the system seem to “go” into emergency mode after this (i will call it timeout)
I searched how to prevent this emergency mode, and i come across this archwiki, i followed the URL to systemd, and applied the recommendation : sudo systemctl mask rescue.target rescue.service emergency.target emergency.service (also masked the rescue after more research), and relaunched mkinitcpio -P.
Yet it still happen.
So my question is this one “does someone know how to prevent this emergency mode” in the initramfs (since we are in preboot) ?
My goal is purely beauty of the boot not security increase, as root is disabled in emergency mode and it will ask the encryption pin even there.
Thanks
cscs 2
Masking those units will not have any impact on the presence or not of the emergency mode in the initram. As mentioned in a note at the link;
I guess we could look at the /etc/mkinitcpio.conf or any custom file if in use.
how would eliminating emergency mode do this?
was one of the idea i had.
If you have an alternative to prevent the password prompt waiting for the TPM2 pin to stop and fell into emergency mode, i take it.
what is exactly the system that prompt the pin / password of Luks in the bootprocess ? (so i can try to find a way to increase the timeout (if i cannot disable it).
My expectation would be that eliminating emergency mode wouldn’t do anything in that regard. You need to control the step you want to control.
do you have a timeout entered as specified here?
you are right, i jumped to the gun to disable what i seen, will check for a timeout, and if i cannot find one, do you think it’s possible to “shutdown” the computer at the end of it.
i think in my memory i had a linux that did that if i did not enter the luks password fast enough in the past.