#sbctl verify failed to find efi system partition
53 messages · Page 1 of 1 (latest)
try as root
same error
permissions?
root
what's the output of sbctl status
Installed: ✓ sbctl is installed
Owner GUID: aef2109e-086a-4d98-8d65-efdf4fdb1d78
Setup Mode: ✓ Disabled
Secure Boot: ✗ Disabled
Vendor Keys: microsoft
What's the type of the partition mounted at /boot/efi
Because secure boot is a bitch so is sbctl
fat32
❯ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 476.9G 0 disk
├─nvme0n1p1 259:1 0 100M 0 part
├─nvme0n1p2 259:2 0 16M 0 part
├─nvme0n1p3 259:3 0 290.6G 0 part
├─nvme0n1p4 259:4 0 642M 0 part
├─nvme0n1p5 259:5 0 2G 0 part /boot/efi
└─nvme0n1p6 259:6 0 183.6G 0 part /
bios boot
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 206847 204800 100M EFI System
/dev/nvme0n1p2 206848 239615 32768 16M Microsoft reserved
/dev/nvme0n1p3 239616 609687551 609447936 290.6G Microsoft basic data
/dev/nvme0n1p4 998897664 1000212479 1314816 642M Windows recovery environment
/dev/nvme0n1p5 609687552 613783551 4096000 2G BIOS boot
/dev/nvme0n1p6 613783552 998897663 385114112 183.6G Linux filesystem
Partition table entries are not in disk order.
Ya the type of /dev/nvme0n1p5 should be EFI System
I'm currently checking for safer options
You could invoke sbctl with
SYSTEMD_ESP_PATH=/boot/efi sbctl verify
this is a one command?
i have to sudo right?
you have to do sudo -i and run this one command as root
because sudo overrides environment variables
[root@crazy-OS ~]# SYSTEMD_ESP_PATH=/boot/efi sbctl verify
Verifying file database and EFI images in /boot/efi...
✗ /boot/efi/EFI/boot/bootx64.efi is not signed
✗ /boot/efi/EFI/cachyos/grubx64.efi is not signed
✗ /boot/efi/EFI/endeavouros/grubx64.efi is not signed
got this
Okay
now i put normal commands or do i have to mention like u did
you can just put SYSTEMD_ESP_PATH=/boot/efi on its own line
And you won't have to repeat it again
wait actually i dont know how to go on from this step
i used cachyOS before
it had a scipt
can u guide me a bit
That script could be in the arch repo
I suck at this as I don't use secure boot :p
Yw
You'll need to enroll keys
But that's kinda dangerous especially for certain machines
Has the risk of bricking your machine
.arch-chan-uwu Unified Extensible Firmware Interface/Secure Boot
but this article is annoying af