You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Servicereport kdump plugin should check initrd-kdump.img for the required kernel module to capture the crash dump at the configured mount point. For example, if /etc/kdump.conf is configured to dump at a local path, that's mounted on multipath disk but the dm_* module are missing from the initrd-kdump.img. Such configurations fail to capture the dump, when the initrd-kdump.img is not build with required kernel modules.
One way to teach Servicereport, to identify the missing module and fix the module dependency issue:
Check /etc/kdump.conf for mount point
Based on the mount point, check dracut --list-module /boot/initrd-kdump.img for the required kernel module and
Add it using dracut --add-drivers "<module names>" /boot/initrd-kdump.img or
Add dracut_args --add-drivers "<module name>" in /etc/kdump.conf
The text was updated successfully, but these errors were encountered:
Servicereport kdump plugin should check
initrd-kdump.img
for the required kernel module to capture the crash dump at the configured mount point. For example, if/etc/kdump.conf
is configured to dump at a local path, that's mounted on multipath disk but thedm_*
module are missing from theinitrd-kdump.img
. Such configurations fail to capture the dump, when theinitrd-kdump.img
is not build with required kernel modules.One way to teach Servicereport, to identify the missing module and fix the module dependency issue:
/etc/kdump.conf
for mount pointdracut --list-module /boot/initrd-kdump.img
for the required kernel module anddracut --add-drivers "<module names>" /boot/initrd-kdump.img
ordracut_args --add-drivers "<module name>"
in/etc/kdump.conf
The text was updated successfully, but these errors were encountered: