failed pve-zsync restore from FreeNAS backup

[DynFi User]

Hello,

I was experimenting a bit with pve-zsync
All of our backups are done on a FreeNAS server and I was able to very easily backup the container on my FreeNAS server.

I am now trying to restore the snapshot from my FreeNAS server.
Restoring went very well and I now have a clean pool with my container mounted where It should be :

root@proxmaster:/etc/pve/lxc# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 119G 2.21T 170K /rpool
rpool/ROOT 105G 2.21T 170K /rpool/ROOT
rpool/ROOT/pve-1 105G 2.21T 105G /
rpool/data 5.53G 2.21T 170K /rpool/data
rpool/data/subvol-100-disk-1 5.53G 4.47G 5.53G /rpool/data/subvol-100-disk-1
rpool/swap 8.50G 2.22T 114K -​

My config has been adapted from the previous server and looks like this :

root@proxmaster:/etc/pve/lxc# cat /etc/pve/lxc/100.conf
arch: amd64
cpulimit: 1
cpuunits: 1024
hostname: osntest.osnet.lan
memory: 3072
nameserver: 192.168.210.25 192.168.210.106
ostype: ubuntu
rootfs: ZFS:subvol-100-disk-1,size=10G
searchdomain: osnet.lan
swap: 2048
​

When I try to start the container, I have a failure with very limited data and info available. So I have restarted It with more debug using :

lxc-start --name 100 --logpriority=DEBUG​

The output of the debug is as follow :

lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:324 - processing: .[all].
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:324 - processing: .kexec_load errno 1.
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:426 - Adding native rule for kexec_load action 327681
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:429 - Adding compat rule for kexec_load action 327681
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:324 - processing: .open_by_handle_at errno 1.
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:426 - Adding native rule for open_by_handle_at action 327681
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:429 - Adding compat rule for open_by_handle_at action 327681
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:324 - processing: .init_module errno 1.
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:426 - Adding native rule for init_module action 327681
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:429 - Adding compat rule for init_module action 327681
lxc-start 1464623897.100 INFO lxc_start - start.c:lxc_check_inherited:226 - closed inherited fd 4
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:324 - processing: .finit_module errno 1.
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:426 - Adding native rule for finit_module action 327681
lxc-start 1464623897.100 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:233 - Seccomp: got negative # for syscall: finit_module
lxc-start 1464623897.100 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:234 - This syscall will NOT be blacklisted
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:429 - Adding compat rule for finit_module action 327681
lxc-start 1464623897.100 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:233 - Seccomp: got negative # for syscall: finit_module
lxc-start 1464623897.100 WARN lxc_seccomp - seccomp.c:do_resolve_add_rule:234 - This syscall will NOT be blacklisted
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:324 - processing: .delete_module errno 1.
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:426 - Adding native rule for delete_module action 327681
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:429 - Adding compat rule for delete_module action 327681
lxc-start 1464623897.100 INFO lxc_seccomp - seccomp.carse_config_v2:436 - Merging in the compat seccomp ctx into the main one
lxc-start 1464623897.100 INFO lxc_conf - conf.c:run_script_argv:362 - Executing script '/usr/share/lxc/hooks/lxc-pve-prestart-hook' for container '100', config section 'lxc'
lxc-start 1464623897.104 INFO lxc_monitor - monitor.c:lxc_monitor_sock_name:178 - using monitor sock name lxc/ad055575fe28ddd5//var/lib/lxc
lxc-start 1464623897.551 ERROR lxc_conf - conf.c:run_buffer:342 - Script exited with status 255
lxc-start 1464623897.551 ERROR lxc_start - start.c:lxc_init:436 - failed to run pre-start hooks for container '100'.
lxc-start 1464623897.551 ERROR lxc_start - start.c:__lxc_start:1170 - failed to initialize the container
lxc-start 1464623897.551 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:172 - command get_init_pid failed to receive response
lxc-start 1464623897.552 WARN lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error
lxc-start 1464623902.557 ERROR lxc_start_ui - lxc_start.c:main:344 - The container failed to start.
lxc-start 1464623902.557 ERROR lxc_start_ui - lxc_start.c:main:346 - To get more details, run the container in foreground mode.
lxc-start 1464623902.557 ERROR lxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options.​

I am not sure what went wrong ?


Any help or pointer will be welcome, I am simply trying to have a safe backup / restore procedure using standard tools.


Sincerely yours.

 

[DynFi User]

Ok - I found the solution by myself :

I have created a new container and compared the semantic in /etc/pve/lxc/

And I found out that my data were defined as :

rootfs: ZFS:subvol-100-disk-1,size=10G
​

Where they should instead look like :

rootfs: volume=local-zfs:subvol-100-disk-1,size=10G​

And that's It !
Works like a charm (at least It starts ok !)