vzdump "no such volume" error

S

stra4d

Well-Known Member
Mar 1, 2012
80
0
46
I have seen some older posts (version 5.2) with this error. The solution was to update. I am running the current 5.3 version and got this error on a backup last night. This file does exist, and the VM is running so not sure why we got this error.

2019-02-14 18:27:23 ERROR: Backup of VM 110 failed - no such volume 'local-lvm:vm-110-disk-1

pveversion -v:
Code: 
# pveversion -v
proxmox-ve: 5.3-1 (running kernel: 4.15.18-11-pve)
pve-manager: 5.3-9 (running version: 5.3-9/ba817b29)
pve-kernel-4.15: 5.3-2
pve-kernel-4.13: 5.2-2
pve-kernel-4.15.18-11-pve: 4.15.18-33
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-1-pve: 4.15.18-19
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-2-pve: 4.15.17-10
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.13.16-4-pve: 4.13.16-51
pve-kernel-4.13.16-3-pve: 4.13.16-50
pve-kernel-4.13.16-2-pve: 4.13.16-48
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.4.98-3-pve: 4.4.98-103
pve-kernel-4.4.98-2-pve: 4.4.98-101
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.4.19-1-pve: 4.4.19-66
corosync: 2.4.4-pve1
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.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-46
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-38
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-34
pve-docs: 5.3-2
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-46
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1

/etc/pve/storage.cfg:
Code: 
dir: local
        path /var/lib/vz
        content vztmpl
        shared 0
        maxfiles 1

lvmthin: local-lvm
        thinpool data
        vgname pve
        content images,rootdir

dir: drive2-vm
        path /drive2/vm
        content images,rootdir
        shared 0
        maxfiles 1

dir: drive2-backups
        path /drive2/vzdumpbackups
        content backup
        shared 0
        maxfiles 1

Running the vzdump manually (just this vm isolated) works fine.
 
Last edited:
Can you please share your vm config
 
Code: 
agent: 1
balloon: 2048
boot: dc
bootdisk: virtio0
cores: 8
ide2: cdrom,media=cdrom
memory: 12288
name: iddemo
net0: e1000=2A:80:53:BB:21:E0,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
scsihw: virtio-scsi-pci
sockets: 2
vga: std
virtio0: local-lvm:vm-110-disk-1,size=50G
 
I'm also seeing the same type of error and it's happen on multiple of my VMs, but only one at a time.

102 ucs FAILED 00:00:07 no such volume 'local-lvm:vm-102-disk-1'

So far I've just run the backup manually after the scheduled backup fails for one of the VMs and it's worked fine. I've started ignoring it now and so far (knock on wood...) I've never had the same VM disk fail to back up two days in a row.

On the 11th I had my FreeBSD VM fail with this error. Then the nightly backups were fine until yesterday the 21st when one of my Debian VMs failed to backup with the error. Then today my FreeBSD VM failed to backup again.

It's a weird problem. If I can help by providing some info just let me know. I'm really not sure what to look at at this point.

I'm running a Ryzen 2600 based system with 32GB ECC RAM and 4 VMs. This problem did not happen for a while after I set up my system. My best guess is it was triggered by some update or other, but I don't have any idea which one as the problem is somewhat random.

Going back in my vzdump emails I see the first backup error I could find was this.

102 ucs FAILED 00:26:01 vma_queue_write: write error - Broken pipe
103 VM 103 FAILED 00:00:00 unable to create temporary directory '/mnt/backups/dump/vzdump-qemu-103-2018_11_29-03_28_14.tmp' at /usr/share/perl5/PVE/VZDump.pm line 825.

I think this problem might have beeen totally unrelated though as we were having UPS problems and the batteries dying caused us issues when the ups would run it's self test the server would die. I think this error happened around that time.
 
Not sure if this is related, but the same VM had an issue w/ the backup last night after doing an update via dist-upgrade:

Code: 
110: 2019-02-27 18:27:06 INFO: Starting Backup of VM 110 (qemu)
110: 2019-02-27 18:27:06 INFO: status = running
110: 2019-02-27 18:27:08 INFO: update VM 110: -lock backup
110: 2019-02-27 18:27:08 INFO: VM Name: iddemo
110: 2019-02-27 18:27:08 INFO: include disk 'virtio0' 'local-lvm:vm-110-disk-1' 50G
110: 2019-02-27 18:27:08 INFO: backup mode: snapshot
110: 2019-02-27 18:27:08 INFO: ionice priority: 7
110: 2019-02-27 18:27:08 INFO: creating archive '/drive2/vzdumpbackups/dump/vzdump-qemu-110-2019_02_27-18_27_06.vma.lzo'
110: 2019-02-27 18:27:14 ERROR: got timeout
110: 2019-02-27 18:27:14 INFO: aborting backup job
110: 2019-02-27 18:27:17 ERROR: Backup of VM 110 failed - got timeout

