<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/1.0.1">
</HEAD>
<BODY>
Just wanted to cue in here and say that I experience a similar situation on an UPGRADE. Bob Meyer and I worked on it and eventually found:
<BR>
1. BIOS (Motherboard NOT scsi) played a vital role in handing the boot process to scsi over ide
<BR>
2. On the upgrade, the necessary init link/file was not passed to the boot strap.
<BR>
This was determined through various steps but the most noticeable was when (after suspecting hardware failure of course :)) was on a fresh install everything worked and booted fine. There are only a handful of scsi adapter manufacturers (less than ide for sure), it's not inconceivable to think they put all the adapter drivers on the distros.
<BR>
On Wed, 2002-05-22 at 17:55, Todd Wirth wrote:
<BLOCKQUOTE>
<FONT COLOR="#0000ff"><FONT SIZE="2"><I>On the subject of RedHat kernel having default support for a every SCSI adapter I disagree. We have a Dell server running RedHat 7.2, although I wasn't involved in the upgrade to a newer kernel (Dell provided), I know what happened through various emails between Dell and our other IT guy. They tried 2 stock RedHat kernels that did not work with our SCSI adapter, until finally the 3rd one did the trick. I was about to take over the project and just compile a kernel, but that would have voided our support w/ Dell & RedHat.</FONT></FONT></I>
<BR>
<FONT COLOR="#737373"><FONT SIZE="3"><I> </FONT></FONT></I>
<BR>
<FONT COLOR="#0000ff"><FONT SIZE="2"><I>I'm not too sure about the hardware as this server (besides a Xeon) is in a remote office, but I did see the email traffic, and you could tell the Dell guys were stumped. ;)</FONT></FONT></I>
<BR>
<FONT COLOR="#737373"><FONT SIZE="3"><I> </FONT></FONT></I>
<BR>
<FONT COLOR="#0000ff"><FONT SIZE="2"><I>-- Todd</FONT></FONT></I>
<BR>
<BR>
</BLOCKQUOTE>
</BODY>
</HTML>