container recovery

ouaolegq

New Member
Mar 22, 2019
8
0
1
32
Formatting '/home/vm//images/200/vm-200-disk-0.raw', fmt=raw size=171798691840
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks: 4096/41943040 done
Creating filesystem with 41943040 4k blocks and 10485760 inodes
Filesystem UUID: eec446f4-4b0b-49f8-be78-222b3b15b411
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: 0/1280 done
Writing inode tables: 0/1280 done
Creating journal (262144 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information: 0/1280 done

extracting archive '/mnt/pve/Backup/dump/vzdump-lxc-106-2019_03_22-10_39_35.tar'
tar: ./var/spool/postfix/dev/urandom: Cannot mknod: Operation not permitted
tar: ./var/spool/postfix/dev/random: Cannot mknod: Operation not permitted
tar: ./var/www/local.gepur/backend/runtime/cache/rb/rbac.bin: time stamp 2020-03-14 11:28:09 is 30928938.622233693 s in the future
tar: ./var/www/local.gepur/frontend/runtime/cache/1c/1c23f379dc0322a02f9b1da206402faf.bin: time stamp 2020-02-13 14:51:24 is 28348888.84699883 s in the future
tar: ./var/www/local.gepur/frontend/runtime/cache/7b/7b19997e1b54ca2861694bb22227e999.bin: time stamp 2020-02-13 15:03:22 is 28349606.751682551 s in the future
tar: ./var/www/local.gepur/frontend/runtime/cache/cb/cb4ca4e552a4bc4a2d192cbb12bb684c.bin: time stamp 2020-02-13 14:51:28 is 28348892.750399713 s in the future
tar: ./var/www/local.gepur/frontend/runtime/cache/dd/ddcdb39414de607308ab7df520d644a2.bin: time stamp 2020-02-13 14:43:19 is 28348403.617360606 s in the future
tar: ./var/www/local.gepur/frontend/runtime/cache/45/455f927be9064b57bdab2795230ea521.bin: time stamp 2020-02-13 14:43:15 is 28348399.61698495 s in the future
tar: ./var/www/local.gepur/frontend/runtime/cache/fb/fb2beccb407d3d0738d01b64ae1829ca.bin: time stamp 2020-02-13 14:55:26 is 28349130.616378046 s in the future
tar: ./var/www/local.gepur/frontend/runtime/cache/b7/b7789052b6e6b48bf8dcbeeefd890e48.bin: time stamp 2020-02-13 14:43:15 is 28348399.390454115 s in the future
tar: ./var/www/local.gepur/frontend/runtime/cache/67/6775103600a4904ff29d8c86faea19d0.bin: time stamp 2020-02-13 14:46:08 is 28348572.389474193 s in the future
Total bytes read: 9917788160 (9.3GiB, 9.4MiB/s)
tar: Exiting with failure status due to previous errors
TASK ERROR: unable to restore CT 200 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf - --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' -C /var/lib/lxc/200/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2
 
This container includes device nodes ( /var/spool/postfix/dev/urandom).

Try restoring as a privileged container. (--privileged 1)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!