kdump Not Capturing Kernel 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

No vmcore is generated after panic, preventing root-cause analysis for kernel-level incidents.

Environment & Reproduction

After kernel updates, boot parameter drift, storage path changes, or disabled kdump service.

Root Cause Analysis

Missing `crashkernel` reservation, invalid dump target, or kdump not enabled at boot.

Quick Triage

Run `systemctl status kdump`, inspect `/etc/default/grub`, and verify dump path capacity.

Step-by-Step Diagnosis

Use `kdumpctl showmem`, `grep crashkernel /proc/cmdline`, `journalctl -u kdump –since -1h`, and `kdumpctl status`.

Solution – Primary Fix

Kdump reports ready state, crashkernel memory is reserved, and vmcore is written on test panic.

Solution – Alternative Approaches

Set proper crashkernel parameter, regenerate GRUB config, enable kdump, and restart host in maintenance window.

Verification & Acceptance Criteria

Perform controlled crash test (`echo c > /proc/sysrq-trigger`) only in approved non-production scenarios.

Rollback Plan

Revert GRUB changes if boot instability occurs and restore previous kernel command line safely.

Prevention & Hardening

Audit kdump readiness after patch cycles and ensure dump storage is monitored for available space.

Related Errors & Cross-Refs

`systemctl enable –now kdump && kdumpctl status && grep crashkernel /proc/cmdline`

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

View all rhel-8 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

RHEL 8 kdump documentation and Red Hat support workflows for vmcore analysis collection.