[SOLVED] Unable to write 'LoaderSystemToken' EFI variable (firmware problem?), ignoring: Invalid argument

[mladenciric]

Hello,
I have custom server with two ssd disk in zfs mirror pool as rpool with boot efi.
One of the disks are fault and i decide to replace it.
The fault disk is with label sdb, and replacing disk also got that label.
I follow instruction how to change zfs boot disk but i got error message when is issue command proxmox-boot-tool init /dev/sdb2

The error message is
Unable to write 'LoaderSystemToken' EFI variable (firmware problem?), ignoring: Invalid argument

I want to note that this is not first time to me to change ssd disk in rpool using official tutorial and i never have a problem like this, but previous changings was on host with legacy bios (grub).
I check Secure boot settings on BIOS, as someone suggested and it is disabled in BIOS.
After i use sgdisk command to copy partition table to new disk from working disk, and use zpool replace command to change partition 3 of faulty disk with new ssd, resilvering passing without errors

pool: rpool
state: ONLINE
status: Some supported and requested features are not enabled on the pool.
The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(7) for details.
scan: resilvered 3.12G in 00:00:16 with 0 errors on Thu Aug 1 16:22:35 2024
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ata-KINGSTON_SUV500240G_50026B7782172E67-part3 ONLINE 0 0 0
ata-Samsung_SSD_870_EVO_250GB_S6PENL0X200968H-part3 ONLINE 0 0 0

errors: No known data errors

command output is as follows:

/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
3759-9CE6 is configured with: uefi (versions: 5.15.158-1-pve, 5.15.158-2-pve, 5.4.195-1-pve)

root@pm0:/home/ma1den# lsblk -o +FSTYPE
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT FSTYPE
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 512M 0 part vfat
└─sda3 8:3 0 223.1G 0 part zfs_member
sdb 8:16 0 232.9G 0 disk
├─sdb1 8:17 0 1007K 0 part
├─sdb2 8:18 0 512M 0 part vfat
└─sdb3 8:19 0 223.1G 0 part zfs_member

root@pm0:/home/ma1den# proxmox-boot-tool format /dev/sdb2 --force
UUID="B9E7-4008" SIZE="536870912" FSTYPE="vfat" PARTTYPE="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PKNAME="sdb" MOUNTPOINT=""
Formatting '/dev/sdb2' as vfat..
mkfs.fat 4.2 (2021-01-31)
Done.

root@pm0:/home/ma1den# proxmox-boot-tool init /dev/sdb2
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
UUID="AFF9-ACA5" SIZE="536870912" FSTYPE="vfat" PARTTYPE="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PKNAME="sdb" MOUNTPOINT=""
Mounting '/dev/sdb2' on '/var/tmp/espmounts/AFF9-ACA5'.
Installing systemd-boot..
Created "/var/tmp/espmounts/AFF9-ACA5/EFI/systemd".
Created "/var/tmp/espmounts/AFF9-ACA5/EFI/BOOT".
Created "/var/tmp/espmounts/AFF9-ACA5/loader".
Created "/var/tmp/espmounts/AFF9-ACA5/loader/entries".
Created "/var/tmp/espmounts/AFF9-ACA5/EFI/Linux".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/AFF9-ACA5/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/AFF9-ACA5/EFI/BOOT/BOOTX64.EFI".
Random seed file /var/tmp/espmounts/AFF9-ACA5/loader/random-seed successfully written (512 bytes).
Unable to write 'LoaderSystemToken' EFI variable (firmware problem?), ignoring: Invalid argument
Failed to create EFI Boot variable entry: Invalid argument

After all suggested checking from posts on forum i try this command:
pve-efiboot-tool init /dev/sdb2
pve-efiboot-tool refresh
but i got same error message

Please if anyone can help me to resolve this issue because i plan to change second old ssd with new one to prevent another ssd failure.

 

[mladenciric]

SOLVED / SOLUTION
I revert BIOS to defaults and setup BIOS again (same settings) and then it works without any error.
This is strange and things shouldn't work like that but in my case that was solution.
Also, it could be solution as someone wrote, to update/upgrade BIOS, but in my case there are no new version, in use is already latest version.
I hope this will useful to someone.