{"id":2068,"date":"2017-08-27T22:49:57","date_gmt":"2017-08-28T04:49:57","guid":{"rendered":"https:\/\/www.supportpro.com\/blog\/?p=2068"},"modified":"2019-10-29T05:26:05","modified_gmt":"2019-10-29T11:26:05","slug":"how-to-perform-fsck-on-a-ploop-container-2","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/how-to-perform-fsck-on-a-ploop-container-2\/","title":{"rendered":"How to Perform fsck on a ploop Container?"},"content":{"rendered":"

Due to various reasons like system crash, incorrect replication level etc, the file system in a ploop container will get corrupted that can result in data loss. So it is necessary to check the filesystem in a ploop container for consistency to avoid this loss of data.<\/p>\n

Error<\/strong><\/p>\n

~# vzctl start 123<\/em><\/span><\/p>\n

Starting container\u2026<\/em><\/span><\/p>\n

Opening delta \/vz\/private\/123\/root.hdd\/root.hdd<\/em><\/span><\/p>\n

Adding delta dev=\/dev\/ploopxxxxx img=\/vz\/private\/123\/root.hdd\/root.hdd (rw)<\/em><\/span><\/p>\n

\/dev\/ploopxxxxxp1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.<\/em><\/span><\/p>\n

(i.e., without -a or -p options)<\/em><\/span><\/p>\n

Error in e2fsck (fsutils.c:315): e2fsck failed (exit code 4)<\/em><\/span><\/p>\n

Failed to mount image: Error in e2fsck (fsutils.c:315): e2fsck failed (exit code 4)<\/em><\/span><\/p>\n

<\/p>\n

Resolution<\/strong><\/p>\n

1. Stop the container<\/p>\n

2. Mount the container’s ploop image.<\/p>\n

3. Run fdisk -l for the ploop\u00a0device reported by the previous command.<\/p>\n

4. Perform a file system check for the partition reported in the previous command’s output.<\/p>\n

5. Unmount the ploop image<\/p>\n

6. Start the container.<\/p>\n

 <\/p>\n

Done! You should be good to go now!<\/p>\n

If you require help, contact SupportPRO Server Admin<\/a><\/p>\n

\"Server<\/a><\/span>