Kdump service failed to restart due to bad mount point

Solution Unverified - Updated -

Issue

  • Why did Kdump service failed to restart with below messages on console?
# service kdump restart
Stopping kdump:[  OK  ]
No kdump initial ramdisk found.[WARNING]
Rebuilding /boot/initrd-2.6.18-194.17.4.el5kdump.img
findfs: Unable to resolve 'UUID=1AXRta-yNIc-PlRj-eAHG-L25n-vNff-yeziTT'
mount: special device UUID=1AXRta-yNIc-PlRj-eAHG-L25n-vNff-yeziTT does not exist
/etc/kdump.conf: Bad mount point UUID=1AXRta-yNIc-PlRj-eAHG-L25n-vNff-yeziTT
Failed to run mkdumprd
  • "/core" is target specified in kdump.conf.
core_collector makedumpfile -d 31 -c
ext3 UUID=1AXRta-yNIc-PlRj-eAHG-L25n-vNff-yeziTT
path /core
  • "/dev/rootvg/core" filesystem is mounted on "/core" mount point.
/dev/rootvg/core        /core                   ext3    defaults        1 2

Environment

  • Red Hat Enterprise Linux 5,6
  • Kdump

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

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