How to check the filesystem for a Windows VE if it has ntfs errors?

The following error appears on the node in Event Viewer:

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 8/24/2006
Time: 8:04:16 AM
User: N/A
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\VZLPBKVolumes\VZLPBKVolume{F9B7EA79-9590....For more information, see Help and Support Center at
Virtual disk of VE with GUID started with {F9B7EA79-9590... is corrupted.

1. List GUIDs of all VEs and choose the required one (create a .cmd, copy commands below and run to list all GUIDs):
@echo off
for /F "skip=3 usebackq tokens=*" %%i in (`cmd /c "vzlist -ao veid"`) do (cmd /c "vzcfgt get %%i GUID" && echo is GUID of VE %%i)

2. Stop issued VE:
vzctl stop VEID

3. Do copy of z:\vz\private\VEID\root.efd for emergency cases.

4. Mount root.efd file:
vzdskctl mount z:\vz\private\VEID\root.efd GUID

5. Run chkdsk on mounted root.efd
chkdsk /f \\?\VolumeGUID

where GUID (after Volume) is a value obtained at step (1).

6. When it’s finished – unmount root.efd:
vzdskctl umount GUID

7. Start VE:
vzctl start VE

A real life example:

vzctl stop 115
vzcfgt get 115 GUID
vzdskctl mount c:\vz\private\115\root.efd {799251BE-720C-468E-B877-913F49476001 }
chkdsk /f \\?\Volume{799251BE-720C-468E-B877-913F49476001 }
vzdskctl umount {799251BE-720C-468E-B877-913F49476001 }
vzctl start 115

Note: this approach works perfectly for additional drives, added via the Mount manager, ie drives D:\ or E:\ Use the additional drive’s GUID from the c:\vz\conf\VEID.conf instead of the VE’ primary GUID to perform the same operations, see GUID example for drive D: DRIVE_D=”type=loopback;file=lpbk0000.efd;guid={cc4a1cb5-9f9d-47ac-a09f-0e6b87643105 };”