Bug 629012

Summary:	mkdumprd: fails parsing mdadm.conf (No module ARRAY found)
Product:	[Fedora] Fedora	Reporter:	Charles Butterfield <cb20777>
Component:	kexec-tools	Assignee:	Neil Horman <nhorman>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	13	CC:	anton, nhorman, qcai
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-09-03 00:14:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Charles Butterfield 2010-08-31 16:40:21 UTC

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

Comment 1 Neil Horman 2010-09-01 10:54:44 UTC

please try the mkdumprd I attached in bz 629003.   That should solve this problem

Comment 2 Charles Butterfield 2010-09-03 00:14:09 UTC

Somehow I created two identical tickets. My Bad.  Closing this one.

*** This bug has been marked as a duplicate of bug 629013 ***