Bug 650596 - No md raid array after installation completed due to misconfigured grub.conf
Summary: No md raid array after installation completed due to misconfigured grub.conf
Keywords:
Status: CLOSED DUPLICATE of bug 649262
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-07 10:07 UTC by Jurgen Kramer
Modified: 2010-11-07 16:12 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-07 16:12:13 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.