Good morning community.
I have this morning run into emergency mode on Rocky Linux 8.6.
Analysis on logs tells me that : Kernel is locked down from EFI secure boot.
I am unable to unlock the Kernel coupled with the fear to lose my system.
Kindly advice on how to securely unlock the Kernel.
I’m not so sure that is your issue. I have two Rocky 9 machines (and a fedora machine) that reports the same message on boot and they come up fine.
[root@mchub01 ~]# cat /etc/fedora-release
Fedora release 36 (Thirty Six)
[root@mchub01 ~]# dmesg | grep 'EFI Secure Boot' -A1
[ 0.000000] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
[ 0.000000] SMBIOS 2.8 present.
[root@idp ~]# cat /etc/rocky-release
Rocky Linux release 9.0 (Blue Onyx)
[root@idp ~]# journalctl | grep 'EFI Secure Boot'
Aug 01 00:29:59 idp.angelsofclockwork.net kernel: Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
[root@awx ~]# cat /etc/rocky-release
Rocky Linux release 9.0 (Blue Onyx)
[root@awx ~]# journalctl | grep 'EFI Secure Boot'
Jul 30 19:47:43 awx.angelsofclockwork.net kernel: Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
You’ll need to dig further into the journal to pinpoint where the issue is.
I get you sir.
Running systemctl command , I have two issues marked in red.
boot-efi.mount is loaded but failed /boot/EFI
systemd-modules-load.service is loaded but failed with the description I Load Kernel Modules.
I have checked the /etc/fstab file and I have confirmed the /boot/efi UUID is the exact one displayed by the blkid command .
At this time , 3 hrs later am still trying to think around this.
Any idea sir ?
So is this the same hardware as in this post of yours?
or is it a different install?
If it is that hardware that was running previously without entering emergency mode what changes did you make to system prior to this event?
If for example you installed proprietary Nvidia driver modules then you will not be able to use Secure-Boot as they are not signed and thus violate the requirements for Secure-Boot.
Yes this is the same hardware. I accidentally lost my system , and had to do a fresh installation.
It’s now on Rocky Linux 9 and the error apparently didn’t reoccur .
Thank you