My environment:
Host:
HP z800 with internal SATA drives. No iSCSI or fiber or anything fancy.
ESXi 5.1.0,799733
Guests:
Windows Servers:
2008R2 (SBS)
2012
2012R2
Creating snapshots on the 2008r2 and the 2012 servers has always worked without any issues. However, whenever I create snapshots of the 2012r2 servers I always get the following error messages:
Log Name: System
Source: Ntfs
Date: 23/10/2014 12:26:19 PM
Event ID: 137
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: host.domain.local
Description:
The default transaction resource manager on volume \\?\Volume{4d63c1a0-5a35-11e4-80c8-000c293e51b6} encountered a non-retryable error and could not start. The data contains the error code.
Log Name: System
Source: Microsoft-Windows-Ntfs
Date: 23/10/2014 12:26:20 PM
Event ID: 140
Task Category: None
Level: Warning
Keywords: (8)
User: SYSTEM
Computer: host.domain.local
Description:
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{4d63c1a0-5a35-11e4-80c8-000c293e51b6}, DeviceName: \Device\HarddiskVolume4.
(The specified request is not a valid operation for the target device.)
I have found the following VMware KB article that appears to cover this exact problem:
However, the article is missing some critical information on this issue... The article does not state whether these alerts indicate if there is likely to be any adverse effect on the systems in question or not. Is this a real issue, that requires remedial action, or simply the misreporting of a non-issue? Also, this article refers to two MS KB articles. However neither of these two articles are relevant to my environment.
So, do we have a problem that needs to be fixed or do we just have yet another Microsoft system log error/warning crying wolf that won't get fixed until Windows 10 Server, if we're very lucky or Fortune 100?