After a crash, kdump startup hangs with a message "A start job is running for...dev-disk...xxxxx.device" and fails to collect a vmcore

Solution Verified - Updated -

Issue

  • kdump fails with dump target on multipathed storage, e.g. a Fibre Channel (FC) LUN.

  • When a kdump is collected, processing stops with the following message.

    A start job is running for dev-disk...xxxxxxxxxx.device

    dev-disk...xxxxxxxxxx.device appears to be the multipath device to which a kdump will be saved.

Environment

  • Red Hat Enterprise Linux (RHEL) 8:
    • RHEL 8.5 - 8.9 (including)
    • dracut-049-191.git20210920.el8 or newer
    • kexec-tools-2.0.26-8.el8 or older
  • Red Hat Enterprise Linux 8.4 using EUS (or similar) repositories and a fixed release:
    • dracut-049-135.git20210121.el8_4.1 or newer
  • Red Hat Enterprise Linux 9:
    • RHEL 9.0 - 9.3
    • kexec-tools-2.0.26-8.el9 or older.
  • Multipath device configured as the kdump target with user_friendly_names enabled in multipath.conf

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