Article ID: 123456, created on Nov 7, 2014, last review on Nov 7, 2014

  • Applies to:
  • Virtuozzo containers for Linux 4.7


After preforming a force reboot from inside the container ("reboot -f") the container stays in "mounted" state.


Simple "reboot" inside the container causes the execution of the runlevel 6 scripts, including "vzreboot".

This script creates a 'reboot' file in the root directory of the container. The presence if this file is detected by the "/etc/cron.d/vereboot" job on the node - and the container is started.

In case "reboot" was performed with "-f" option - execution of the scripts is skipped. As a result - the 'reboot' mark is not created and the container is not started from the node - it is left in the 'mounted' state.

A similar situation will be observed in case "/etc/cron.d/vereboot" cron task is manually disabled/deleted on the node: "vzreboot" script will create the 'reboot' mark in the root directory, the container will go and remain in "mounted" state.


Use "reboot" without "-f" option inside the container.

Check that "/etc/cron.d/vereboot" cron task is present and enabled on the node.

Search Words

container in mounted state

reboot -f


e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 0c05f0c76fec3dd785e9feafce1099a9

Email subscription for changes to this article
Save as PDF