Article ID: 1008, created on Jan 31, 2012, last review on May 6, 2014

  • Applies to:
  • Plesk 11.0 for Windows
  • Virtuozzo containers for Windows


The following error appears on the node in the 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


The virtual disk of VE with GUID, starting with {F9B7EA79-9590, is corrupted.


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

2. Stop issued VE:
vzctl stop VEID

3. Make copy of z:\vz\private\VEID\root.efd for emergency cases.
4. Mount the root.efd file:
vzdskctl mount z:\vz\private\VEID\root.efd GUID

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

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

6. When it's finished - unmount the root.efd fle:
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 including drives D:\ or E:\ Use the additional drive's GUID from the c:\vz\conf\VEID.conf instead of the VE's 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 };"

965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 85a92ca67f2200d36506862eaa6ed6b8 514af229ae32522202a910a2649c80fb bd7fc88cf1b01f097749ae6f87272128

Email subscription for changes to this article