VMs before and after this one (in order they are backup up) worked fine, all go to same local drive.
 
stra4d said:
110: 2019-02-27 18:27:08 INFO: creating archive '/drive2/vzdumpbackups/dump/vzdump-qemu-110-2019_02_27-18_27_06.vma.lzo' 110: 2019-02-27 18:27:14 ERROR: got timeout
Click to expand...

I'd guess it's not related and probably has something to do with the storage on /drive2/. If it's NFS, then it's most likely a network/storage problem (hence timeout and not other kind of error).
 
I still have this issue from time to time. So far I have no idea what triggers it. It doesn't always happen on the same VM either. I have 4 VMs on my server and as far as I can tell, it never happens on the first vm or the last vm in the backups. It's always either the second or the third. One of those VMs is relatively small BSD at about 4GB and the other one is a bigger Debian install at about 25GB.

It also never fails on both VMs at once. It's only one or the other.
 
I just had it happen as well on one VM out of five. It was the second one out of five, the first backup of a Windows 10 qemu was fine, the second backup of a Debian qemu failed, then the last three lxc's all succeeded. The error logged was "no such volume 'local-lvm:vm-102-disk-0", which does in fact exist. Re-running the backup manually from the GUI worked fine.

102: 2019-03-26 00:06:31 INFO: Starting Backup of VM 102 (qemu)
102: 2019-03-26 00:06:31 INFO: status = running
102: 2019-03-26 00:06:32 INFO: update VM 102: -lock backup
102: 2019-03-26 00:06:32 INFO: VM Name: robin
102: 2019-03-26 00:06:32 INFO: include disk 'scsi0' 'local-lvm:vm-102-disk-0' 100G
102: 2019-03-26 00:06:40 ERROR: Backup of VM 102 failed - no such volume 'local-lvm:vm-102-disk-0'

The volume is 100G but only 32 are partitioned right now and the backup size is around 6 GB after compression.

The lvm storage is on a Linux RAID1 with 2x1TB SSD's so Proxmox was installed on top of Debian. The server has a Supermicro Xeon D-1541 motherboard with 32 GB of RAM.
 
The past 3 nights the same VM out of the 4 I have on my server has given me this error. I backed it up manually this morning with no problems.

Not sure what to do to troubleshoot this, but it doesn't seem to be getting better, and there doesn't appear to be any issues with the VM. Also I've never had a manual backup fail, so it must be something to do with the automated process somehow.
 
Well, the past week everything had been working well with no backup failures, and then this morning I get the email from the backup tool and 3 out of 4 of my VMs failed with the no such volume error. This is the first time in a long time that more than one backup failed, and I'm pretty sure I've never had more than two fail before.

So anyone have any ideas how to go about troubleshooting this?
 
Hello,

I had similar issues after upgrading to version 5.4-3 lately, three out of five backups failed, but in my case also manual backups of single VM's didn't work anymore.

