Question

  Asked: Aug 14 2006   5:45 PM GMT
  Asked by: chucklong


SAN attach Windows servers hang on boot


Storage, Storage products and equipment, Adapters/Interfaces, Fibre channel controllers/Host bus adapters, SAN

I have several IBM X series (342,345,346) servers with Windows 2000 and 2003 loaded. I am experiencing an issue with the server hanging when booting. This only happens when I have the server connected to the SAN. I am using Qlogic 2340 HBA connecting to Cisco 9509 SAN switches. I can see the HBA log into the switch when the server hangs so I know that it's not the flogi. If I pull the fiber cable or disable the switch port the server will continue to boot with no issue. I have verified that the server bios and the HBA bios are on current levels as well as the HBA driver. This issue happens mainly when rebooting from the OS. If the server is completely powered down and then restarted the problem usually does not happen

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window

Answer Wiki (Improve, edit or add to this answer)


 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0



What Kind of SAN are you using? Also, validate with the SAN manufacturer the compatibility of all firmware and driver levels - starting with the SAN conrollers, then the QLogic cards, the qlogic drivers and load balancing drivers if you are using them. Aditionally, I would INVESTIGATE increasing the following value to 0x78 if it is still set to the default: HKEY_Local_MachineCurrentControlSetSystemServicesDiskTimeOutValue.
  • AddThis Social Bookmark Button

Browse more Questions and Answers on Storage.

Looking for relevant Storage Whitepapers? Visit the SearchStorage.com Research Library.


Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

ltimothy  |   Sep 8 2006  10:15AM GMT

The value I mentioned, 0×78, is shorthand for 0×00000078, or 120 in decimal format.

 

Psyklops  |   Sep 10 2006  9:04AM GMT

What disk array are you running? Typically this might happen if the storage array is ‘misconfigured’ i.e. the host-port personality is set to another OS type other than what is compatible for Windows.

The disk array controllers may have hung?

Check your zoning also, it may be conflicting with other initiators (or another device) on the SAN as well. Try zoning your Windows HBA port with a single port from the disk array controller port(s).

Try removing MS’s MPIO multipathing software as well and see if it will boot and present the LUN’s twice under Windows disk administrator.

Update your drivers. Try MS’s storport (or SCSIport) driver and make sure you’re Service-Packed and patched to the latest supported revision from your SAN/storage provider.