- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
boot from san not finding LUN
I am trying to get one of my VI3 servers to boot from SAN. The san is an IBM FastT600 (or DS4300).
I have created one 15GB lun and masked it off in its own storage partition so only the wwn of the VI3 servers HBA can access it. The LUN id of this LUN has been set to zero. The owning storage processor of this LUN is SP A.
The HBA (which is a QLogic 2340) has had the BIOS upgraded to 1.50 which is the latest on the qlogic site. It has the BIOS and Boot Selection options enabled.
I have selected the WWN of the storage processor A and the submenu shows that LUN 0 can be seen. I have selected LUN 0 so that the BIOS shows SP A LUN 0 as the boot path & LUN.
I have also verified that the LUN which the HBA bios can see is the correct LUN by changing the LUN id to a different number and seeing if the HBA picks up the new id when a device scan is performed from the HBA. It does so this proves I am looking at the correct LUN.
The settings have been saved to the BIOS and upon reboot the HBA banner shows that it is looking at LUN 0.
When I come to install VI3 (via graphical mode) the blue screen hangs on the QLA driver for around 2-3 minutes. I get a message saying that no storage has been found and it gives me an option to manually select one. I choose the QLA driver (out of a list of the network driver or the qlogic driver) and the install progresses to the point of loading up the proper GUI.
After accepting the licence agreement and selecting keyboard and mouse settings I get a message appearing on the screen saying that no storage has been found at which time the server restarts.
I've been over and over this and I can't see what I am doing wrong. Does anybody have any ideas??