INFO: starting new backup job: vzdump 100 110 111 112 113 --node pve --quiet 1 --mailto p.euerle@shutdown-r.wtf --storage backup --mode snapshot --compress lzo --mailnotification failure
INFO: Starting Backup of VM 100 (qemu)
INFO: status = running
INFO: update VM 100: -lock backup
INFO: VM Name: sophos
INFO: include disk 'virtio0' 'local-lvm:vm-100-disk-0' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/backup/dump/vzdump-qemu-100-2019_04_26-02_00_02.vma.lzo'
INFO: started backup task '3a0e645b-3928-46dd-b5fa-a8b869b108ba'
INFO: status: 0% (665124864/107374182400), sparse 0% (372715520), duration 3, read/write 221/97 MB/s
INFO: status: 1% (1649737728/107374182400), sparse 1% (1161392128), duration 6, read/write 328/65 MB/s
INFO: status: 2% (2770993152/107374182400), sparse 2% (2161897472), duration 9, read/write 373/40 MB/s
INFO: status: 3% (3363831808/107374182400), sparse 2% (2197790720), duration 12, read/write 197/185 MB/s
INFO: status: 4% (4375052288/107374182400), sparse 2% (2934992896), duration 18, read/write 168/45 MB/s
INFO: status: 5% (5399117824/107374182400), sparse 2% (3069157376), duration 26, read/write 128/111 MB/s
INFO: status: 6% (6530269184/107374182400), sparse 2% (3211845632), duration 35, read/write 125/109 MB/s
INFO: status: 7% (7518552064/107374182400), sparse 2% (3216769024), duration 93, read/write 17/16 MB/s
INFO: status: 8% (8632270848/107374182400), sparse 3% (3354263552), duration 158, read/write 17/15 MB/s
INFO: status: 9% (9666166784/107374182400), sparse 3% (3409145856), duration 203, read/write 22/21 MB/s
INFO: status: 10% (10753277952/107374182400), sparse 3% (3546836992), duration 263, read/write 18/15 MB/s
INFO: status: 11% (11813781504/107374182400), sparse 3% (3585572864), duration 338, read/write 14/13 MB/s
INFO: status: 12% (12912295936/107374182400), sparse 3% (3901169664), duration 380, read/write 26/18 MB/s
INFO: status: 13% (13961396224/107374182400), sparse 3% (3954061312), duration 435, read/write 19/18 MB/s
INFO: status: 14% (15063711744/107374182400), sparse 3% (4283396096), duration 483, read/write 22/16 MB/s
INFO: status: 15% (16116613120/107374182400), sparse 4% (4454055936), duration 536, read/write 19/16 MB/s
INFO: status: 16% (17198022656/107374182400), sparse 4% (4772425728), duration 597, read/write 17/12 MB/s
INFO: status: 17% (18281594880/107374182400), sparse 4% (5005275136), duration 642, read/write 24/18 MB/s
INFO: status: 18% (19339935744/107374182400), sparse 4% (5294325760), duration 692, read/write 21/15 MB/s
INFO: status: 19% (20411842560/107374182400), sparse 5% (5507112960), duration 747, read/write 19/15 MB/s
INFO: status: 20% (21483749376/107374182400), sparse 5% (5755293696), duration 802, read/write 19/14 MB/s
INFO: status: 21% (22567059456/107374182400), sparse 5% (5974372352), duration 870, read/write 15/12 MB/s
INFO: status: 22% (23646568448/107374182400), sparse 5% (6246084608), duration 933, read/write 17/12 MB/s
INFO: status: 23% (24707072000/107374182400), sparse 5% (6339764224), duration 987, read/write 19/17 MB/s
INFO: status: 24% (25790382080/107374182400), sparse 6% (6616236032), duration 1021, read/write 31/23 MB/s
INFO: status: 25% (26847084544/107374182400), sparse 6% (6652350464), duration 1079, read/write 18/17 MB/s
INFO: status: 26% (27926593536/107374182400), sparse 6% (6787059712), duration 1138, read/write 18/16 MB/s
INFO: status: 27% (29005250560/107374182400), sparse 6% (6787915776), duration 1208, read/write 15/15 MB/s
INFO: status: 28% (30066606080/107374182400), sparse 6% (6922760192), duration 1263, read/write 19/16 MB/s
INFO: status: 29% (31142313984/107374182400), sparse 6% (6974377984), duration 1323, read/write 17/17 MB/s
INFO: status: 30% (32221822976/107374182400), sparse 6% (7108694016), duration 1378, read/write 19/17 MB/s
INFO: status: 31% (33301331968/107374182400), sparse 6% (7140790272), duration 1449, read/write 15/14 MB/s
INFO: status: 32% (34369437696/107374182400), sparse 6% (7275089920), duration 1511, read/write 17/15 MB/s
INFO: status: 33% (35433742336/107374182400), sparse 6% (7292919808), duration 1578, read/write 15/15 MB/s
INFO: status: 34% (36517052416/107374182400), sparse 6% (7430742016), duration 1636, read/write 18/16 MB/s
INFO: status: 35% (37592760320/107374182400), sparse 6% (7457959936), duration 1707, read/write 15/14 MB/s
INFO: status: 36% (38664667136/107374182400), sparse 7% (7679672320), duration 1765, read/write 18/14 MB/s
INFO: status: 37% (39728971776/107374182400), sparse 7% (7693225984), duration 1836, read/write 14/14 MB/s
INFO: status: 38% (40823685120/107374182400), sparse 7% (7853146112), duration 1899, read/write 17/14 MB/s
INFO: status: 39% (41887989760/107374182400), sparse 7% (7919906816), duration 1963, read/write 16/15 MB/s
INFO: status: 40% (42963959808/107374182400), sparse 7% (8109117440), duration 2023, read/write 17/14 MB/s
INFO: status: 41% (44028198912/107374182400), sparse 7% (8189435904), duration 2090, read/write 15/14 MB/s
INFO: status: 42% (45103710208/107374182400), sparse 7% (8247291904), duration 2156, read/write 16/15 MB/s
INFO: status: 43% (46183219200/107374182400), sparse 7% (8253235200), duration 2208, read/write 20/20 MB/s
INFO: status: 44% (47281733632/107374182400), sparse 7% (8282411008), duration 2262, read/write 20/19 MB/s
INFO: status: 45% (48330833920/107374182400), sparse 7% (8284479488), duration 2309, read/write 22/22 MB/s
INFO: status: 46% (49403789312/107374182400), sparse 7% (8307175424), duration 2357, read/write 22/21 MB/s
INFO: status: 47% (50470846464/107374182400), sparse 7% (8307240960), duration 2422, read/write 16/16 MB/s
INFO: status: 48% (51683196928/107374182400), sparse 8% (9264398336), duration 2435, read/write 93/19 MB/s
INFO: status: 49% (53056503808/107374182400), sparse 9% (10637029376), duration 2438, read/write 457/0 MB/s
INFO: status: 50% (54609903616/107374182400), sparse 11% (12190388224), duration 2441, read/write 517/0 MB/s
INFO: status: 52% (56091803648/107374182400), sparse 12% (13669986304), duration 2444, read/write 493/0 MB/s
INFO: status: 53% (57662504960/107374182400), sparse 14% (15238942720), duration 2447, read/write 523/0 MB/s
INFO: status: 55% (59124744192/107374182400), sparse 15% (16701181952), duration 2450, read/write 487/0 MB/s
INFO: status: 56% (60620210176/107374182400), sparse 16% (18193649664), duration 2453, read/write 498/0 MB/s
INFO: status: 57% (62241046528/107374182400), sparse 18% (19813195776), duration 2456, read/write 540/0 MB/s
INFO: status: 59% (63651315712/107374182400), sparse 19% (21218623488), duration 2459, read/write 470/1 MB/s
INFO: status: 60% (65167228928/107374182400), sparse 21% (22734536704), duration 2462, read/write 505/0 MB/s
INFO: status: 61% (66422374400/107374182400), sparse 22% (23988293632), duration 2465, read/write 418/0 MB/s
INFO: status: 63% (67816849408/107374182400), sparse 23% (25382653952), duration 2468, read/write 464/0 MB/s
INFO: status: 64% (69177049088/107374182400), sparse 24% (26741665792), duration 2471, read/write 453/0 MB/s
INFO: status: 65% (70670024704/107374182400), sparse 26% (28231208960), duration 2474, read/write 497/1 MB/s
INFO: status: 67% (71977861120/107374182400), sparse 27% (29539045376), duration 2477, read/write 435/0 MB/s
INFO: status: 68% (73185099776/107374182400), sparse 28% (30745513984), duration 2480, read/write 402/0 MB/s
INFO: status: 69% (74105487360/107374182400), sparse 29% (31665901568), duration 2483, read/write 306/0 MB/s
INFO: status: 70% (75223007232/107374182400), sparse 30% (32430567424), duration 2487, read/write 279/88 MB/s
INFO: status: 71% (76538707968/107374182400), sparse 31% (33385869312), duration 2494, read/write 187/51 MB/s
INFO: status: 72% (77552877568/107374182400), sparse 31% (34291183616), duration 2497, read/write 338/36 MB/s
INFO: status: 73% (78663516160/107374182400), sparse 32% (35399254016), duration 2500, read/write 370/0 MB/s
INFO: status: 74% (79694921728/107374182400), sparse 33% (36430659584), duration 2504, read/write 257/0 MB/s
INFO: status: 75% (80868343808/107374182400), sparse 34% (37544103936), duration 2507, read/write 391/19 MB/s
INFO: status: 76% (82257969152/107374182400), sparse 36% (38906994688), duration 2510, read/write 463/8 MB/s
INFO: status: 78% (83834372096/107374182400), sparse 37% (40480309248), duration 2513, read/write 525/1 MB/s
INFO: status: 79% (85231927296/107374182400), sparse 38% (41874661376), duration 2516, read/write 465/1 MB/s
INFO: status: 80% (86661988352/107374182400), sparse 40% (43304722432), duration 2519, read/write 476/0 MB/s
INFO: status: 81% (88020680704/107374182400), sparse 41% (44658044928), duration 2522, read/write 452/1 MB/s
INFO: status: 83% (89282445312/107374182400), sparse 42% (45919752192), duration 2525, read/write 420/0 MB/s
INFO: status: 84% (90581762048/107374182400), sparse 43% (47217221632), duration 2528, read/write 433/0 MB/s
INFO: status: 85% (91917320192/107374182400), sparse 45% (48551546880), duration 2531, read/write 445/0 MB/s
INFO: status: 87% (93430743040/107374182400), sparse 46% (50064969728), duration 2534, read/write 504/0 MB/s
INFO: status: 88% (94883086336/107374182400), sparse 47% (51516657664), duration 2537, read/write 484/0 MB/s
INFO: status: 89% (96458113024/107374182400), sparse 49% (53090189312), duration 2540, read/write 525/0 MB/s
INFO: status: 91% (97826766848/107374182400), sparse 50% (54458822656), duration 2543, read/write 456/0 MB/s
INFO: status: 92% (99556720640/107374182400), sparse 52% (56179625984), duration 2546, read/write 576/3 MB/s
INFO: status: 94% (101116608512/107374182400), sparse 53% (57738092544), duration 2549, read/write 519/0 MB/s
INFO: status: 95% (102570196992/107374182400), sparse 55% (59191664640), duration 2552, read/write 484/0 MB/s
INFO: status: 96% (103997571072/107374182400), sparse 56% (60618514432), duration 2555, read/write 475/0 MB/s
INFO: status: 97% (104563212288/107374182400), sparse 56% (60734091264), duration 2558, read/write 188/150 MB/s
INFO: status: 98% (105354756096/107374182400), sparse 56% (60850954240), duration 2562, read/write 197/168 MB/s
INFO: status: 99% (107350458368/107374182400), sparse 58% (62846644224), duration 2565, read/write 665/0 MB/s
INFO: status: 100% (107374182400/107374182400), sparse 58% (62870368256), duration 2566, read/write 23/0 MB/s
INFO: transferred 107374 MB in 2566 seconds (41 MB/s)
INFO: archive file size: 34.38GB
INFO: delete old backup '/mnt/pve/backup/dump/vzdump-qemu-100-2019_04_19-02_00_02.vma.lzo'
INFO: Finished Backup of VM 100 (00:44:37)
INFO: Starting Backup of VM 110 (qemu)
INFO: status = running
INFO: update VM 110: -lock backup
INFO: VM Name: fipVPN
INFO: include disk 'virtio0' 'local-data:vm-110-disk-0' 20G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/backup/dump/vzdump-qemu-110-2019_04_26-02_44_39.vma.lzo'
INFO: started backup task '3bb4facd-d70a-4962-9aef-1d96e3c3812c'
INFO: status: 2% (507379712/21474836480), sparse 0% (23846912), duration 3, read/write 169/161 MB/s
INFO: status: 4% (863502336/21474836480), sparse 0% (27463680), duration 6, read/write 118/117 MB/s
INFO: status: 6% (1338441728/21474836480), sparse 0% (29683712), duration 9, read/write 158/157 MB/s
INFO: status: 8% (1759903744/21474836480), sparse 0% (34947072), duration 12, read/write 140/138 MB/s
INFO: status: 9% (2128609280/21474836480), sparse 0% (38600704), duration 15, read/write 122/121 MB/s
INFO: status: 11% (2572484608/21474836480), sparse 0% (46051328), duration 18, read/write 147/145 MB/s
INFO: status: 14% (3033268224/21474836480), sparse 0% (46432256), duration 21, read/write 153/153 MB/s
INFO: status: 16% (3485597696/21474836480), sparse 0% (46661632), duration 24, read/write 150/150 MB/s
INFO: status: 17% (3759276032/21474836480), sparse 0% (47423488), duration 27, read/write 91/90 MB/s
INFO: status: 18% (3933732864/21474836480), sparse 0% (48795648), duration 33, read/write 29/28 MB/s
INFO: status: 20% (4354211840/21474836480), sparse 0% (50302976), duration 36, read/write 140/139 MB/s
INFO: status: 21% (4614520832/21474836480), sparse 0% (50987008), duration 39, read/write 86/86 MB/s
INFO: status: 22% (4825612288/21474836480), sparse 0% (51552256), duration 42, read/write 70/70 MB/s
INFO: status: 26% (5662310400/21474836480), sparse 2% (588222464), duration 45, read/write 278/100 MB/s
INFO: status: 28% (6043729920/21474836480), sparse 2% (614957056), duration 48, read/write 127/118 MB/s
INFO: status: 29% (6306004992/21474836480), sparse 2% (617873408), duration 52, read/write 65/64 MB/s
INFO: status: 31% (6678511616/21474836480), sparse 2% (621432832), duration 55, read/write 124/122 MB/s
INFO: status: 33% (7124549632/21474836480), sparse 3% (772046848), duration 58, read/write 148/98 MB/s
INFO: status: 36% (7773356032/21474836480), sparse 6% (1328046080), duration 61, read/write 216/30 MB/s
INFO: status: 43% (9264037888/21474836480), sparse 13% (2818629632), duration 64, read/write 496/0 MB/s
INFO: status: 47% (10098900992/21474836480), sparse 15% (3413680128), duration 67, read/write 278/79 MB/s
INFO: status: 52% (11285430272/21474836480), sparse 21% (4600135680), duration 70, read/write 395/0 MB/s
INFO: status: 60% (13058637824/21474836480), sparse 29% (6334345216), duration 73, read/write 591/12 MB/s
INFO: status: 66% (14311751680/21474836480), sparse 34% (7500070912), duration 76, read/write 417/29 MB/s
INFO: status: 74% (15991570432/21474836480), sparse 42% (9179783168), duration 79, read/write 559/0 MB/s
INFO: status: 83% (17904566272/21474836480), sparse 51% (11092656128), duration 82, read/write 637/0 MB/s
INFO: status: 92% (19840565248/21474836480), sparse 60% (13028544512), duration 85, read/write 645/0 MB/s
INFO: status: 100% (21474836480/21474836480), sparse 68% (14662709248), duration 88, read/write 544/0 MB/s
INFO: transferred 21474 MB in 88 seconds (244 MB/s)
INFO: archive file size: 2.73GB
INFO: delete old backup '/mnt/pve/backup/dump/vzdump-qemu-110-2019_04_19-02_14_02.vma.lzo'
INFO: Finished Backup of VM 110 (00:02:14)
INFO: Starting Backup of VM 111 (qemu)
INFO: status = running
INFO: update VM 111: -lock backup
INFO: VM Name: unifi
INFO: include disk 'scsi0' 'local-data:vm-111-disk-0' 100G
ERROR: Backup of VM 111 failed - no such volume 'local-data:vm-111-disk-0'
INFO: Starting Backup of VM 112 (qemu)
INFO: status = running
INFO: update VM 112: -lock backup
INFO: VM Name: winappsrv
INFO: include disk 'sata0' 'local-data:vm-112-disk-0' 150G
ERROR: Backup of VM 112 failed - no such volume 'local-data:vm-112-disk-0'
INFO: Starting Backup of VM 113 (qemu)
INFO: status = running
INFO: update VM 113: -lock backup
INFO: VM Name: nextcloud
INFO: include disk 'scsi0' 'local-data:vm-113-disk-0' 100G
INFO: include disk 'scsi1' 'local-data:vm-113-disk-1' 2000G
ERROR: Backup of VM 113 failed - no such volume 'local-data:vm-113-disk-0'
INFO: Backup job finished with errors

