Error "Failed to read secure boot state" from pveproxy since updating to 6.5.11-4-pve (8.1.3)

[automaton]

I have 2 PVE nodes running, and ever since I updated to the version in the title I get the following log messages whenever I open the web UI:

Nov 27 22:56:05 pve pveproxy[80603]: Failed to read secure boot state: can't open '/sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c' - No such file or directory

Nov 27 22:55:10 pve2 pveproxy[48806]: Failed to read secure boot state: can't open '/sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c' - No such file or directory

These are running on Dell R710s and this error does not appear in any log message before the upgrade. The machines have been running Proxmox for about 2 years and have gone through upgrades since v7. Any ideas?

 

[automaton]

I guess this is because they don't boot in secure mode, but I don't think they ever have? I'm not sure how to check past boots, but I don't think the R710 supports secure boot and I've certainly never enabled it.

root@pve:/sys/firmware/efi/efivars# dmesg | grep -i secure
[    0.000000] secureboot: Secure boot could not be determined (mode 0)
[    0.020455] secureboot: Secure boot could not be determined (mode 0)
[    1.772763] ima: secureboot mode disabled

 

[fabian]

that read is just for informational purposes (to display it in the UI when viewing the node summary). it seems to lack a guard, you can ignore the warnings until a fixed version is rolled out.

 

[fabian]

patch sent: https://lists.proxmox.com/pipermail/pve-devel/2023-November/060850.html

out of interest, could you post the output of "ls /sys/firmware/efi/efivars" ? thanks!

 

[gustagj]

I have the same problem in one of my nodes.

root@proxmox:/sys/firmware/efi/efivars# ls -la
total 0
drwxr-xr-x 2 root root   0 Nov 28 14:16 .
drwxr-xr-x 5 root root   0 Nov 28 14:16 ..
-rw-r--r-- 1 root root 298 Nov 28 14:16 Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  34 Nov 28 14:16 ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   8 Nov 28 14:16 Kernel_ATPSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root   8 Nov 28 14:16 Kernel_DriverSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root   8 Nov 28 14:16 Kernel_RvkSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root   8 Nov 28 14:16 Kernel_SiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root   8 Nov 28 14:16 Kernel_SkuSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root   8 Nov 28 14:16 Kernel_WinSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b

 

[gustagj]

I am seeing that the error message only appears as soon as I login to the node.

Any idea how to fix it ?

Dec 01 08:09:18 proxmox pvedaemon[1142]: <root@pam> successful auth for user 'root@pam'
Dec 01 08:09:21 proxmox pveproxy[98373]: Failed to read secure boot state: can't open '/sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c' - No such file or directory

 

[fabian]

just wait for it to be included in the next package updates, the fix is already applied in git.

 

[gustagj]

just wait for it to be included in the next package updates, the fix is already applied in git.

Thank you.