Bug 65568

Summary:	Installer on DPT RAID systems doesn't put dpt_i2o into initrd
Product:	[Retired] Red Hat Linux	Reporter:	Terry Letsche <letsche>
Component:	installer	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.3
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:	2002-06-04 15:26: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:
Embargoed:

Description Terry Letsche 2002-05-27 18:44:14 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513

Description of problem:
On systems with DPT/Adaptec RAID cards using the dpt_i2o module, the installer
correctly loads the driver, but when it comes time to make a boot disk or put
ther kernel on the hard drive, it apparently is not included in the initrd. When
the system reboots, it can't find init, which usually indicates it can't load
the root file system, which in this case is a disk partition controlled by the
DPT card.

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


How reproducible:
Always

Steps to Reproduce:
1.Install RH (upgrade existing RH 7.2 install) on dpt enabled system
2.Reboot at conclusion of install
3.
	

Actual Results:  Systems won't boot. Can't find init.

Expected Results:  Should boot up.

Additional info:

This is on RH 7.2 systems built with Tim Calloway's 7.2 boot floppies. I have
not tried it on a bare system with DPT SCSI card.

Comment 1 Scott D. Webster 2002-05-28 18:49:22 UTC

I'm having a problem where the dpt_i2o driver seems to hang on initialization
during the install.  I don't know if my problem is related to this one.

Comment 2 Michael Fulbright 2002-06-04 15:25:56 UTC

Jeremy do you know of issues with the dpt controller?

Comment 3 Jeremy Katz 2002-06-04 15:33:22 UTC

On a 7.2 system, you also need to use the update disk which has been released
for 7.2 as well.

Comment 4 Terry Letsche 2002-06-04 15:38:20 UTC

On 7.2 or 7.3? This is concerning 7.3, which has a module available to load on 
the install media already.

Comment 5 Jeremy Katz 2002-06-04 16:38:14 UTC

To quote what you said -- "This is on RH 7.2 systems built with Tim Calloway's
7.2 boot floppies. I have not tried it on a bare system with DPT SCSI card."

With 7.3, Tom says that he has done an install with the hardware which he has
and that it worked for him without any changes.

Comment 6 Terry Letsche 2002-06-04 16:57:37 UTC

To clarify: This system already has 7.2 on it. I'm trying to upgrade to 7.3.

The _original_ install on this server (7.2) used an update disk from Tom. On 
the upgrade I expected to be able to use the new installer, per Tom, with no 
problem. On reboot after install it can't find the paritions because it doesn't 
have the dpt_i2o in the initrd that is generated.

Comment 7 Jeremy Katz 2002-06-04 18:44:27 UTC

Did your /etc/modules.conf contain the scsi_hostadaptor alias for dpt_i2o?

Comment 8 Terry Letsche 2002-06-05 21:06:30 UTC

No, I run monolithic kernels on my servers. There was a 
leftover /etc/modules.conf from my initial install, and it did not have the 
dpt_iso module listed in it. If having the leftover /etc/modules.conf is the 
cause, would adding the dpt_i2o driver to it make the next install work better?

Comment 9 Jeremy Katz 2002-06-05 21:22:40 UTC

You have to have the scsi adaptor module alias listed in modules.conf, otherwise
mkinitrd has no way to find out that it needs to add the module to the initrd. 
So with it there, yes, an upgrade should work fine.