📖 ~1 min read
Table of contents
Symptom & Impact
After kernel upgrade the new kernel is not selectable from the GRUB menu.
Environment & Reproduction
Triggered when /etc/grub2.cfg is not regenerated after kernel installation.
Root Cause Analysis
BLS snippet generation failed or grub2-mkconfig did not run.
Quick Triage
List installed kernels with `dnf list installed kernel` and BLS entries in /boot/loader/entries.
Step-by-Step Diagnosis
Verify BLS configuration is enabled and entries exist.

Solution – Primary Fix
Regenerate with `grub2-mkconfig -o /boot/grub2/grub.cfg` and `grubby –info=ALL`.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Set default kernel with `grubby –set-default /boot/vmlinuz-…`.
Verification & Acceptance Criteria
GRUB menu lists the new kernel and it becomes the default.
Rollback Plan
Reset default kernel to the previous one if the new entry fails to boot.
Prevention & Hardening
Schedule kernel updates with `dnf-automatic` and validate post-install hooks.
Related Errors & Cross-Refs
Often co-occurs with initramfs rebuild failures and secure-boot issues.
Related tutorial: View the step-by-step tutorial for centos-stream-10.
View all centos-stream-10 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
CentOS Stream 10 GRUB and BLS reference materials.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.