VMware Cloud Community
mwiese
Contributor
Contributor
Jump to solution

Disk D becomes readonly after snapshot

Hi gurus,

we currently encounter problems with one of our Windows 2008 64bit machines (not R2!).

The server is backuped with VDR 1.2.0.1131. At the beginning the snapshot is taken - everthings fine so far. But after the snap completed and the backup is running, disk D inside the guest system becomes readonly!

This RO flag isn't remoed anymore, even after the backup completed and the server is not usable anymore. The following errors are displayed in the logs of the windows server:

System Log:

  • The system failed to flush data to the transaction log. Corruption may occur.
  • Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc000a082 Parameters 0x000007FEFD1A722C 0x000007FEFD1A722C 0x000007FEFD1A722C 0x000007FEFD1A722C
  • {Delayed Write Failed} Windows was unable to save all the data for the file D:\Notes\data\pid.nbf; the data has been lost.  This error may be caused if the device has been removed or the media is write-protected.

Application Log:

  • Volume Shadow Copy Error: VSS waited more than 40 seconds for all voumes to be flushed.  This caused volume \\?\Volume{6e198479-c63d-11df-b53f-806e6f6e6963}\ to timeout while waiting for the release-writes phase of shadow copy creation.  Trying again when disk activity is lower may  solve this problem.

    Operation:
       Executing Asynchronous Operation

    Context:
       Current State: flush-and-hold writes
  • Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume D:\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000], Flush[0x00000000], Release[0x00000000], OnRun[0x80042314].

    Operation:
       Executing Asynchronous Operation

    Context:
       Current State: DoSnapshotSet
  • The VSS service is shutting down due to idle timeout.

Does anybody has seen this error before and can assist to fix this?

Thanks and best regards

Marco

Reply
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

The problem is discussed in:

http://communities.vmware.com/message/1598996

Basiclly you need to disable the Virtual Machine Application Consistent Quiescing to solve your problem.

1 Start the vSphere Client, and log in to a vCenter Server.

2 Select Virtual Machines and Templates and click the Virtual Machines tab.

3  Right‐click the Windows 2008 virtual machine for which you are enabling  the disk UUID attribute, and select Power > Power Off.  The  virtual machine

powers off.

4 Right‐click the virtual machine, and click Edit Settings.

5Click the Options tab, and select the General entry in the settings column.

6Click Configuration Parameters… The Configuration Paramters window appears.

7Click Add Row.

8 In the Name column, enter disk.EnableUUID.

9In the Value column, enter FALSE.

10 Click OK and click Save.

11 Power on the virtual machine.

View solution in original post

Reply
0 Kudos
4 Replies
admin
Immortal
Immortal
Jump to solution

The problem is discussed in:

http://communities.vmware.com/message/1598996

Basiclly you need to disable the Virtual Machine Application Consistent Quiescing to solve your problem.

1 Start the vSphere Client, and log in to a vCenter Server.

2 Select Virtual Machines and Templates and click the Virtual Machines tab.

3  Right‐click the Windows 2008 virtual machine for which you are enabling  the disk UUID attribute, and select Power > Power Off.  The  virtual machine

powers off.

4 Right‐click the virtual machine, and click Edit Settings.

5Click the Options tab, and select the General entry in the settings column.

6Click Configuration Parameters… The Configuration Paramters window appears.

7Click Add Row.

8 In the Name column, enter disk.EnableUUID.

9In the Value column, enter FALSE.

10 Click OK and click Save.

11 Power on the virtual machine.

Reply
0 Kudos
mwiese
Contributor
Contributor
Jump to solution

Hi,

thanks a lot for your reply.

Because this machine can't be powered off during the day, we'll check this flag tonight. I will post the result later on...

Best regards

Marco

Reply
0 Kudos
mwiese
Contributor
Contributor
Jump to solution

Hi,

unfortunately this doesn't resolve my issue.

The flag you mentioned is set, so the VM was created with vSphere 4.1 supporting application quiescing:

temp.jpg

So this is not the problem, isn't it?

For applicationconsistent quiescing to be available, three conditions  must be met:

  • The UUID attribute must be enabled. This is enabled by default on virtual machines created on ESX 4.1 hosts.
  • The virtual machine must use only SCSI disks. For example,  application-consistent quiescing is not supported for virtual machines  with IDE disks. There must as many free SCSI slots in the virtual  machine as the number of disks. For example, if there are 8 SCSI disks  on SCSI adapter 1, there are not enough SCSI slots free to perform  application quiescing.
  • The virtual machine must not use dynamic disks.

Source: http://vknowledge.wordpress.com/category/esxi-4/

Our affected VM uses drive D as dynamic disk. Perhaps this is the root cause of the problem?

Please advise...

Thanks and best regards

Marco

Reply
0 Kudos
mwiese
Contributor
Contributor
Jump to solution

Sorry, my fault!

You told me to disable (FALSE) this flag. Whyever I read to enable (TRUE) it, as it is already set to true...

We'll try to disable the flag and see what happens....

Best regards

Marco

Reply
0 Kudos