VMware Cloud Community
rhummels
Contributor
Contributor

ESX 3.5 U1 installation hang at Loading qla2300_707_vmw driver

Hi!

I'm trying to install a new ESX host but can't get pass "Loading block driver - Loading qla2300_707_vmw driver". The server is a brand new IBM x3850 M2 with 2x dualport 4Mbit HBA. From what I've read other places, this could be related to my SAN configuration. Last week I installed an 100% identical server, but at another location. This sever is located in another contry, so I can't just pop out to physically check the server. Any suggestions what to look for?

Regards,

R

Tags (4)
Reply
0 Kudos
9 Replies
rubensluque
Enthusiast
Enthusiast

You have to disconnect the fibre cables before installing the ESX Server. Did you try it ?

Reply
0 Kudos
Rubeck
Virtuoso
Virtuoso

Reply
0 Kudos
rhummels
Contributor
Contributor

No the fibercables is connected. I'll try to find someone who can disconnect them, and try once more :smileygrin:

R

Reply
0 Kudos
oreeh
Immortal
Immortal

If this doesn't help try and remove the HBAs while installing ESX and plug them back in afterwards.

This helped me a few times in the past.

Reply
0 Kudos
rubensluque
Enthusiast
Enthusiast

Just to complement my answer. See what the VMware recommends bellow:

"CAUTION VMware recommends that you disconnect the SAN before you begin the

ESX Server install process. There is one exception: If you are booting from a SAN, then

only the system LUN should be presented to the ESX Server. All other LUNs should not

be presented to the ESX Server during the install process".

Installation Guide, page 83 - http://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_installation_guide.pdf

Reply
0 Kudos
Texiwill
Leadership
Leadership

Hello,

If the install is hanging on loading the driver, then its not possible to remove the device yet. I would verify that your HBA has the proper BIOS version and is on the HCL. THese are the general cause to the hangs during install.

At this stage of the boot into the install the # of LUNs presented could be an issue. But not if they are less than 128 LUNs.

Did you run diagnostics on the system for at least 24 hours, memory diags for at least 24 hours? Verify the BIOS versions? Verify the BIOS settings are compatible with VMware ESX?


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
Reply
0 Kudos
glynnd1
Expert
Expert

I recall when first installing 3.0.x thinking the same thing, only to find out that it did eventually carry on by it's self - I was very impatient. I persume that it is attempting to access the possible LUNs that cound be connected to it.

Reply
0 Kudos
Schorschi
Expert
Expert

Also, if the HBA is having issues loggging into the fabric you can have issues.

Reply
0 Kudos
rhummels
Contributor
Contributor

Hi!

The problem was solved by disabling the fiberswitchport during installation :smileygrin: After installation was finished, we enabled it again and everyone was happy :smileygrin:

Thx to all for the help!

Regards

R

Reply
0 Kudos