Bug 206628

Summary: Anaconda crash after attmepting to write to dmraid device
Product: [Fedora] Fedora Reporter: Andre Grove <andre.grove>
Component: anacondaAssignee: Peter Jones <pjones>
Status: CLOSED DUPLICATE QA Contact: Mike McLean <mikem>
Severity: high Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-27 22:13:52 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:
Attachments:
Description Flags
Anaconda Crash Dump none

Description Andre Grove 2006-09-15 12:43:13 UTC 
Description of problem: Anaconda crashes on FC8test3-i386  install


Version-Release number of selected component (if applicable):


How reproducible: try to install on a RAID0 array build by an Intel ICH7 controller


Steps to Reproduce:
1. Boot from DVD iso to try install on Asus P5WD2-E Premium BIOS Revision 604
motherboard, using Intel ICH7 Raid Controller V5.1.2.1002 on RAID0 array
comprised of 2x Samsung SP2405C drives
2. raid array already has 2 partitions but yas 10Gig free space
3. install on free space either using automatic partitioning or custom layout
  
Actual results: Crash warning 


Expected results: Continuation of install


Additional info:
Comment 1 Andre Grove 2006-09-15 12:43:14 UTC 
Created attachment 136351 [details]
Anaconda Crash Dump
Comment 2 Andre Grove 2006-09-15 15:24:21 UTC 
(In reply to comment #1)
> Created an attachment (id=136351) [edit]
> Anaconda Crah Dump
> 

i've made a mistake on point 1 of the replication procedure:

1) Do an FTP install on Asus P5WD2-E Premium BIOS Revision 604
motherboard, using Intel ICH7 Raid Controller V5.1.2.1002 on RAID0 array
comprised of 2x Samsung SP2405C drives
Comment 3 Peter Jones 2006-09-27 22:13:52 UTC 

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