|
This is a problem for us as well. The most reliable
solution I've been given (but haven't had time to try) is to bust open your
initrd and change the entry for your HBA to "ignore" in the /modules/pcitable
file.
There are a number of options that are SUPPOSED to work,
like latefcload, but it hasn't worked for us.
From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx]
On Behalf Of Robbie Pike
Sent: Friday, June 01, 2007 10:28 AM To: kickstart-list@xxxxxxxxxx Subject: Kickstart issue I have an issue re-kickstarting RHEL 4 servers when I
need to redploy them. I have HP Linux servers that the CCISS raid controller
(came out of Compaq). The disk presented by this raid controller should up as
/dev/cciss/c#d#. If I have the systems connected to SAN storage then they show
up as /dev/sd[a, b,c, etc.]. If I try to kickstart a HP server that has SAN
devices already zoned to it the kickstart process fails with “Input/output error
during write on /dev/sda” error. Does anyone know what could be the
problem and how to address. I’m would like to eleminate having to disconnecting
the fiber connections or unzoning luns. Here’s my partition section of the
ks.cfg zerombr yes clearpart --drives=cciss/c0d0,cciss/c0d1 --all part swap --start=1 --end=800 --ondisk cciss/c0d0 --asprimary part / --fstype ext3 --start=801 --end=1057 --ondisk cciss/c0d0 --asprimary part pv.00 --size 1 --grow --asprimary --ondisk cciss/c0d0 volgroup vg00 pv.00 logvol /usr --vgname=vg00 --size=2024 --name=lvol1 logvol /var --vgname=vg00 --size=4096 --name=lvol2 logvol /home --vgname=vg00 --size=1024 --name=lvol3 logvol /opt --vgname=vg00 --size=4096 --name=lvol4
Thanks for any
help, |
