I am having trouble with our Mail Server running on a VM under VMWare Server 2.
- For some reason, I was not able to log into VMware Infrastructure Web Access. I noticed that the VMware Host Agent was not running, and I tried restarting it but it kept stopping after I tried logging in.
- Windows Application Event Log reported:
Log Name: Application
Source: vmauthd
Date: 6/16/2011 6:51:04 PM
Event ID: 100
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: -------
Description:
Cannot connect to VMX: -----------------.vmx
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="vmauthd" />
<EventID Qualifiers="0">100</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-06-17T01:51:04.000000000Z" />
<EventRecordID>8015</EventRecordID>
<Channel>Application</Channel>
<Computer>---------</Computer>
<Security />
</System>
<EventData>
<Data>Cannot connect to VMX: ------------.vmx
</Data>
</EventData>
</Event>
In the past, when a virtual machine has problems, I've had some success using VMWare Converter on the afflicted VM - however in this case, even that is failing.
I found the following in one of the logs:
[#6] [2011-06-16 14:27:16.563 'App' 3152 verbose] [,0] DISKLIB-SPARSE: "----------000001-s011.vmdk" : failed to open (36872): Underlying file system does not support files that large.
[#6] [2011-06-16 14:27:16.564 'App' 3152 verbose] [,0] DISKLIB-LINK : "---------000001.vmdk" : failed to open (The file is too large).
[#6] [2011-06-16 14:27:16.564 'App' 3152 verbose] [,0] DISKLIB-CHAIN : "---------000001-.vmdk" : failed to open (The file is too large).
[#6] [2011-06-16 14:27:16.564 'App' 3152 verbose] [,0] DISKLIB-LIB : Failed to open ----------000001.vmdk' with flags 0xe (The file is too large)
checking the size of the file ending 000001-s011.vmdk reveals that the .vmdk has grown to a size of over 13GB!
The VM was set to be split into multiple files, and all other files in the folder remain at 1.99 GB (2,146,762,752 bytes) or less in size..
Based on the other files in the same folder, I suspect a snapshot was initiated back in early April. I am not sure why this 000001-s011.vmdk file has grown out of control since then, and even less sure of how to proceed in fixing this issue.
If anyone has any suggestions for recovery at this point, I'd appreciate your advice..