RHEL qlogic failover problem

[djdb]

Hi everyone!

I have HP BL20p G3 server with no direct attached hard drives and with attached storage HP EVA8000 through 2-port qlogic HBAs (qlogic 2312). SAN configuration is in attached image.

http://img165.imageshack.us/img165/9819/evaky3.jpg

I have try to install RHEL 4 AS update 4. When I starts "Disk Druid" (text mode) i've seen 8 mirrored partitions: sda, sdb, sdc, sdd, sde, sdf, sdg, sdh instead of single sda.

I have try to install to sda. After installation complete and before reboot i have made next steps:
go to the second sonsole
# chroot /mnt/sysimage
setup eth0, adding default route and config resolv.conf
# cd /root
# wget http://.../hp_qla2x00-2006-10-11.tar.gz
# tar -xzvf hp_qla2x00-2006-10-11.tar.gz
# cd hp_qla2x00-2006-10-11.tar.gz
# ./set_parms2.26 to "EVA/XP/MSA failover" (as i understand - it creates /etc/hp_qla2x00.conf)
# ./INSTALL (it compiles driver, makes initrd and patch /etc/modprobe.conf) for my 2.6.9-42.EL kernel
then i do it manually for my 2.6.9-42.ELsmp kernerl
# cd /opt/hp/src/hp_qla2x00src
# ./build_driver.rh -m 2.6.9-42.ELsmp
# ./make_initrd 2.6.9-42.ELsmp

and then reboot

...

after reboot a have only seen "Attemting Boot From Hard Drive (c:)" :(

Many advise on this forum tolds to disconnet redundand paths from server with aim to make one single SAN connection from EVA to HBA, but i can't do this on production SAN.

Can anybody helps me to resolve problem?

[Ulf Zimmermann]

During the BIOS do you see the qlogic firmware detecting your LUN on the SAN? Is the firmware set to enable?

[Andrew Cowan]

Are your SAN people using LUN masking, if so are you SURE that they have plugged you into the right switch and have enabled both your World Wide Names?

[djdb]

2 Ulf Zimmermann:
Yes I do. It works fine and install CD can find partitions, but duplicates (sda, sdb, sdc... , sdh)

2 Andrew Cowan:
LUN maskink isn't using.

...
Also, i have olready made Debian i386 (testing cd) installation on this system (also download firmware and drivers after installation complete and before reboot, made mkinitrd with hooks ... etc.), and I hasn't problems with boot.

I think my problem in GRUB. It isn't property installed, and as a result - system can't find executive data in MBR on /dev/sda. May be I mistake.

[Andrew Cowan]

Then mkinitrd is the answer

[djdb]

As I wrote before, I have made ./build_driver.rh and ./make_initrd

for each 2.6.9-42.EL and 2.6.9-42.ELsmp kernels and has no result.