FS#76180 - systemd-boot Failed to write 'LoaderSystemToken' EFI variable: Invalid argument
Attached to Project:
Arch Linux
Opened by Simon Brännström (Sensu) - Wednesday, 12 October 2022, 17:17 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 12 October 2022, 23:08 GMT
Opened by Simon Brännström (Sensu) - Wednesday, 12 October 2022, 17:17 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 12 October 2022, 23:08 GMT
|
Details
Description:
I'm trying to migrate to systemd-boot from GRUB. I followed the Arch Wiki guide on removing grub and then proceeded to install systemd-boot. Not sure what I might be doing wrong, but I get an error for for LoaderSystemToken when I install systemd-boot using "sudo bootctl install" Output from the command: Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/systemd/systemd-bootx64.efi". Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/BOOT/BOOTX64.EFI". Random seed file /boot/loader/random-seed successfully written (32 bytes). Failed to write 'LoaderSystemToken' EFI variable: Invalid argument I was kinda scared it would leave me with an unbootable system, so I ran "sudo bootctl remove" and then reinstalled GRUB with "grub-install". NOTE:The attached screenshot was taken after reinstalling GRUB and rebooting the system. I haven't yet tried doing this on the LTS kernel, but I'm gonna add a comment to this once I've done so. Additional info: * package version(s): systemd 251.5-1 linux 5.19.13.arch1-1 * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: https://wiki.archlinux.org/title/GRUB#GRUB_removal https://wiki.archlinux.org/title/Systemd-boot#Installing_the_EFI_boot_manager |
This task depends upon
Comment by Toolybird (Toolybird) -
Wednesday, 12 October 2022, 23:08 GMT
There is no identifiable bug in Arch packaging here. This is more
of a support request so please use the proper support channels
(forum/IRC/etc) to seek help in debugging the problem. If an an
Arch bug turns up then of course please let us know. Searching
online I found quite a few references to the error which might
steer you in the right direction.
ksnip_20221012-190406.png