rhel6: kdump on NVME device partition fails

Solution Unverified - Updated -

Issue

kdump fails on nvme device with an error message:

Saving to the local filesystem UUID=d5cb22e7-eb55-4104-a7d8-f2aa1976012c
Usage: fsck.ext4kvm: exiting hardware virtualization
 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
                [-I inode_buffer_blocks] [-P process_inode_size]
                [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
                [-E extended-options] device

If the kdump device is specified in kdump.conf via LABEL=, UUID= or explicitly using a device name:

Saving to the local filesystem /dev/nvme1n1p1
fsck.ext4: No such file or directory while trying to open /dev/nvme1n1p1
/dev/nvme1n1p1: 
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

fsck.ext4 /dev/nvme1n1p1 failed. Executing default action

Environment

  • Red Hat Enterprise Linux (RHEL) 6.6 and 6.7
  • kexec-tools-2.0.0-280.el6.x86_64.rpm
  • kdump

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