Solved

ESX will not attempt to boot after enabling FC HBA card; stops at: " LSI logic pci boot rom sucessfully installed!"

Posted on 2008-10-03
2
503 Views
Last Modified: 2013-11-14
I installed ESX 3.5u2 and ran things locally just fine. Then, to get my SAN up, I noticed that ESX (GUI) didn't pick up the HBAs on the local host (server). So i rebooted and discovered that the card's config menu had it disabled on boot. Turned that to on.

Now the card's LEDs turned from light blue to dark blue (so it's communicating at least) and I get the following message before ESX is even loaded:

LSI logic pci boot rom successfully installed! It will hang here indefinitely. I assume it is trying to do a network boot from SAN or something to that effect. I perused the config again looking to turn of the boot feature but it lists the PXE boot as the only option (explicitly tells you that there are no other options after pressing <space> to change).

This is critical to a weekend project. Much appreciated.

Carl
0
Comment
Question by:minnefornian
2 Comments
 
LVL 7

Expert Comment

by:BogdanSUA
ID: 22654811
Did you just enable the card, or did you enable the FC card's BIOS.  Doing the latter is for Boot from SAN.

What kind of hardware are you using?
0
 

Accepted Solution

by:
minnefornian earned 0 total points
ID: 22687909
Incompatible LSI card with VMWare. Switch to Qlogic and worked as advertised. Thx.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question