Link to home
Start Free TrialLog in
Avatar of VDGinfo
VDGinfo

asked on

VMware ESX 4 VM will not post

HELP URGENT

I`ve been having problems with backupexec backing up my exchange servers for the last 2 weeks and so as this is the evening I tried rebooting my exchange servers to see if that could have something to do with it.

To my surprise my exchange mailbox server will now not boot. They are stuck on the VMware bios screen with the status bar half way. I have no idea what to do as I have searched on the net and found nothing.

I`m  a little stressed as these servers HAVE TO be in prod tomorrow.

Here is the info:
2 hosts running vmware esx4
2 vms running win2k8R2 exchange 2010 hub/cas - booting fine
2 vms running win2k8R2 exchange 2010 mailbox - both will not boot.

Any help or questions that can be provided will be greatly appreciated.
Avatar of bepsoccer1
bepsoccer1
Flag of United States of America image

Have you hard powered off yet and tried booting again?
Avatar of VDGinfo
VDGinfo

ASKER

Thank you for the response. Yes multiple times.
Do you have anything in your logs?  How many vCPUs do the VMs have?  If you have multiple, try configure to just 1 vCPU to help troubleshoot.
Where are the VMs (vmdks) stored? Are they local to the host or on shared storage?
ASKER CERTIFIED SOLUTION
Avatar of Adrian Cantrill
Adrian Cantrill
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of VDGinfo

ASKER

I don't see anything in the logs, it doesn't seem to be erroring out, just hangs...

The two VMs have 4 vCPUs each. I reduced them down to 1 each but unfortunately it is hanging at the same place..

Thank you for your response.
Avatar of VDGinfo

ASKER

I have not tried power cycling the hosts.. I will try that now and report back..

The storage for each vm is on a HP EVA and is setup as a LUN to each VM so this means I cannot migrate the VMs to other hosts.
Ok, a restart of both hosts would be my next step. It may not fix, but its something which removes a lot of problems in one quick and dirty step.
Avatar of VDGinfo

ASKER

Cool, they are rebooting right now.
Avatar of VDGinfo

ASKER

Rebooting the servers allowed them to provide me with a valid error.. It turns out their was one disk on each server that had been deleted from the EVA and not removed from the VMs. By removing this disk both VMs now boot.

Thank you so much for your help!!!
Great stuff, glad i could help in some small way.

At least you're ready for production :)
Avatar of VDGinfo

ASKER

Yes exactly.. stress has gone down :)