[SOLVED] ERROR: Backup of VM 104 failed - no such volume

R

rvdk92

Active Member
Nov 8, 2020
68
3
28
33
Hello,

I have a strange problem.. from 1 of the 3 pve servers my backup doesn't work..

when i start the backup from all of the vm's on that node i get the following error:


INFO: starting new backup job: vzdump 104 --node pve-a03 --storage pbs-a02 --remove 0 --mode snapshot INFO: Starting Backup of VM 104 (qemu) INFO: Backup started at 2021-02-09 20:53:51 INFO: status = running INFO: VM Name: xxxxxxx INFO: include disk 'ide0' 'DATASTORE03:vm-104-disk-0' 80G /dev/sdc: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdc: open failed: No medium found ERROR: Backup of VM 104 failed - no such volume 'DATASTORE03:vm-104-disk-0' INFO: Failed at 2021-02-09 20:54:25 INFO: Backup job finished with errors TASK ERROR: job errors


All my packeges are up to date.. the same of the other 2 nodes..

I have tried to remove all of my backup's of the vm's en configure again the backup job.. but doesn't help.

i backup to a proxmox-backup-server, but problem is also to local storage.

When i migrate my vm to another node than the backup works.

how can i resolved this issue on this node withouth restart my node?
 
Can you please use the [code][/code] tags or the </> format button to post the following?
Code: 
cat /etc/pve/qemu-server/104.conf
cat /etc/pve/storage.cfg
cat /etc/pve/vzdump.cron
pvecm status
fdisk -l
 
Dominic said:
Can you please use the [code][/code] tags or the </> format button to post the following?
Code: 
cat /etc/pve/qemu-server/104.conf
cat /etc/pve/storage.cfg
cat /etc/pve/vzdump.cron
pvecm status
fdisk -l
Click to expand...
yes thank you:

cat /etc/pve/qemu-server/104.conf

Code: 
root@pve-a03:~# cat /etc/pve/qemu-server/104.conf
agent: 1
boot: order=ide0
cores: 2
ide0: DATASTORE03:vm-104-disk-0,format=raw,size=80G
memory: 4096
name: hosting
net0: vmxnet3=DE:EC:62:5B:F9:EB,bridge=vmbr0,tag=10
ostype: l26
scsihw: pvscsi
smbios1: uuid=65d3225a-365d-4136-a55b-c996c522ceb1
startup: order=5
vmgenid: 06018c55-10c1-4084-b0d2-dc98ed2d1446

cat /etc/pve/storage.cfg
Code: 
root@pve-a03:~# cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content iso,vztmpl,backup

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

lvm: DATASTORE
        vgname DATASTORE
        content images,rootdir
        nodes pve-m01
        shared 0

nfs: NAS302
        export /volume1/proxmox-meppel
        path /mnt/pve/NAS302
        server 10.1.123.62
        content iso,images
        nodes pve-m01,pve-a02
        prune-backups keep-all=1

pbs: pbs-m01
        datastore NAS302-Meppel
        server 10.1.123.211
        content backup
        fingerprint 10:55:67:88:f5:8f:f3:e9:83:bd:a3:ef:e9:13:b1:47:40:42:21:b1:61:02:a2:88:78:fd:3c:73:48:14:df:e2
        nodes pve-m01
        prune-backups keep-all=1
        username pvecluster@pbs

lvm: DATASTORE02
        vgname DATASTORE02
        content rootdir,images
        nodes pve-a02
        shared 0

nfs: NAS501
        export /volume1/proxmox-apeldoorn
        path /mnt/pve/NAS501
        server 10.1.123.61
        content iso,images
        nodes pve-a02
        prune-backups keep-all=1

pbs: pbs-a02
        datastore NAS501-Apeldoorn
        server 10.1.123.212
        content backup
        fingerprint 38:19:c9:de:40:77:f7:53:5d:e7:2f:5a:a1:8a:a5:3e:59:fe:82:f6:19:95:98:99:e8:ab:f9:4b:31:63:7f:34
        nodes pve-a02,pve-a03
        prune-backups keep-all=1
        username pvecluster@pbs

