VMware ESX - Guest Windows servers crash - NTFS corruption

Over the past week or so, three of my virtual machines in VMware have been crashing.  All VM's are Win2k3 Server.  I have three ESX hosts (4.0 U2) connected to an EMC NX4 SAN.  The datastores are NFS.  The VM's are all on different hosts.  I will notice that the servers randomly restart and come back up running chkdsk or will come up and have NTFS errors (event ID 55):

Description: The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume "Drive_letter:"

I have run chkdsk multiple times, but continue to have the same problems.  All three problem servers are very active servers.  Two SQL and one Exchange.  Most of the time when the servers crash, data becomes corrupt or gets lost.  Any ideas what would be causing the problems?  Other VM's seem to be fine.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

did you try steps in this:
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
This seems like an issue with the underlying datastore storage presented to ESX hosts.

e.g. your NFS datastore on the EMC NX4 SAN.

Are you using Jumbo Frames to connect to the EMC SAN, make sure that jumbo frames if enabled are enabled on the ESX hosts, networking switches and EMC SAN.

Also check with the Vendor for specific NFS pararmeters than can be used to "tune" each ESX host, in the advanced NFS global settings.

You could try moving the VMs back to local storage and check if the problem remains.

Check datastore disk and write latency.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RickAstleyAuthor Commented:
Looks like it ended up being a problem with the storage.  The latency for writes was extremely high.  Moving VM's off to another SAN seems to have solved the problem.

VMware logs showed that ESX was briefly losing connectivity to the NFS shares.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.