TASK ERROR: job errors

pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-12-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
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.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-50
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-25
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-19
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

I got the backup running again by deleting all old backups of the VM's for that the backup did not work anymore (in my case VM ID 111, 112 and 113) including log files from the backup storage.

Easiest way is to SSH into your PVE host, switch to directory "/mnt/pve/backup/dump" and then delete everything by VM-ID with "rm *-[VMID]-*".

Maybe this will solve your issues too.

Greetings
 
It comes and goes for me. Sometimes it will be weeks before I get a failure, and sometimes I get failures several nights in a row.
 
The same problem. DELL R320 PERC H710 Mini.
Source disk is HW RAID6 - persistent.

Backup VM manually from GUI without any problems, via Backup scheduled task "no such volume 'local-lvm: vm-1061-disk-0", etc.

========================================
proxmox-ve: 5.4-1 (running kernel: 4.15.18-15-pve)
pve-manager: 5.4-6 (running version: 5.4-6/aa7856c5)
pve-kernel-4.15: 5.4-3
pve-kernel-4.15.18-15-pve: 4.15.18-40
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
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.1-10
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-52
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-43
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-37
pve-container: 2.0-39
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-2
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-52
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

===========================

update:

If I create a backup scheduled task for each virtual, backup run without problems.
 
Last edited:
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back