Import MOK state failed volume full
Hi everyone.
I had an issue a few days after my first installation of Bazzite, because of the NVRAM fulled by the enrolling keys, the MOK. I was not able to boot to my OS, and it was also impossible to launch a terminal.
So, I decided to desactivate the secure boot of my BIOS, after I had deleted the keys.
It dos not seem to be a problem but I'm not sure :
Except security reasons, could it cause me problems to use Bazzite in the future if the security boot is disabled ? Could Bazzite be stucked or broken if the security boot is disable ? Some updates would need the security boot ?
Or can I use Bazzite with the security boot disabled ? Sorry for the repetitions, my English is not always good 🙂
3 Replies
There is no hard requirement to use SecureBoot with Bazzite or any uBlue image, and there probably never will be.
If your NVRAM is full you can try to flush it by deleting every key from there via UEFI. Remember that if you are dual-booting with Windows you can remove that key by accident.
Basically SecureBoot is MS creation.
Hi Pryka.
Thanks for your feedback. I should try to boot to Windows now, maybe I have deleted it 🙃 . Well, if this is the case I don't mind, my Windows partition is small and I don't care much.
I mean Windows should restore its secureboot key on launch if it is not there. But I did see that backfire and "repair" Windows option was required.