Article ID: 119937, created on Jan 31, 2014, last review on Sep 22, 2015

  • Applies to:
  • Virtuozzo


A ploop container does not start with the following error:

[root@vz ~]# vzctl start 101
bash: line 58: /bin/cp: cannot execute binary file
 ERROR: Can't copy file /etc/sysconfig/network
Unmount image: /vz/private/101/root.hdd
Container is unmounted

Try to chroot into the container's mount point:

# chroot /vz/root/101
chroot: failed to run command `/bin/bash': Exec format error

In case if chroot into the container's mount point was successful, then the corrupt files may be revealed more precisely:

[root@vz ~]# chroot /vz/root/101
[root@vz /]# ls -la /etc/profile.d/
bash: /bin/ls: cannot execute binary file
[root@vz ~]# file -sk /vz/root/101/bin/ls
/vz/root/101/bin/ls: data

Or, the container does not start without any visible error message:

Run the script /etc/sysconfig/vz-scripts/dists/scripts//
File resolv.conf was modified
Running the command: /etc/sysconfig/vz-scripts/vz-stop 
Unmount image: /vz/private/100/root.hdd
Container is unmounted
Failed to start the Container


Parallels File Cache has been corrupted.


Repair PFcache with the following command:

# pfcache verify /vz/pfcache

Search Words

cannot execute binary file

Exec format error

starting container failed without error

0dd5b9380c7d4884d77587f3eb0fa8ef 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF