NickTheGreek 160 Report post Posted May 1, 2018 having done this numerous times and yet there is always a first with everything synced 100% successfully and yet the ploop image would not work properly /dev/ploop28196p1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) Error in e2fsck (fsutils.c:293): e2fsck failed (exit code 4) Solution? # ploop check -F /vz/private/139/root.hdd/root.hdd # ploop mount /vz/private/139/root.hdd/DiskDescriptor.xml # fdisk -l /dev/ploop56824 # e2fsck /dev/ploop56824p1 # vzctl start 139 Dump file /vz/dump/Dump.131 exists, trying to restore from it Restoring container ... Unmounting device /dev/ploop56824 Opening delta /vz/private/131/root.hdd/root.hdd Adding delta dev=/dev/ploop56824 img=/vz/private/131/root.hdd/root.hdd (rw) Mounting /dev/ploop56824p1 at /vz/root/131 fstype=ext4 data='balloon_ino=12,' Container is mounted undump... Adding IP address(es): 78.129.146.84 Setting CPU limit: 100 Setting CPU units: 1000 Setting CPUs: 1 Setting iolimit: 67108864 bytes/sec resume... Container start in progress... Restoring completed successfully https://serverfault.com/questions/666443/openvz-containers-will-not-start-after-a-reboot Quote Share this post Link to post Share on other sites
NickTheGreek 160 Report post Posted May 14, 2018 always handy !!! Quote Share this post Link to post Share on other sites
