2.2.4 Troubleshooting Secure Boot
You might encounter the following problems when Secure Boot is enabled.
- Secure boot violation: Invalid signature detected. Check Secure Boot Policy
in Setup. — The grub loader has an invalid signature.
Note:
Even though a certificate may expire, the validation is based on the date on which the grub & kernel were signed and if the certificate was valid at that time. - error: file has invalid signature. error: You need to load the kernel first. — The grub loader is signed, but the kernel is unsigned.
- ERROR: Verification failed: (15) Access Denied. Failed to load image: Access Denied.start_image() returned Access Denied — The ISO image being loaded to image the server is not signed.
Parent topic: Restricting the Binaries Used to Boot the System