Can't restore LXC backup

Kyar

New Member
Sep 9, 2022
29
0
1
Hello,

I have erros when I try to restore a backup :
Code:
recovering backed-up configuration from 'BACKUP:backup/vzdump-lxc-106-2023_08_14-07_03_44.tar.zst'
Formatting '/mnt/pve/BACKUP/images/106/vm-106-disk-0.raw', fmt=raw size=5368709120 preallocation=off
Creating filesystem with 1310720 4k blocks and 327680 inodes
Filesystem UUID: 6d400788-d449-41d1-a823-1c73e7045aa5
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736
mount: /var/lib/lxc/106/rootfs: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
mounting container failed
TASK ERROR: unable to restore CT 106 - command 'mount -o noacl /dev/loop0 /var/lib/lxc/106/rootfs//' failed: exit code 32


It's a lxc container, I have configure backup to keep 1 month but I have only one ...

1692546289431.png

So, I need to restore this backup, someone can help me ?

Thanks you
 
Hi,
Hello,

I have erros when I try to restore a backup :
Code:
recovering backed-up configuration from 'BACKUP:backup/vzdump-lxc-106-2023_08_14-07_03_44.tar.zst'
Formatting '/mnt/pve/BACKUP/images/106/vm-106-disk-0.raw', fmt=raw size=5368709120 preallocation=off
Creating filesystem with 1310720 4k blocks and 327680 inodes
Filesystem UUID: 6d400788-d449-41d1-a823-1c73e7045aa5
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736
mount: /var/lib/lxc/106/rootfs: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
mounting container failed
TASK ERROR: unable to restore CT 106 - command 'mount -o noacl /dev/loop0 /var/lib/lxc/106/rootfs//' failed: exit code 32
This sounds like https://bugzilla.proxmox.com/show_bug.cgi?id=4846 and the reason is that the noacl option got removed for ext4. Can you verify that the configuration in the backup uses acl=0? If yes, what you can do is either:
  • Restore via CLI and specify --rootfs <target storage ID>:<size in GiB> as part of the command.
  • Extract the archive manually, edit the configuration removing acl=0, and repack it. Then restore.
  • Wait until the bug is fixed.
It's a lxc container, I have configure backup to keep 1 month but I have only one ...
keep-monthly=N means it should only keep backups for N different months, so only 1 in your case. See the Prune Simulator to better understand the settings: https://pbs.proxmox.com/docs/prune-simulator/index.html
View attachment 54465

So, I need to restore this backup, someone can help me ?
 
  • Like
Reactions: jieiku and Kyar
Hi,

This sounds like https://bugzilla.proxmox.com/show_bug.cgi?id=4846 and the reason is that the noacl option got removed for ext4. Can you verify that the configuration in the backup uses acl=0? If yes, what you can do is either:
  • Restore via CLI and specify --rootfs <target storage ID>:<size in GiB> as part of the command.
  • Extract the archive manually, edit the configuration removing acl=0, and repack it. Then restore.
  • Wait until the bug is fixed.

keep-monthly=N means it should only keep backups for N different months, so only 1 in your case. See the Prune Simulator to better understand the settings: https://pbs.proxmox.com/docs/prune-simulator/index.html
I was very tired and I tried to restore to BACKUP folder in my NAS and not in local...

But now I have learn prune, I have set keep last = 4

Thanks you,
 
*bump* - still happening with backups/restores in pmx8 - would have thought it was patched out by now.