[SOLVED] Unable to parse volume ID

[Marcel Fuhrmann]

Hi!

I've wanted to resize the virtio1 disk of this VM:

[13:37]root@frapevh004:/etc/pve/qemu-server# cat 167.conf 
agent: 1
boot: order=virtio0;net0
cores: 1
memory: 32768
name: frapelogdb001-n4
net0: virtio=6E:A5:69:CE:5B:EA,bridge=vmbr300
numa: 0
onboot: 1
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=a2eb0072-5eb1-4e60-a5cd-6b5ebe9f0ced
sockets: 4
startup: order=20,up=3
virtio0: vm_local:167/vm-167-disk-0.qcow2,size=20G
virtio1: /dev/sas1/frapelogdb-n4,size=2T

But `qm` command (and also the web UI) complains about it (see title).
I've turned the VM off and added a config change like

[PENDING]
virtio1: frapelogdb-n4,size=2T

But the VM didn't start anymore. The UI didn't gave a specific error message.

I am wondering I have to write this line to point to an LV.

I know entries like this work perfectly:

virtio0: vm_local:167/vm-167-disk-0.qcow2,size=20G

(vm_local is an LV)
or

virtio0: sas1:vm-235-disk-0,cache=writeback
(sas1 is a VG and vm-235-disk-0 is an LV).

(sas1 is a VG and vm-235-disk-0 is an LV).


Here some LVS information:

[13:50]root@frapevh004:~# vgs
  VG    #PV #LV #SN Attr   VSize   VFree 
sas1    1  11   0 wz--n-  26.19t   9.77t
vmsys   1   2   0 wz--n- 222.06g 200.06g
[13:50]root@frapevh004:~# lvs
LV            VG    Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
frapelogdb-n4 sas1  -wi-ao----   2.00t                                                   
osd1          sas1  -wi-ao----   4.00t                                                   
perfentesten  sas1  -wi-a----- 100.00g                                                   
vm-111-disk-0 sas1  -wi-ao----   3.42t                                                   
vm-207-disk-0 sas1  -wi-ao----   2.00t                                                   
vm-238-disk-0 sas1  -wi-ao---- 180.00g                                                   
vm-258-disk-0 sas1  -wi-ao----   3.42t                                                   
vm-262-disk-0 sas1  -wi-ao----  20.00g                                                   
vm-320-disk-0 sas1  -wi-ao---- 100.00g                                                   
vm-343-disk-0 sas1  -wi-ao---- 200.00g                                                   
vm_local      sas1  -wi-ao----   1.00t                                                   
root          vmsys -wi-ao----  20.00g                                                   
varlog        vmsys -wi-ao----   2.00g                                                   
[13:50]root@frapevh004:~# ll /dev/sas1/frapelogdb-n4 
lrwxrwxrwx 1 root root 7 Dec 1 13:17 /dev/sas1/frapelogdb-n4 -> ../dm-6

Greetings

 

[Marcel Fuhrmann]

I found a solution.
Detaching the disk

virtio1: /dev/sas1/frapelogdb-n4,size=2T

lvrename sas1 frapelogdb-n4 vm-167-disk-1
qm rescan

Then you are able to attache the disk via the web UI and also able to resize it.