Bug 687863

Summary: Rescue mode with RAID partitions fails
Product: Red Hat Enterprise Linux 6 Reporter: Alexander Todorov <atodorov>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team>
Severity: high Docs Contact:
Priority: high    
Version: 6.1   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-15 17:36:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 670159    
Attachments:
Description Flags
anaconda.log
none
program.log
none
storage.log
none
syslog none

Description Alexander Todorov 2011-03-15 15:39:15 UTC
Created attachment 485525 [details]
anaconda.log

Description of problem:
When / is on RAID0 array and booting into rescue mode anaconda tells me that it can't find any Linux file systems.

Version-Release number of selected component (if applicable):
anaconda-13.21.104-1.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create a KVM domU with 2 disks: vda and vdb
2. Create the following layout:
vda1 - 1024, ext4 - /boot
vda2 - rest of space, Linux raid

vdb1 - 1024, swap
vdb2 - rest of space, Linux raid

md0 - RAID0, ext4, vda2, vdb2 - /

3. Complete the install and confirm that / is on RAID0 array
4. Boot into rescue mode. 
  
Actual results:
/ can't be found

Expected results:
/ is found and mounted under /mnt/sysimage.

Additional info:

Comment 1 Alexander Todorov 2011-03-15 15:39:42 UTC
Created attachment 485526 [details]
program.log

Comment 2 Alexander Todorov 2011-03-15 15:39:50 UTC
Created attachment 485527 [details]
storage.log

Comment 3 Alexander Todorov 2011-03-15 15:39:59 UTC
Created attachment 485528 [details]
syslog

Comment 4 David Lehman 2011-03-15 17:36:02 UTC

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