Difference between revisions of "How to fix corrupted ploop"
| Line 20: | Line 20: | ||
Maybe mount/remount and give a check w/o specifying superblock | Maybe mount/remount and give a check w/o specifying superblock | ||
e2fsck /dev/ploop28980 | e2fsck /dev/ploop28980 | ||
| + | |||
| + | |||
| + | --- | ||
| + | if still issues you may try to mount ploop into folder and copy data | ||
| + | |||
| + | Unmount first of mounted | ||
| + | ploop umount -d /dev/ploop1234 | ||
| + | |||
| + | Mount into some dir | ||
| + | mkdir /mnt/ploop-restore1 | ||
| + | mount -r -o noload /dev/ploop30196 /mnt/ploop-restore1 | ||
Revision as of 15:33, 4 December 2020
Stop the container Mount the container’s ploop image.
cd /vz/private/CTID
check fdisk:
fdisk -l root.hdd/root.hdd
Mount:
ploop mount root.hdd/DiskDescriptor.xml Opening delta /vz/private/16311/root.hdd/root.hdd Adding delta dev=/dev/ploop28980 img=/vz/private/16311/root.hdd/root.hdd (rw) #note the dev=/dev/ploop2890
As from previous output we can see how it's mounted dev=/dev/ploop2890 Try e2fsck
e2fsck /dev/ploop28980
If fail try with another superblock:
mke2fs /dev/ploop28980 # note the block here and use one of them e2fsck -b 32768 /dev/ploop28980
Maybe mount/remount and give a check w/o specifying superblock
e2fsck /dev/ploop28980
---
if still issues you may try to mount ploop into folder and copy data
Unmount first of mounted
ploop umount -d /dev/ploop1234
Mount into some dir
mkdir /mnt/ploop-restore1 mount -r -o noload /dev/ploop30196 /mnt/ploop-restore1
