hello, i've been using Zorin for about a year now, im vert happy with it, but for the past month or so every now and then i've been experiencing issues, especially when turning my pc off.
first thing that made me seriously nervous is that restart option simply didn't work. it would keep my pc on loop and i'd have to turn it off manually by pressing the button. then, sometimes, when turning it off, it would freeze, the logo would pulse on the screen and the pc wouldn't turn off. then again, while turning the pc on, i'd be stuck in a loop of ">grub_" lines flashing down my entire screen. i was seriously panicked. i managed to "fix" it by completely killing the power to my pc. and now i think i hit my limit, i turned it off, it froze with the zorin logo pulsing on my screen, and i had to manually turn it off again because i had to leave. when i got back, it booted up into bios, and no matter what wouldn't boot into the os... i thought my hard drive died or something. what ended up fixing it was disabling and re-enabling secure boot, but not before giving me a heart attack with a blue screen and "Security fail"...
is there a way to fix it? is it a zorin issue? i don't know what to do
Welcome to the Forum!
So, enabling Secure Boot helps? When You installed Zorin, was there Secure Boot enabled?
hello, thank you!
i think it was enabled when i first installed zorin. i turned it off a few months ago in order to set up a dual boot or a virtual machine, but i decided i didn't really need either of them, so i deleted and reintegrated (sorry if that's not the right term) that partition, but i think i just simply forgot to reenable the secure boot until now.
Are you using Nvidia card?
You probably toggled Secure Boot. Having it enabled, by itself, would not fix the issue, but by toggling its state, that may have helped overcome a held state in memory.
Nvidia vRAM has been having trouble dumping vRAM on restart, which is why I asked.
nope, i'm using an amd gpu
all i did was search my bios for "Secure Boot", and toggled it from Disabled to Enabled. then, i exited bios, was flashed with a huge blue screen saying exactly "Verification failed 0x1a Security violation" and then it booted up Zorin os like normal
1 Like
This means that you started out with Secure boot enabled - then you enrolled keys with MOK utility.
With secure boot disabled, these keys you enrolled were not being authenticated. I stand corrected. In your case, it mattered. You can,. if you prefer Secure Boot disabled, run
mokutil --reset
1 Like
hello, i finally found the culprit!
during the brief time when i was using a dual boot, the 2nd system had its own boot option (apologies for the awful technical language, i'm trying my best) that i found by using
sudo efibootmgr -v
it returned that my BootCurrent was 0001, and that 0001 was fedora (which is exactly what i had in my dualboot)! i got rid of it by using
sudo efibootmgr -b 0001 -B
and now my PC reboots like normal, i no longer have the freezing on restart or powering off, and no longer see the blue square with the message "Verification failed 0x1a Security violation"
i'm leaving this reply in case someone also experiences a similar issue - i know i was terrified when i found absolutely nobody else have ever fcked it up this bad, haha
2 Likes
Good that it works now well. I marked Your Post as Solution.
1 Like