Article ID: 1008, created on Oct 6, 2008, last review on Jun 17, 2016

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


  1. The following error appears on the node in the Event Viewer:

    Event Type: Error
    Event Source: Ntfs
    Event Category: Disk
    Event ID: 55
    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 the container with GUID (starting with "{F9B7EA79-9590") is corrupted.


  1. List the GUIDs of all VEs and choose the required one:

    for /F %i in ('vzlist -Hao veid') do vzcfgt get %i GUID && echo is GUID of VE %i
  2. Stop the issued CT:

    vzctl stop CTID
  3. Make a copy of "z:\vz\private\CTID\root.efd" in case of emergency.

  4. Mount the "root.efd" file:

    vzdskctl mount z:\vz\private\CTID\root.efd GUID

    If this step cannot be completed, for example:

    C:\Users\Administrator>vzdskctl mount c:\vz\private\101\root.efd {3B461D9D-D930-4FD8-9D2C-898166C222A1}

    Refer to: 113728 "Issues caused by high fragmentation of root.efd"

  5. Run "chkdsk" on the mounted "root.efd" file:

    chkdsk /f \\?\VolumeGUID

(where "GUID" (after "Volume") is the value obtained in step 1)

  1. When the process is finished, unmount the "root.efd" file:

    vzdskctl umount GUID
  2. Start the CT:

    vzctl start CTID

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 for additional drives added via the Mount manager, including drives D:\ or E:.

Use the additional drive's GUID from "c:\vz\conf\VEID.conf" instead of the VE's primary GUID to perform the same operations. See this GUID example for drive D:

    DRIVE_D="type=loopback;file=lpbk0000.efd;guid={cc4a1cb5-9f9d-47ac-a09f-0e6b87643105 };"

Additional Information

Corrupted permissions may cause various inconsistencies inside containers. As a result, operating system components and applications may continue malfunctioning even after you have fixed the permissions issue.

If you come across this behavior and are unable to quickly diagnose and fix it, it is recommended you consider restoring the container from a backup or even creating a new empty container and moving the old data from the corrupted container manually.

Search Words


ntfs error eventid 55

mount failed

already used by container


{Registry Hive Recovered} Registry hive (file): '\??\D:\vz\Private\907\root\vzquota\machine' was corrupted and it has been recovered. Some data might have been lost.


mysql several times crush in the specified container after vzupdate and windows update

API function call 'VzkrnlLockNFlushRegistry' failed

Bugcheck VDI117

disk quota on vps

pmigrate c administrator@ v 126

The file system structure on the disk is corrupt and unusable

Windows API function call 'CreateFile' failed

Windows Process Activation Service does not work inside containers: "System error 6801 has occurred"

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

Email subscription for changes to this article
Save as PDF