LPAR hangs during kdump crash reboot

This document (000020315) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12

Situation

LPAR hung during crash reboot and not coming up when kdump path set to local filesystem created.

Hardware changes were made to the sever and/or it was migrated to a new OS level.

A local filesystem is defined in /etc/sysconfig/kdump such as:

KDUMP_SAVEDIR="/var/crash"

Resolution

Manually rebuild capture kernel initrd after migration and/or hardware changes.

# mkdumprd -f ; systemctl restart kdump

Cause

The initrd for the kdump kernel is generated against the system it will run on to save memory usage and disk space. It contains the minimum set of kernel modules and utilities to boot the machine to a stage where the dump target could be mounted.

With the kdump service enabled, kdump will try to detect system changes and rebuild the kdump initrd if needed. But it cannot guarantee covering every possible case. If there was a hardware change, disk migration, storage setup update, or any similar system level change, it is highly recommended to rebuild the initrd manually.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.