Kdump hangs waiting for 3rd party storage device

Solution In Progress - Updated -

Environment

  • Red Hat Enterprise Linux 5

Issue

  • Kdump hangs waiting for 3rd party storage device

Resolution

  • Check for /etc/critical-disks to validate if a 3rd party kernel module is required to access that drive.
  • Move /etc/critical-disks to a temporary file with a different name, touch /etc/kdump.conf, and restart the kdump service with service kdump restart

Root Cause

  • The devices in file /etc/critical-disks need to become available before the kdump process can continue. This is an issue if you have blacklisted kernel modules within /etc/kdump.conf.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.