Kdump fails to capture a vmcore: "fsck: WARNING: couldn't open /etc/fstab: No such file or directory"

Solution Unverified - Updated -

Environment

  • Red Hat Enterprise Linux 5.6

Issue

  • kdump fails to capture a crash dump (vmcore) and hangs during the kexec-boot udev process:
Attmpting to enter user-space to capture vmcore
Creating root device.
Checking root device.
Checking root filesystem.
fsck 1.38 (30-Jun-2005)
fsck: WARNING: couldn't open /etc/fstab: No such file or directory
e2fsck 1.38 (30-Jun-2005)
fsck.ext3: while determing whether /dev/vg-server/lv-root is mounted.
/dev/vg-server/lv-root: recovering journal
Clearing orphaned inode nnnnnnn(uid=0, gid=0, mode=0100600, size=2048)
Clearing orphaned inode nnnnnnn(uid=0, gid=0, mode=0100600, size=0)
Clearing orphaned inode nnnnnnn(uid=0, gid=0, mode=0100600, size=512)
/dev/vg-vgname/lv-lvname: clean, nnnnn/nnnnnnnfiles, nnnnnnn/nnnnnnnblocks
Mounting root filesystem.
Trying mount -t ext4 /dev/vg-vgname/lv-lvname /sysroot
Trying mount -t ext3 /dev/vg-vgname/lv-lvname /sysroot
kjournald starting.  Commit interval 5 seconds
EXT3 FS on dm-1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Using ext3 on root filesystem
Switching to new root and running init.
type=1403 audit(1343047724.855:2): policy loaded auid=4294967295 ses=42949672
INIT: version 2.86 booting
   Welcome to Red Hat Enterprise Linux Server
Setting clock (utc): Mon Jul 23 13:48:47 BST 2012  [ OK ]
Starting udev:

Resolution

  • Please upgrade kexec-tools. This is a known issue which is addressed by ERRATA RHSA-2012-0152

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.