Hello All,
Kindly need your help to solve this error..
Btw thank you for this fantastic product
Since yesterday night I have got error in the scheduled backup and also have tried did manual backup had same error.
Error happen to all VMs which the VMs disk were in local-lvm.
When do backup to VM which the VM disk is in NAS(NFS) there is no issue.
Before this error happen I did import .ova on yesterday afternoon, did convert vmdk to qcow2 to local-lvm
I have tried
-Shutdown the VM, then did manual backup same error.
-No issue on start/stop VM
-Able to did VM snapshot
-Did recreate backup schedule same error
Here is the error
lv display find associated LV
Kindly need your help to solve this error..
Btw thank you for this fantastic product
Since yesterday night I have got error in the scheduled backup and also have tried did manual backup had same error.
Error happen to all VMs which the VMs disk were in local-lvm.
When do backup to VM which the VM disk is in NAS(NFS) there is no issue.
Before this error happen I did import .ova on yesterday afternoon, did convert vmdk to qcow2 to local-lvm
I have tried
-Shutdown the VM, then did manual backup same error.
-No issue on start/stop VM
-Able to did VM snapshot
-Did recreate backup schedule same error
Here is the error
Code:
INFO: starting new backup job: vzdump 113 --mailto someone@me --node svrproxmox --storage BackupNAS --remove 0 --mode snapshot --compress lzo
INFO: Starting Backup of VM 113 (qemu)
INFO: Backup started at 2021-01-20 17:06:16
INFO: status = running
INFO: update VM 113: -lock backup
INFO: VM Name: OSTICKET-DEV
INFO: include disk 'scsi0' 'local-lvm:vm-113-disk-0' 50G
WARNING: Device /dev/dm-9 not initialized in udev database even after waiting 10000000 microseconds.
ERROR: Backup of VM 113 failed - no such volume 'local-lvm:vm-113-disk-0'
INFO: Failed at 2021-01-20 17:06:33
INFO: Backup job finished with errors
TASK ERROR: job errorslv display find associated LV
Code:
--- Logical volume ---
LV Path /dev/pve/vm-113-disk-0
LV Name vm-113-disk-0
VG Name pve
LV UUID ggxdwP-e3yU-Iu6A-ZWem-2qfQ-ycHU-WPfy3I
LV Write Access read/write
LV Creation host, time svrproxmox, 2020-03-09 11:46:06 +0700
LV Pool name data
LV Status available
# open 1
LV Size 50.00 GiB
Mapped size 4.51%
Current LE 12800
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:16
Code:
root@svrproxmox:/tmp# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)
pve-kernel-5.0: 6.0-5
pve-kernel-helper: 6.0-5
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph: 14.2.6-pve1
ceph-fuse: 14.2.6-pve1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-2
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-5
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-3
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-5
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-5
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1
root@svrproxmox:/tmp#