CentOS Stream 10 – Common Problem 241 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Boot menu only lists the latest kernel after grub2-mkconfig, hiding rollback options on failures.

Environment & Reproduction

Common when /boot/loader/entries are deleted or BLS_USE_BOOT is misconfigured during cleanup.

Root Cause Analysis

Boot Loader Specification entries were removed; grub2-mkconfig alone no longer recreates legacy menu blocks.

Quick Triage

List /boot/loader/entries and check installed kernels with rpm -q kernel.

Step-by-Step Diagnosis

Run: ls /boot/loader/entries; rpm -q kernel; cat /etc/default/grub.

Solution – Primary Fix

Run: sudo kernel-install add $(uname -r) /lib/modules/$(uname -r)/vmlinuz for each kernel.

Solution – Alternative Approaches

Reinstall kernel packages with sudo dnf reinstall kernel-core to regenerate BLS entries.

Verification & Acceptance Criteria

grub menu lists all installed kernels and grub2-editenv saved_entry matches the desired default.

Rollback Plan

Restore /boot/loader/entries from backup or fallback to legacy grub.cfg generation.

Prevention & Hardening

Avoid manual edits in /boot/loader/entries and rely on kernel-install hooks for changes.

Related Errors & Cross-Refs

Related to dracut omitted modules and grub2 secure boot signing 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

grub2-mkconfig(8) and Red Hat boot loader documentation.