?
Solved

Esxi physical host will not come back up after reboot......

Posted on 2013-01-31
7
Medium Priority
?
990 Views
Last Modified: 2013-02-05
hi guys

so recently I was on the phone to Vmware. They asked me to Vmotion all of the VM's from this particular host, onto the other three we have in the cluster. I did. They then asked me to reboot the Esxi physical host. I did. But then...it never came back up. I.e. when I look at the screen, it is constantly going through a loop. It goes through the startup stages, but then it gets stuck in this loop which I've attached a photo.

It's trying to use PXE at boot? I've checked in BIOS and the primary boot is CD room. Last is PXE.

I ran harware diagnostics and sent to IBM (makers of our hosts/SAN environment). They said there's nothing wrong there.

So they asked me to do firmware updates. I've run them, but it takes forever.

However, in the morning I'm hoping it's come back up.

Otherwise, what's the next step? Re-install the OS? If so, do you have any steps I can go through?

The make model of this host is X3650 M3. We're using Vmware Esxi 4.1.0.

Thanks for your help
Yash

Many thanks
Yash
20130130-122945.jpg
0
Comment
Question by:Yashy
  • 4
  • 3
7 Comments
 
LVL 124
ID: 38841970
If it's trying to PXE BOOT, it's trying to BOOT from the Network, because

1. BIOS settings have been changed to BOOT from network.

or

2. RAID array, storage controller, ESXi installation has become corrupted.

Check storage subsystem, and reinstall ESXi.
0
 
LVL 1

Author Comment

by:Yashy
ID: 38841989
I went into Bios. Booting from CD first. Im sure thats what i saw. I have left it runniig updates. one of which consists of the sas controller.

Is there much to installing the esxi host again? And adding back to cluster?
0
 
LVL 124
ID: 38842017
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
LVL 1

Author Comment

by:Yashy
ID: 38843241
Fantastic thank you man. I'm assuming it's the same principle for 4.1?

Also, I applied the updates. When I reboot the Esxi host, the startup screen is really fast but I caught a glimpse of it saying:

CD drive: Boot Failed
Hard Disk 0: Boot Failed.

And IBM looked at the error logs and said there's no hardware faults.

Re-install Esxi 4.1? Or Diagnose the Boot failure you think?
0
 
LVL 124
ID: 38843248
exactly the same for 4.1 as 5.1.

Hard Disk 0: Boot Failed, possibly hard drive issues?

otherwise re-install ESXi 4.1.
0
 
LVL 1

Author Comment

by:Yashy
ID: 38843577
All resolved.

You wouldn't believe this. After a reboot, the BIOS settings somehow decided to 'forget' two original settings. One was the actual LSA controller settings which looks at which drives to boot from. It was set to 'none'. Changed that to virtual drive 0.

Secondly, in the boot menu, there was what's called a 'Legacy' option missing. Added this to the boot option and put it just below the CD rom drive option.

Works like a charm now.

Unbelievable! All of this because we rebooted it and it forgot settings. Strange right?
0
 
LVL 124

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 38843602
weird things do happen, check the CMOS Battery!

replace if older than 3 years.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

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

If your vDisk VHD file gets deleted from the image store accidentally or on purpose, you won't be able to remove the vDisk from the PVS console. There is a known workaround that is solid.
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.
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…
Suggested Courses

749 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