Closed TheBabu closed 5 months ago
sbctl verify
aborts on errors and the for-loop doesn't act on a ordered data structure. Remove /boot/FSCK0001.REC
as a temporary solution and I should probably not have it hard-abort on errors.
I see, is removing FSCK____.REC
safe then?
I was recently able to successfully set up secure boot using sbctl via this reddit post. And I have verified this when I run
sbctl status
. However, I see that the output ofsbctl verify
can vary wildy every time I run it. I do dual boot windows and Arch Linux, and I also have a MSI motheboard.Here is a screenshot of what I mean:![image](https://github.com/Foxboron/sbctl/assets/24832107/65251cbf-65de-4d92-9e5a-09d357a021b6)
And an asciinema recording of the weird behavior: https://asciinema.org/a/631378
It doesn't really affect me, since I secure boot is enabled and both Linux and Windows both recognize that secure boot is enabled, I was just wondering why I am seeing this behavior / is this a bug?. Also could be a sympton of the errors that I'm getting?