Bug 428135

Summary:	Installation hangs with two RAID0 volumes in system
Product:	Red Hat Enterprise Linux 5	Reporter:	Adam Cetnerowski <adam.cetnerowski>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.1	CC:	Jacek.Danecki, rpacheco
Target Milestone:	rc
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-12-10 19:19:55 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 Adam Cetnerowski 2008-01-09 13:58:47 UTC

Setup two (2 or 3 disk) RAID0 volumes on an ICH8DO system, using the ISW OROM. 
RHEL5 x86_64 install from DVD started (used linux all-generic-ide to get the
PATA DVD to work with the Marvell controller).  After a few screens in the
graphical setup, the install hung. In the F4 console there were messages about
dm-multipath and about RAID5 and RAID6, which seems strange.  The system was
then corrupted and the integrated graphics driver stopped working correctly.

Comment 1 Joel Andres Granados 2008-06-12 12:34:08 UTC

does installing with nodmraid help?

Comment 2 Chris Lumens 2008-12-10 19:19:55 UTC

The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present.  Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current RHEL release, or that there is no longer any interest in tracking the problem.

Setting status to "CLOSED: INSUFFICIENT_DATA".  If you still experience this problem after updating to our latest RHEL release and can provide the information previously requested, please feel free to reopen the bug report.

There are, in addition, a wide variety of dmraid-related bugs being reported and fixed in 5.3 right now.  This is a fairly high churn region of code at the moment.  If you could please test with the latest snapshot, that would be greatly appreciated.  Thanks.

Thank you in advance.

Comment 3 Jacek Danecki 2008-12-12 12:39:55 UTC

(In reply to comment #2)
> The information we've requested above is required in order to review this
> problem report further and diagnose or fix the issue if it is still present. 
> Since it has been thirty days or more since we first requested additional
> information, we're assuming the problem is either no longer present in the
> current RHEL release, or that there is no longer any interest in tracking the
> problem.
> 
> Setting status to "CLOSED: INSUFFICIENT_DATA".  If you still experience this
> problem after updating to our latest RHEL release and can provide the
> information previously requested, please feel free to reopen the bug report.
> 
> There are, in addition, a wide variety of dmraid-related bugs being reported
> and fixed in 5.3 right now.  This is a fairly high churn region of code at the
> moment.  If you could please test with the latest snapshot, that would be
> greatly appreciated.  Thanks.
> 
> Thank you in advance.

We can't reproduce this bug on snap5.