Description of problem: mkdumprd fails while parsing my mdadm.conf file (enclosed). It seems to be looking for a RAID level number, which is not there and the fails, aborting creation of the initrd file. Version-Release number of selected component (if applicable): Fedora-13 kexec-tools.x86_64 2.0.0-36.fc13 mdadm.x86_64 3.1.2-10.fc13 How reproducible: TOTALLY with my mdadm.conf prior to installing VirtualBox and KVM. They have uncovered other latent bugs that seem to cause an earlier fail. Steps to Reproduce: 1. Have my /etc/mdadm.conf 2. rm -f /boot/initrd*kdump.img 3. service kdump start Actual results: No kdump initrd .... Rebuilding /boot/initrd... IN HANDLERAID No module ARRAY found for kernel... This aborts the attempt to Expected results: rebuild initrd Additional info: I'm running on a DELL T3500, with ICH10R fake raid controller, and two 1-TB SATA drives in a RAID-1 configuration. /dev/md127p1 is the boot partition and the rest of the RAID-1 (/dev/md127p2) is configured as an LVM PV. My /etc/mdadm.conf was generated at install time. Here it is $ cat /etc/mdadm.conf # mdadm.conf written out by anaconda MAILADDR root AUTO +imsm +1.x -all ARRAY /dev/md0 UUID=97a96c74:ad42f440:0a32a68e:41e25eaa ARRAY /dev/md127 UUID=3998c76c:0221a91e:7d4d5a$ more /etc/mdadm.conf
please try the mkdumprd I attached in bz 629003. That should solve this problem
Somehow I created two identical tickets. My Bad. Closing this one. *** This bug has been marked as a duplicate of bug 629013 ***