Things to look out for:
1) Be sure to use the latest version of boot BIOS on your adapters, and follow the instructions included in the readme file that comes with the driver version for setting up the boot BIOS correctly.
2) When using more than one HBA in the server, set up both HBA's for boot, and make sure your path-failover software supports it. Doing so will allow you to survive an HBA failure.
3) Make sure the system BIOS is not trying to boot from any internal disks. You can verify this by disabling the internal SCSI adapters in the server, and re-trying the boot.
4) Make sure the HBA topology setting is correct for your environment (FCAL or fabric)
5) Make sure you use "single initiator zoning" in your fabric to the port where your boot drive is located. In other words, simply zone the HBA you are booting from to the storage port where the boot LUN is ported (do this for each HBA in the server). In my experience, If you have more than one target port in the zone for the boot HBA, the BIOS may get confused during boot, and you will experience the exact same symptom you are getting.
6) Get the latest tech-tips from Microsoft on SAN booting technet.microsoft.com and search for SAN BOOT.
Dig Deeper on SAN technology and arrays
Related Q&A from Christopher Poelker
SAN expert Chris Poelker discusses how to change the size of a LUN in a Microsoft cluster server environment. Continue Reading
SAN expert Chris Poelker compares connecting a SAN with wavelength cabling and dark fiber and discusses the pros and cons of each. Continue Reading
Storage expert Chris Poelker outlines WWN basics in order to answer the question: "Why do HBAs in a SAN have same base?" Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.