[RHEL6 Alpha] fsck command fails while gathering kdump

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux 6.0 Alpha-3 (and earlier)

Issue

  • fsck command fails while gathering kdump:

    Creating block device sda
Creating block device sr0
hwlock:can't open '/dev/misc/rtc': No such or directory
Saving to the local filesystem LABREL=/dump
end_request: I/O error, dev fd0, sector 0
fsck.ext3: not found
Copying data                         : [ 54 %]

Resolution

The fix has been checked in as of kexec-tools-2.0.0-62.el6 and will be included when RHEL6 is released

Root Cause

Recent busybox versions changed how fsck works.  Now busybox just does a callout to the other fsck utilities (fsck.ext3, fsck.ext4, etc), so they need to be included in the kdump initrd.

Diagnostic Steps

  • reproduced on lab machine
  • review contents of kdump initrd, specifically init script and included binaries

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.

Comments