Help troubleshooting restoring a VM

[redmop]

This error happens when I try and create a VM. It works for a while after reboot. When I create a zvol, it does not show up under /dev/zvol until I reboot.

What is my next step?

Task viewer: VM 223 - Restore

OutputStatus

Stop
restore vma archive: lzop -d -c /mnt/cb-nas1/proxbackup/dump/vzdump-qemu-214-2018_04_20-01_05_02.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp22965.fifo - /var/tmp/vzdumptmp22965
CFG: size: 386 name: qemu-server.conf
CFG: size: 489 name: qemu-server.fw
DEV: dev_id=1 size: 68719476736 devname: drive-scsi0
CTIME: Fri Apr 20 01:05:10 2018
new volume ID is 'snap-1d:vm-223-disk-1'
map 'drive-scsi0' to '/dev/zvol/rpool/data/vms/snap-1d/vm-223-disk-1' (write zeros = 0)

** (process:22978): ERROR **: can't open file /dev/zvol/rpool/data/vms/snap-1d/vm-223-disk-1 - Could not open '/dev/zvol/rpool/data/vms/snap-1d/vm-223-disk-1': No such file or directory
/bin/bash: line 1: 22977 Broken pipe lzop -d -c /mnt/cb-nas1/proxbackup/dump/vzdump-qemu-214-2018_04_20-01_05_02.vma.lzo
22978 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp22965.fifo - /var/tmp/vzdumptmp22965
temporary volume 'snap-1d:vm-223-disk-1' sucessfuly removed
TASK ERROR: command 'lzop -d -c /mnt/cb-nas1/proxbackup/dump/vzdump-qemu-214-2018_04_20-01_05_02.vma.lzo|vma

pveversion -v
proxmox-ve: 5.1-41 (running kernel: 4.13.13-6-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13.13-6-pve: 4.13.13-41
pve-kernel-4.13.4-1-pve: 4.13.4-26
corosync: 2.4.2-pve3
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-3
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.6-pve1~bpo9

 zfs list -o name
NAME
rpool
rpool/ROOT
rpool/ROOT/pve-1
rpool/data
rpool/data/home
rpool/data/home/root
rpool/data/vms
rpool/data/vms/pve-config
rpool/data/vms/snap-15m
rpool/data/vms/snap-1d
rpool/data/vms/snap-1d/vm-200-disk-1
rpool/data/vms/snap-1d/vm-201-disk-1
rpool/data/vms/snap-1d/vm-203-disk-1
rpool/data/vms/snap-1d/vm-204-disk-1
rpool/data/vms/snap-1d/vm-205-disk-1
rpool/data/vms/snap-1d/vm-206-disk-1
rpool/data/vms/snap-1d/vm-207-disk-1
rpool/data/vms/snap-1d/vm-209-disk-1
rpool/data/vms/snap-1d/vm-210-disk-1
rpool/data/vms/snap-1d/vm-220-disk-1
rpool/data/vms/snap-1d/vm-222-disk-1
rpool/data/vms/snap-custom
rpool/data/vms/sync-15m
rpool/data/vms/sync-15m/vm-100-disk-1
rpool/data/vms/sync-15m/vm-104-disk-1
rpool/data/vms/sync-15m/vm-118-disk-1
rpool/data/vms/sync-15m/vm-118-disk-2
rpool/data/vms/sync-15m/vm-213-disk-1
rpool/data/vms/sync-1d
rpool/data/vms/sync-custom
rpool/swap

Apr 20 10:01:18 cb-prox1 pvedaemon[56115]: <root@pam> starting task UPID:cb-prox1:0000D2AD:07A2E846:5ADA0ECE:qmrestore:223:root@pam:
Apr 20 10:01:18 cb-prox1 zed: eid=126083 class=history_event pool_guid=0x6E26C39814F6EB27
Apr 20 10:01:18 cb-prox1 pvedaemon[26257]: storage 'cb-nas1_isos' is not online
Apr 20 10:01:19 cb-prox1 kernel: [1281158.228694] traps: vma[53937] trap int3 ip:7f9f903ca261 sp:7ffdcec1c9b0 error:0 in libglib-2.0.so.0.5000.3[7f9f9037a000+112000]
Apr 20 10:01:19 cb-prox1 zed: eid=126084 class=history_event pool_guid=0x6E26C39814F6EB27
Apr 20 10:01:19 cb-prox1 pvedaemon[53933]: command 'lzop -d -c /mnt/cb-nas1/proxbackup/dump/vzdump-qemu-214-2018_04_20-01_05_02.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp53933.fifo - /var/tmp/vzdumptmp53933' failed: exit code 133
Apr 20 10:01:19 cb-prox1 pvedaemon[56115]: <root@pam> end task UPID:cb-prox1:0000D2AD:07A2E846:5ADA0ECE:qmrestore:223:root@pam: command 'lzop -d -c /mnt/cb-nas1/proxbackup/dump/vzdump-qemu-214-2018_04_20-01_05_02.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp53933.fifo - /var/tmp/vzdumptmp53933' failed: exit code 133

 

[redmop]

On another host, it let me restore 1 VM, but not a second one before it did the same error.

 

[redmop]

Bump
Anyone?