RHEL 9 Kernel Update Installed but Old Kernel Still Boots

📖 ~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

A new kernel RPM installs on RHEL 9, but the system keeps booting an older kernel.

Environment & Reproduction

uname -r output does not match latest installed kernel and expected fixes are absent.

Root Cause Analysis

Bootloader default entry points to an older kernel, or reboot did not complete to target host.

Quick Triage

List versions with ‘rpm -q kernel’ and confirm the newest build is present and valid.

Step-by-Step Diagnosis

Use grubby to display current default and verify it references the newest kernel path.

Solution – Primary Fix

Select the right kernel entry, reboot, then verify with ‘uname -r’ after startup.

Solution – Alternative Approaches

Confirm normal multi-user or graphical targets load and no emergency mode fallbacks force old behavior.

Verification & Acceptance Criteria

Validate initramfs and boot partition free space to avoid incomplete update artifacts.

Rollback Plan

In Secure Boot environments, ensure signed kernel artifacts are accepted by platform firmware.

Prevention & Hardening

Use ‘journalctl -b -1 –no-pager’ to inspect previous boot and detect bootloader handoff issues.

Related Errors & Cross-Refs

Keep at least one known-good prior kernel entry available for emergency rollback.

Related tutorial: View the step-by-step tutorial for rhel-9.

View all rhel-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Automate kernel update validation with post-reboot checks and alert when running kernel is not expected.