[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Install to local drive instead of a fibre attached SAN

Also, you can change the kickstart file's disk order I believe.
we use cciss so even if a san is attached, it goes to sda (local storage) per the kickstart file.
but I had to change the bootloader order via:
bootloader --location=mbr --driveorder=cciss/c0d0,sda

might work on the actual partitioning directive. Haven't tried it.

Stephen Mah wrote:
I did a quick google. Try passing "nostorage"


Beamon, John wrote:
We've had a few isolated incidents of kickstart installs assigning "/dev/sda" to a fibre attached SAN volume instead of the internal scsi disks. My environment is RHEL 4U4 on mixed 32- and 64-bit Intel hardware. Is there a way to script in %pre the exclusion of drives attached by an HBA? I've rewritten /tmp/modprobe.conf with "scsi_hostadapterN qla2300" as both first and last entry in the scsi hosts, but the lettering of the drive doesn't change. It appears to be set by the kernel image during boot. Can that be re-ordered? The closest thing I've found is that I can 'rmmod qla2300' in %pre, but the better long-term plan would be to configure internal or external by choice so we have the option of installing to the SAN later.


Kickstart-list mailing list
Kickstart-list redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]