I got this from the URL: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/ref-guide/ch-modules.html
"During installation, Red Hat Enterprise Linux uses a limited subset of device drivers to create a stable installation environment. Although the installation program supports installation on many different types of hardware, some drivers (including those for SCSI adapters and network adapters) are not included in the installation kernel."
Which means that if the installation kernel that you are using does have the SCSI modules, you should just load the parameters during the process of loading anaconda.
When the RHEL loads, the first phase of the installation, you should use the SCSI parameters there!
If nothing happens, this means that the SCSI drivers that you need are not in the installation kernel.
I recommend using the latest release of the version of the RHEL you are trying to install.
Also check page number 106 (20-30) of the pdf that Roger posted, on SCSI options.
I hope these guidelines will help you solve the problem.
Regards,
Filipe Miranda
On 3/1/07, isplist@xxxxxxxxxxxx <
isplist@xxxxxxxxxxxx> wrote:
I'm not sure what you're telling me here.
Since this isn't something I knew how to do, I've been asking for help. The
things I know how to do now, which still don't work, are all things which have
been suggested by people who are trying to help.
From all of this, the one thing I've learned is that it does not matter what I
try to enter at the install command line, the problem is the redhat installer,
there is no way of passing this information.
I need to modify the RHEL4 install CD's initrd.img in order for anaconda to
see this at install time... and, I don't know how to do this but am reading up
on it.
> http://www.kernel.org/pub/linux/kernel/people/gregkh/lkn/lkn_pdf/ch09.pdf
Thanks, I'll check this out.
> what you have to writte is a litle modification of
> what you type in the modprobe.conf file
> maybe something like:
> scsi_mod.max_luns=256
> scsi_mod.scsi_dev_flags=INLINE:TF200:0x242
I don't have access to modprobe.conf at install time, that's the point of my
problem. I can modify it AFTER install and see all of the storage but I need
to see the storage AT install time so that I can install TO the storage.
> man, you have to test it, try and error approach maybe
I've been at trial and error for a couple of weeks now.
Mike
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
