Link to home
Start Free TrialLog in
Avatar of Armitage318
Armitage318

asked on

VM Windows 2008 very slow on boot

Hi, I have a VM (VMware) Windows Server 2008 R2 Standard that become very slow during boot process ( > 15 minutes).
This VM has 500 GB disks (90% full), 16 GB RAM and 8 vCPU.
How can I determine root cause of this issue? Thank you!
Avatar of arnold
arnold
Flag of United States of America image

Do you have VCSA installed?
What functions does the system serve?
When booting while looking at the console, what is it processing

500gb 90% full
Based on your CPU allocation, is this an SQL or exchange VM? Allocate more ram if you can.

Check resource prioritization?
If you watch the system boot from the console where is it spending the most amount of time?  Is it sitting on the Windows logo screen for 14 minutes or is it during one of the Windows message screens like "Windows is Getting Ready"?  If it's on one of the Windows message screens I would take a look at your event logs to see if any services are having a timeout issue trying to get started.
Avatar of Armitage318
Armitage318

ASKER

Hi @arnold, yes I do have VCSA. This server is a little web/mail/SQL shared hosting server with few domains (about 30).
What do you mean exactly with "check resource priorization"?

@aaron: I see "Microsoft corporation" and loading bar. I will check log and let you know.
Thank you
within VCSA you can prioritize VMs to make them higher/lower priority on CPU/Memory/DISK IO etc.

mail and sql are not little memory consumers.

Your VM might benefit from additional memory

you have allocated 8vcpu's with 16Gb of RAM.

how big are the sql DBs that are in use, cumulative?
have you limited sql server to only use 10GB
My guess here is misconfigured DNS. A Windows box that cannot reach a DNS server tends to take about 15mins to boot.
Hi,

I'm sure you're aware of this, but on January 14, 2020, support for Windows Server 2008 and 2008 R2 will end.
Might be worth while to focus on migrating your workloads to newer OS version insted, which might then end up solving your issue also.

Thanks
it was a storage issue
ASKER CERTIFIED SOLUTION
Avatar of Armitage318
Armitage318

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
it was a storage issue (MD3800, with corrupted volume)