Article ID: 126933, created on Sep 18, 2015, last review on Jun 17, 2016

  • Applies to:
  • APS 2.x
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux

Symptoms

Container cannot be started with the following error:

[root@vz ~]# vzctl start 101
Mount image: /vz/private/101/root.hdd
/dev/ploop30233p1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)
Failed to mount image /vz/private/101/root.hdd: e2fsck failed (exit code 4)
Failed to mount image: e2fsck failed (exit code 4) [152]

Cause

Container's mount fails due to file system errors inside the ploop virtual disk.

Resolution

Run the check disk as per the instructions from the following article

115683 How to perform fsck on a ploop container

Search Words

Failed to mount image: Error in e2fsck

virtuozzo container is not getting started

Failed to mount image /vz/private/2455/root.hdd: Error in e2fsck

Failed to mount image

csid failure

disk space shows zettabytes

RUN fsck MANUALLY

container

e2fsck: Bad magic number in super-block while trying to open

Error in e2fsck

UNEXPECTED INCONSISTENCY

e2fsck failed

e2fsck failed (exit code 4)

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef 717db81efe94e616312b74fb03a5d474 70bf700e0cdb9d7211df2595ef7276ab e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f

Email subscription for changes to this article
Save as PDF