Source: partman-efi
Version: 110
Severity: normal
Tags: d-i
X-Debbugs-Cc: [email protected], [email protected]
package is a guess, please move as needed.
Installed with "Guided - use entire disk and set up encrypted LVM" and
was surprised to see logs mentioning a previous very brief Kali install
that had been done on the same machine.
Should old UEFI vars be wiped if using one of the entire disk partman
recipes?
$ journalctl --no-pager -b -t systemd-hibernate-resume | perl -lpe 's/UUID=[^
]* //;' | cut -d' ' -f 1-3,5-
Jan 07 22:18:07 systemd-hibernate-resume[1023]: Reported hibernation image:
ID=kali VERSION_ID=2025.3 kernel=6.12.38+kali-amd64 offset=0
Jan 07 22:18:07 systemd-hibernate-resume[1023]: HibernateLocation system
identifier doesn't match currently running system, would not resume from it.
$ < /sys/firmware/efi/efivars/HibernateLocation-* tr -d '\000\a' | jq
'del(.uuid)'
{
"offset": 0,
"kernelVersion": "6.12.38+kali-amd64",
"osReleaseId": "kali",
"osReleaseVersionId": "2025.3"
}
-- System Information:
Debian Release: 13.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security-debug'), (500,
'stable-security'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
