 | | | Problems with SCSI support on Red Hat Work Station 3 Update 1 | Problems with SCSI support on Red Hat Work Station 3 Update 1 2004-02-03 - By tomncc3
Back
Stuart -
Unfortunately, I reverted the box I installed RHWS 3 on back to Fedora, since that flavor of RH could detect the SCSI adapter on boot. I understand the suggestions you mentioned below, and have used variants of them on other occasions, such as to enable RHAS 2.1 to run on a SAN, from an HP blade.
I will save your post so when I try RHWS on the server, again, I 'll see what happens. Thank you very much for your tech tips, I 'll tuck them away for a later date.
This is not directed at you, but my main concern is /why/ would RH remove these modules from a standard installation? Certainly a lot of people are going to upgrade from Fedora and RH9 to RHWS 3, whom are running slightly older, but well known hardware, just to encounter issues. You should not have to take a step back on the installation when upgrading to an enterprise version of the operating system. I realize that Red Hat is striving for stability, and perhaps the older drivers could cause problems, as a guess, but the adapter I am using is pretty well known and I feel it should have its module available during installation. If it were an obscure adapter, that fell into the realm of the Beta Max VCR or something like that, I could understand and drive on.
The SCSI adapter I am trying to use, I usually configure as a three disk RAID5 set for my root area, not as storage after the fact of the installation. This is why I want it available on installation. I really like Red Hat Linux, I think it 's a great operating system, and I am not trying to bash them, but I think they should at least give people the option of having the older modules around, in case they would like to use them during system installations.
Thanks,
TK
Stuart Sears wrote:
> On Sunday 01 February 2004 04:55, tomncc3 wrote:
>
> >How do you get SCSI support with Red Hat Work Station 3? This seems rather
> > "odd " that the Enterprise version of the operating system couldn 't handle a
> >fairly standard SCSI controller, where the other "free " versions could. I
> >am looking through the docs to see what I might have done wrong, but I
> >can 't see anything. Did RH drop support for this controller for the
> >Enterprise version?
>
> no, but they have shifted a lot of kernel modules into a 'kernel-unsupported '
> rpm. just install the one that matches your kernel
Can you "modprobe " the device to get the driver to load? If so, and you
want the card active at bootup, you MUST make sure the initrd image has
the driver installed. Building a kernel (or installing one) will not
force the driver to be loaded into the initrd image. To do this, two
conditions must be met:
1) There must be an "alias scsi_hostadapter driver-name " in
the /etc/modules.conf file
2a) You must have a filesystem from the SCSI drive in question
in /etc/fstab that must be mounted at boot
OR
2b) You must tell mkinitrd to force-load the driver by using the
"--with=module-name " option.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN " >
<HTML > <HEAD >
<META http-equiv=Content-Type content= "text/html; charset=iso-8859-1 " >
<META content= "MSHTML 6.00.2800.1276 " name=GENERATOR >
<STYLE > </STYLE >
</HEAD >
<BODY bgColor=#ffffff >
<DIV > <FONT face=Arial size=2 >Stuart - </FONT > </DIV >
<DIV > <FONT face=Arial size=2 > </FONT > </DIV >
<DIV > <FONT face=Arial size=2 >Unfortunately, I reverted the box I installed RHWS
3 on back to Fedora, since that flavor of RH could detect the SCSI
adapter on boot. I understand the suggestions you mentioned below, and
have used variants of them on other occasions, such as to enable RHAS 2.1 to run
on a SAN, from an HP blade. </FONT > </DIV >
<DIV > <FONT face=Arial size=2 > </FONT > </DIV >
<DIV > <FONT face=Arial size=2 >I will save your post so when I try RHWS on the
server, again, I 'll see what happens. Thank you very much for your
tech tips, I 'll tuck them away for a later date. </FONT > </DIV >
<DIV > <FONT face=Arial size=2 > </FONT > </DIV >
<DIV > <FONT face=Arial size=2 >This is not directed at you, but my main concern is
/why/ would RH remove these modules from a standard installation?
Certainly a lot of people are going to upgrade from Fedora and RH9 to RHWS 3,
whom are running slightly older, but well known hardware, just to encounter
issues. You should not have to take a step back on the installation when
upgrading to an enterprise version of the operating system. I realize that
Red Hat is striving for stability, and perhaps the older drivers could cause
problems, as a guess, but the adapter I am using is pretty well known and I feel
it should have its module available during installation. If it were an
obscure adapter, that fell into the realm of the Beta Max VCR or something like
that, I could understand and drive on. </FONT > </DIV >
<DIV > <FONT face=Arial size=2 > </FONT > </DIV >
<DIV > <FONT face=Arial size=2 >The SCSI adapter I am trying to use, I usually
configure as a three disk RAID5 set for my root area, not as storage after the
fact of the installation. This is why I want it available on
installation. I really like Red Hat Linux, I think it 's a great operating
system, and I am not trying to bash them, but I think they should at least give
people the option of having the older modules around, in case they would
like to use them during system installations. </FONT > </DIV >
<DIV > <FONT face=Arial size=2 > </FONT > </DIV >
<DIV > <FONT face=Arial size=2 >Thanks, </FONT > </DIV >
<DIV > <FONT face=Arial size=2 > </FONT > </DIV >
<DIV > <FONT face=Arial size=2 >TK </FONT > </DIV >
<DIV > <FONT face=Arial size=2 > <FONT face=Arial size=2 > </FONT > </FONT > </DIV >
<DIV > <FONT face=Arial size=2 > <FONT face=Arial size=2 > </FONT > </FONT > </DIV >
<DIV > <FONT face=Arial size=2 > <FONT face= "Times New Roman " size=3 >Stuart Sears
wrote: <BR >> On Sunday 01 February 2004 04:55, tomncc3 wrote: <BR >>
<BR >>>How do you get SCSI support with Red Hat Work Station 3? This
seems rather <BR >>> "odd " that the Enterprise version of the operating
system couldn 't handle a <BR >>>fairly standard SCSI controller, where the
other "free " versions could. I <BR >>>am looking through the docs to
see what I might have done wrong, but I <BR >>>can 't see anything. Did
RH drop support for this controller for the <BR >>>Enterprise
version? <BR >> <BR >> no, but they have shifted a lot of kernel modules into
a 'kernel-unsupported ' <BR >> rpm. just install the one that matches your
kernel <BR > <BR >Can you "modprobe " the device to get the driver to load? If
so, and you <BR >want the card active at bootup, you MUST make sure the initrd
image has <BR >the driver installed. Building a kernel (or installing one)
will not <BR >force the driver to be loaded into the initrd image. To do
this, two <BR >conditions must be met: <BR > <BR >1) There must be an "alias
scsi_hostadapter driver-name " in <BR >the /etc/modules.conf file <BR > <BR >2a) You
must have a filesystem from the SCSI drive in question <BR >in /etc/fstab that
must be mounted at boot <BR > <BR >OR <BR > <BR >2b) You must tell mkinitrd to
force-load the driver by using the <BR > "--with=module-name "
option. </FONT > <BR > </DIV > </FONT > </BODY > </HTML >
|
|
|