Bug 650596

Summary:	No md raid array after installation completed due to misconfigured grub.conf
Product:	[Fedora] Fedora	Reporter:	Jurgen Kramer <gtmkramer>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	anaconda-maint-list, jonathan, vanmeeuwen+fedora
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-11-07 16:12:13 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 Jurgen Kramer 2010-11-07 10:07:02 UTC

Description of problem:
After installing F14 on my system with a raid5 md array on separate disks it was not online (and dmesg showed a segfault in mdadm).

Version-Release number of selected component (if applicable):
anaconda version that came with F14 install DVD (x86_64)

How reproducible:
always

Steps to Reproduce:
1. Install F14 on empty HDD
2. Disk partitioning shows the software raid partitions -> keep intact
3. Finish installation 
  
Actual results:
No md0 raid device

Expected results:
Working md0 raid device

Additional info:
The raid array was created with F11 and is/was running properly. I did supply the correct /etc/mdadm.conf. Checking the kernel messages and the output of /proc/mdstat suggested the raid is not online due to dracut configuration. The kernel line in /etc/grub.conf shows rd_NO_MD !! after removing this and rerunning dracut the raid array is working as it should.

Comment 1 Chris Lumens 2010-11-07 16:12:13 UTC


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