Disk not found on new VM

[CharlesErickT]

Hello,

Either when adding a disk to an existing VM or when creating a new VM, I'm not able to start the said VM.

I've added a second disk to an existing VM (# 124) and starting it gives me the following error:

kvm: -drive file=/dev/zvol/rpool/data/vm-124-disk-2,if=none,id=drive-scsi1,cache=writeback,discard=on,format=raw,aio=threads,detect-zeroes=unmap: Could not open '/dev/zvol/rpool/data/vm-124-disk-2': No such file or directory
TASK ERROR: start failed: command '/usr/bin/kvm -id 124 -chardev 'socket,id=qmp,path=/var/run/qemu-server/124.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/124.pid -daemonize -smbios 'type=1,uuid=23f5ce50-aceb-46e5-891f-681a6e1e3f81' -name dev-fmclt-1 -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/124.vnc,x509,password -no-hpet -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed' -m 8192 -k en-us -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -chardev 'socket,path=/var/run/qemu-server/124.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:ab016ab396' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/zvol/rpool/data/vm-124-disk-2,if=none,id=drive-scsi1,cache=writeback,discard=on,format=raw,aio=threads,detect-zeroes=unmap' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1' -drive 'file=/dev/zvol/rpool/data/vm-124-disk-1,if=none,id=drive-virtio0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=101' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/mnt/dev-nas-1/Proxmox/template/iso/virtio-win-0.1.141.iso,if=none,id=drive-sata2,media=cdrom,aio=threads' -device 'ide-drive,bus=ahci0.2,drive=drive-sata2,id=sata2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap124i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=A6:1F:95:07:59:EF,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1

From the webui I can clearly see the disk fine.

ZFS list also show the disk #2

rpool/data/vm-124-disk-1      83.0G  1.34T  83.0G  -
rpool/data/vm-124-disk-2        56K  1.34T    56K  -

but the file does not exist in /dev/zvol/rpool/data

lrwxrwxrwx 1 root root  13 Nov  9 14:55 vm-124-disk-1 -> ../../../zd16
lrwxrwxrwx 1 root root  15 Nov  9 14:55 vm-124-disk-1-part1 -> ../../../zd16p1
lrwxrwxrwx 1 root root  15 Nov  9 14:55 vm-124-disk-1-part2 -> ../../../zd16p2
lrwxrwxrwx 1 root root  13 Nov  9 14:55 vm-128-disk-1 -> ../../../zd32
lrwxrwxrwx 1 root root  13 Nov  9 14:55 vm-140-disk-1 -> ../../../zd48
lrwxrwxrwx 1 root root  13 Nov  9 14:55 vm-141-disk-1 -> ../../../zd64
lrwxrwxrwx 1 root root  13 Nov  9 14:55 vm-141-disk-2 -> ../../../zd80
lrwxrwxrwx 1 root root  13 Nov  9 14:55 vm-141-disk-3 -> ../../../zd96

Any idea what might cause this ?

Here's my pveversion

proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-35 (running version: 5.1-35/722cc488)
pve-kernel-4.13.4-1-pve: 4.13.4-25
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90

Thanks

 

[wolfgang]

Hi,

How did you add this disk?
I think it is a filesystem and no volume

zfs list  -o type  rpool/data/vm-124-disk-2

 

[CharlesErickT]

The disk was finally created after some time. I don't know if this is on some sort of timer or navigating trough the webui that forced something but after a couples of minute the disk was there. I tried reproducing the issue but no luck. I will update this thread if it ever happen again

Thanks for the help