AlexSystemEngin
Contributor
Contributor

Loading ESXi installer issue " Relocating modules and starting up the kernel"

Hello Everyone,

We are trying to install ESXi 5.0 on one of our server

We are booting from CD, In "Loading ESXi Installer " screen when everything loads we get a message at the end " Relocating modules and starting up the kernel..." and it freezes here and nothing else happens..   for hours....

I have tried to restart the installation few times and i get same thing.. 

Anyone know what could be the issue?

Attached is a screenshot.

Thank You!

57 Replies
AndreTheGiant
Immortal
Immortal

Welcome to the community.

Have you first check that your system is in HCL?

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
AlexSystemEngin
Contributor
Contributor

Andre,

Yes, It is,   We had no issue with 4.0/4.1 installation...   Not sure why 5.0 has issues loading/installing

Thank You!

0 Kudos
AndreTheGiant
Immortal
Immortal

HCL could be different... Check if your system is in HCL for vSphere 5.

And be sure that all firmware are up to date.

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
ashleymilne
Enthusiast
Enthusiast

I had two white boxes that I had previously been able to install ESX 3.5, 4.0 and 4.1. I am now unable to install ESXi 5 on either of them. I believe the HCL has reduced that number of hardware devices previous HCL's supported, and this is likely your problem. Good luck.


AM

0 Kudos
cdu
Enthusiast
Enthusiast

I'm having the same error.

I'm installing to USB (no local disk) from CD, SATA controller is ICH 10, Nic is Intel 82574L/82571, FC HBA is QLE2460, they are all in HCL. CPU is i7 920/930.

Not sure what would cause it.

I ran ESXi 4.1u1 and install ESXi 5 as a VM, passthrough Intel 82571 dual port nic and qle2460 HBA to that VM and it ran fine.

0 Kudos
ashleymilne
Enthusiast
Enthusiast

Try leaving it with that message on the screen, overnight if possible. I had a similar situation trying to install ESXi 4.1 on a whitebox and it got stuck during the install on a similar but different message. I left it overnight and the following morning the install had completed.

AM

0 Kudos
cdu
Enthusiast
Enthusiast

Thanks.

I'm going to disconnect all the devices and try again tonight.

0 Kudos
martin_r
Contributor
Contributor

I had the same problem on my home 'ESX-server' (simple desktop board).

Turned out, ESX 5i changes to a different video-mode (not regular 80*40 like the older versions).

I had onboard-video set to use 1MB of memory (no need for more with simple text-mode).

Setting onboard-video to 8MB solved it for me !

0 Kudos
psychowood
Contributor
Contributor

I had onboard-video set to use 1MB of memory (no need for more with simple text-mode).

Setting onboard-video to 8MB solved it for me !

Thanks martin_r, this was exaclty what caused ESXi 5 not booting in my case. Smiley Happy

0 Kudos
AlexSystemEngin
Contributor
Contributor

What if you don't have onboard video?  that is my case right now.  Any other thoughts?

0 Kudos
DSTAVERT
Immortal
Immortal

Have you checked the HCL http://vmware.com/go/hcl Make sure that all your embedded components are on the HCL. Your servers have seperate Video Cards???? That would be very unusual for a server.

-- David -- VMware Communities Moderator
0 Kudos
martin_r
Contributor
Contributor

Since your screenshot looks like the output i got before changing the memory-size of onboard video (different font), your problem seems video-related also.

What kind of videocard are you using (make/model/memory/bus-type) ?

If Vsphere5 is using the VESA-bios to change the screen-output (don't know if that is the case, but it might be), upgrading the BIOS of the videocard might help. If you have the possibility to use another videocard (or onboard-video if that is available), that might help also (after installation the screen output looks the same as during the installation, so temporary using another videocard is problably no permanent solution).

I came to changing the memory-size of the onboard videocard after booting with the install-CD om my regular desktop (videocard: ATI HD4850 1GB), finding out that screen output was different from previous versions (and different from my ESX-machine).

0 Kudos
McBain113
Contributor
Contributor

Hi Folks

I'm having the same issue.  I'm using a Dell Studio 435MT.  I know it's not on the HCL and it worked just fine with vSphere 4.1.  So now when I run the installer I'm still getting stuck at the "Relocating Modules and Starting up the Kernel".  I have tried swapping video cards to see if that's the issue as mine does not have onboard video.  Is there anything else that anyone can suggest?  Is there a way to turn on logging in the installer so you can tell what's causing it to hang?  Help please!

Thanks,

McBain113

0 Kudos
paradox
Enthusiast
Enthusiast

Thanks so much.  That solved it for me too!

onboard video. Changed from 1MB to 8MB.

Champion

0 Kudos
yannara
Contributor
Contributor

I´m installing ESXi 5.0 on a clone desktop, with 4GB of ram install is succsessfull, with 8 GB no. With 8GB, it stucks at the same spot.

0 Kudos
kiwimedia
Contributor
Contributor

Exactly the same issue as one in screenshot. Machine boots on esxi 4.x without issue but booting with DVD or USB copy of esix 5.x displays line "Relocating modules and starting up the kernel..." then it reboots without error. I dont have an onboard video card and have reduced system from 32GB to 4GB of RAM but no change. Looking for more verbose logging to locate cause.

0 Kudos
unitrierwi1
Contributor
Contributor

I've got the same problem. Can somebody help? At my Server, there is no option to increase graphic memory, but the graphic card is onboard.

Might a bios update is a solution? My hardware is only 3 years old, it should work.

0 Kudos
LockAze
Contributor
Contributor

Same problem, onboard video card, tried another video card, but that didn't help. 8gb system..... Anyone got any info on what could cause this?

0 Kudos
lightninhopkins
Contributor
Contributor

This has happened a few times. My issue was on the Supermicro H8DMT motherboard with 48GB RAM.

I went into the BIOS and set "linux" as the operating system.