lvm: DATASTORE03
        vgname DATASTORE03
        content rootdir,images
        nodes pve-a03
        shared 0

cat /etc/pve/vzdump.cron
Code: 
root@pve-a03:~# cat /etc/pve/vzdump.cron
# cluster wide vzdump cron schedule
# Automatically generated file - do not edit

PATH="/usr/sbin:/usr/bin:/sbin:/bin"

0 20 * * *           root vzdump --storage pbs-m01 --exclude 100 --mailto r.vanderkooi..... --quiet 1 --all 1 --mode snapshot --compress zstd --node pve-m01 --mailnotification always
0 22 * * *           root vzdump --mode snapshot --all 1 --mailnotification failure --node pve-a02 --mailto robbert...... --quiet 1 --storage pbs-a02 --exclude 107
0 0 * * *           root vzdump --mailnotification always --node pve-a03 --mode snapshot --all 1 --storage pbs-a02 --quiet 1 --mailto r.vanderkooi.....

pvecm status
Code: 
root@pve-a03:~# pvecm status
Cluster information
-------------------
Name:             pveclushes
Config Version:   3
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Wed Feb 10 09:31:42 2021
Quorum provider:  corosync_votequorum
Nodes:            3
Node ID:          0x00000003
Ring ID:          1.100
Quorate:          Yes

Votequorum information
----------------------
Expected votes:   3
Highest expected: 3
Total votes:      3
Quorum:           2
Flags:            Quorate

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 10.1.123.11
0x00000002          1 10.1.123.12
0x00000003          1 10.1.123.13 (local)

fdisk -l
Code: 
root@pve-a03:~# fdisk -l
Disk /dev/sda: 223.6 GiB, 240021504000 bytes, 468792000 sectors
Disk model: LOGICAL VOLUME
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: E4D4326B-8C61-4F47-8DC9-FB81E4288EE6

Device       Start       End   Sectors  Size Type
/dev/sda1       34      2047      2014 1007K BIOS boot
/dev/sda2     2048   1050623   1048576  512M EFI System
/dev/sda3  1050624 468791966 467741343  223G Linux LVM

Partition 1 does not start on physical sector boundary.


Disk /dev/sdb: 8.2 TiB, 9001677316096 bytes, 17581401008 sectors
Disk model: LOGICAL VOLUME
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 786432 bytes


Disk /dev/sdd: 7.3 GiB, 7823458304 bytes, 15280192 sectors
Disk model: DataTraveler 2.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B8A35F5A-CC98-4F3A-8828-C28222F86139

Device       Start     End Sectors  Size Type
/dev/sdd1       64    8191    8128    4M EFI System
/dev/sdd5     8224  520191  511968  250M Microsoft basic data
/dev/sdd6   520224 1032191  511968  250M Microsoft basic data
/dev/sdd7  1032224 1257471  225248  110M VMware Diagnostic
/dev/sdd8  1257504 1843199  585696  286M Microsoft basic data
/dev/sdd9  1843200 7086079 5242880  2.5G VMware Diagnostic


Disk /dev/mapper/DATASTORE03-vm--111--disk--0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 786432 bytes


Disk /dev/mapper/DATASTORE03-vm--111--disk--1: 80 GiB, 85899345920 bytes, 167772160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 786432 bytes
Disklabel type: gpt
Disk identifier: D7C78C10-7DEA-43CF-9A23-8E88A56C8F77

Device                                           Start       End   Sectors  Size Type
/dev/mapper/DATASTORE03-vm--111--disk--1-part1    2048   1023999   1021952  499M Windows recovery environment
/dev/mapper/DATASTORE03-vm--111--disk--1-part2 1024000   1226751    202752   99M EFI System
/dev/mapper/DATASTORE03-vm--111--disk--1-part3 1226752   1259519     32768   16M Microsoft reserved
/dev/mapper/DATASTORE03-vm--111--disk--1-part4 1259520 167770111 166510592 79.4G Microsoft basic data


Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/pve-root: 55.8 GiB, 59861106688 bytes, 116916224 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/pve-vm--111--disk--0: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: AC17D687-F8EB-4D2A-9AA6-7C41AB9D471F

