Article ID: 123033, created on Sep 30, 2014, last review on Sep 30, 2014

  • Applies to:
  • Virtuozzo containers for Linux 4.7


  1. fsck was run on the /vz partition (automatically or manually, after an incorrect node shutdown)
  2. After that some of the containers are missing (not displayed by the vzlist -a command, but the container's private area is present in the /vz/private directory and has a proper size)


Container's ve.conf file was corrupted (vz/private/CTID/ve.conf).


  1. Check the contents of the lost+found directory for the vz partition (the contents of the files that were moved there).
  2. If the ve.conf file was not moved to the /vz/lost+found, restore the configuration file from one of the container's backups (this can be done using "vzarestore --print-ct-config BackupID" command)
  3. Place the restored ve.conf file in /vz/private/CTID/ve.conf
  4. To register the container create a symbolic link in the /etc/sysconfig/vz-scripts/ folder. e.g for container 101:

    # cd /etc/sysconfig/vz-scripts
    # ln -s /vz/private/101/ve.conf 101.conf  

Search Words

container missing after fsck

container conf file corrupted

container missing after e2fsck

e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 0c05f0c76fec3dd785e9feafce1099a9

Email subscription for changes to this article
Save as PDF