Article ID: 118002, created on Oct 17, 2013, last review on May 8, 2014

  • Applies to:
  • Virtuozzo containers for Windows

Symptoms

Container with additional disk configured cannot start with the following error :

C:\>vzctl start 101
Starting container ...
ERROR: Parallels Virtuozzo Containers API function call 'VZVolumeMountExW' failed (C:\vz\Private\101\lpbk0001.efd, {f60a13a8-5a82-40f2-824f-580ee83b882e}) err = 2
ERROR: Parallels Virtuozzo Containers API function call 'VpsVolumeMount' failed
ERROR: Drive 'D' is not mounted
Container is mounted
Container was started

Cause

The file of second drive was removed from the server.

Resolution

Restore the missing .efd file to the container private directory %VZROOT%\private\CTID.

If restoring the file is not possible, remove the corresponding line from the container configuration file %VZROOT%\Conf\CTID.conf. The line has the following format:

C:\>type C:\vz\conf\101.conf | findstr DRIVE
DRIVE_D="type=loopback;guid={F60A13A8-5A82-40F2-824F-580EE83B882E};file=lpbk0001.efd;quota=1024000000;total=1023995904;free=989765632"

Note: Create a backup of the configuration file prior to any changes made to it.

The container should be able to start successfully afterwards.

Search Words

failed to start

Parallels Virtuozzo Containers API function call 'VZVolumeMountExW' failed

cannot start

err = 2

'VpsVolumeMount' failed

additional drive

d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8

Email subscription for changes to this article
Save as PDF