Hide Forgot
Description of problem: If /etc/mdadm.conf does not contain "level=", mkdumprd parses the file incorrectly, looking for an "ARRAY" module. Version-Release number of selected component (if applicable): 2.0.0.188.el6 How reproducible: 100% Steps to Reproduce: 1. /etc/mdadm.conf: ARRAY /dev/md1 metadata=1.2 name=elliot.mno.stratus.com:1 UUID=b0371fff:5f24c046:90f04bf0:dbf53e43 2. (Re)start the kdump service Actual results: No module ARRAY found for kernel 2.6.32-131.0.15.el6.exp10.bz16586.x86_64, aborting. Failed to run mkdumprd Additional info: This is a regression, bz490818 fixed this in release 5.3 by running /sbin/mdadm --examine instead of relying upon the /etc/mdadm.conf file.
*** This bug has been marked as a duplicate of bug 707805 ***
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously, the mkdumprd utility failed to parse the /etc/mdadm.cof configuration file. As a consequence, mkdumprd failed to create an initial ramdisk for kdump crash recovery and the kdump service failed to start. With this update, mkdumprd has been modified so that it now parses the configuration file and builds initrd correctly. The kdump service now starts as expected.