Kdump fails when NFS mount is not mounted

Solution Verified - Updated -

Issue

  • Starting the kdump service fails
  • journald indicates the mount point is likely not mounted. It will look similar to the following:
# systemctl status -l kdump.service
● kdump.service - Crash recovery kernel arming
   Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2016-09-13 10:59:49 EDT; 7s ago
  Process: 112357 ExecStart=/usr/bin/kdumpctl start (code=exited, status=1/FAILURE)
 Main PID: 112357 (code=exited, status=1/FAILURE)

Sep 13 10:59:48 nfs-clinet.example.com [1]: Starting Crash recovery kernel arming...
Sep 13 10:59:48 nfs-clinet.example.com kdumpctl[112357]: No kdump initial ramdisk found.
Sep 13 10:59:48 nfs-clinet.example.com kdumpctl[112357]: Rebuilding /boot/initramfs-3.10.0-327.13.1.el7.x86_64kdump.img
Sep 13 10:59:49 nfs-clinet.example.com kdumpctl[112357]: Dump target nfs-server.example.com:/kdump is probably not mounted.
Sep 13 10:59:49 nfs-clinet.example.com kdumpctl[112357]: mkdumprd: failed to make kdump initrd
Sep 13 10:59:49 nfs-clinet.example.com kdumpctl[112357]: Starting kdump: [FAILED]
Sep 13 10:59:49 nfs-clinet.example.com systemd[1]: kdump.service: main process exited, code=exited, status=1/FAILURE
Sep 13 10:59:49 nfs-clinet.example.com systemd[1]: Failed to start Crash recovery kernel arming.
Sep 13 10:59:49 nfs-clinet.example.com systemd[1]: Unit kdump.service entered failed state.
Sep 13 10:59:49 nfs-clinet.example.com systemd[1]: kdump.service failed.

Environment

  • Red Hat Enterprise Linux (RHEL) 7.0 - 7.2
  • kexec-tools below version kexec-tools-2.0.7-50.el7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content