kdump Fails To Capture Crash Dumps

📖 ~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 kernel panic, no vmcore is written to configured dump target on reboot.

Environment & Reproduction

crashkernel memory is not reserved, kdump service is inactive, or dump path is unreachable.

Root Cause Analysis

Run sudo systemctl status kdump, grep crashkernel /proc/cmdline, and journalctl -u kdump.

Quick Triage

Set appropriate crashkernel value in GRUB, regenerate grub config, and reboot to apply.

Step-by-Step Diagnosis

Configure dump target in /etc/kdump.conf and start kdump service.

Solution – Primary Fix

Perform controlled crash test with sysrq trigger and verify vmcore generation.

Solution – Alternative Approaches

Confirm vmcore files exist with expected timestamps and readable metadata.

Verification & Acceptance Criteria

Revert crashkernel settings if memory pressure is unacceptable and redesign sizing.

Rollback Plan

Validate kdump after kernel updates and keep dump target capacity monitored.

Prevention & Hardening

Alert when kdump service is inactive or dump target path is unavailable.

Related Errors & Cross-Refs

Include periodic kdump readiness checks in maintenance and compliance routines.

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

Review kdumpctl, kexec-tools, and RHEL 9 crash dump administration guides.