Device                                 Start      End  Sectors Size Type
/dev/mapper/pve-vm--111--disk--0-part1    34    32767    32734  16M Microsoft reserved
/dev/mapper/pve-vm--111--disk--0-part2 32768 41938943 41906176  20G Microsoft basic data

Partition 1 does not start on physical sector boundary.


Disk /dev/mapper/DATASTORE03-vm--113--disk--0: 120 GiB, 128849018880 bytes, 251658240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 786432 bytes
Disklabel type: dos
Disk identifier: 0x000cb836

Device                                         Boot   Start       End   Sectors  Size Id Type
/dev/mapper/DATASTORE03-vm--113--disk--0-part1 *       2048   2099199   2097152    1G 83 Linux
/dev/mapper/DATASTORE03-vm--113--disk--0-part2      2099200 251658239 249559040  119G 8e Linux LVM


Disk /dev/mapper/DATASTORE03-vm--105--disk--0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 786432 bytes


Disk /dev/mapper/DATASTORE03-vm--105--disk--1: 80 GiB, 85899345920 bytes, 167772160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 786432 bytes
Disklabel type: gpt
Disk identifier: D0D7BEE0-2629-4FF9-A4A2-90040AD3B748

Device                                           Start       End   Sectors  Size Type
/dev/mapper/DATASTORE03-vm--105--disk--1-part1    2048   1023999   1021952  499M Windows recovery environment
/dev/mapper/DATASTORE03-vm--105--disk--1-part2 1024000   1226751    202752   99M EFI System
/dev/mapper/DATASTORE03-vm--105--disk--1-part3 1226752   1259519     32768   16M Microsoft reserved
/dev/mapper/DATASTORE03-vm--105--disk--1-part4 1259520 167770111 166510592 79.4G Microsoft basic data


Disk /dev/mapper/DATASTORE03-vm--115--disk--0: 200 GiB, 214748364800 bytes, 419430400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 786432 bytes
Disklabel type: dos
Disk identifier: 0x000aac76

Device                                         Boot   Start       End   Sectors  Size Id Type
/dev/mapper/DATASTORE03-vm--115--disk--0-part1 *       2048   2099199   2097152    1G 83 Linux
/dev/mapper/DATASTORE03-vm--115--disk--0-part2      2099200 419430399 417331200  199G 8e Linux LVM


Disk /dev/mapper/DATASTORE03-vm--116--disk--0: 120 GiB, 128849018880 bytes, 251658240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 786432 bytes
Disklabel type: dos
Disk identifier: 0x000ce83f

Device                                         Boot   Start       End   Sectors  Size Id Type
/dev/mapper/DATASTORE03-vm--116--disk--0-part1 *       2048   2099199   2097152    1G 83 Linux
/dev/mapper/DATASTORE03-vm--116--disk--0-part2      2099200 251658239 249559040  119G 8e Linux LVM


Disk /dev/mapper/DATASTORE03-vm--104--disk--0: 80 GiB, 85899345920 bytes, 167772160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 786432 bytes
Disklabel type: dos
Disk identifier: 0x000aa164

Device                                         Boot   Start       End   Sectors Size Id Type
/dev/mapper/DATASTORE03-vm--104--disk--0-part1 *       2048   2099199   2097152   1G 83 Linux
/dev/mapper/DATASTORE03-vm--104--disk--0-part2      2099200 167772159 165672960  79G 8e Linux LVM
 
Hi,

I have shutdown my server last night, in de bios disabled usb stick internal (usb stick of VMWare) en restart.. after that my backup running again.

Thanks for the support.
 
  • Like
Reactions: Dominic
You must log in or register to reply here.
Top Bottom