Kdump Not Capturing Crash Dumps on RHEL 9

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

After a panic event, no vmcore is created under configured dump directory.

Environment & Reproduction

Missing crashkernel boot parameter, kdump disabled, or dump target misconfigured.

Root Cause Analysis

Run: systemctl status kdump, cat /proc/cmdline, and kdumpctl status.

Quick Triage

Ensure dump target has enough space and dracut includes required storage/network modules.

Step-by-Step Diagnosis

Capture missing crashkernel or inactive service evidence.

Solution – Primary Fix

Capture active kdump status after enabling and rebooting.

Solution – Alternative Approaches

Set crashkernel in GRUB and regenerate config, then reboot.

Verification & Acceptance Criteria

Enable service: sudo systemctl enable –now kdump.

Rollback Plan

Run kdumpctl test if policy allows and verify vmcore destination.

Prevention & Hardening

Confirm kdumpctl status is operational and target path is writable.

Related Errors & Cross-Refs

Include crashkernel parameter checks in patch compliance and build validation.

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

Revert GRUB crashkernel settings if memory pressure becomes unacceptable.