TASK ERROR: error during cfs-locked 'storage-nfs' operation: disk image '/mnt/pve/nfs-10g/images/101/vm-101-cloudinit.qcow2' already exists


New Member
Sep 14, 2020
Hi, im getting error
TASK ERROR: error during cfs-locked 'storage-nfs' operation: disk image '/mnt/pve/nfs-10g/images/101/vm-101-cloudinit.qcow2' already exists
durning VM startup after node reboot. VM is set to start automatically, but it wont. After starting vm through web ui vm starts without problem. I dont have to delete any files etc.
Both cloud-init and main image are on nfs share on freenas box.
Below is pveversion -v output:
proxmox-ve: 6.2-1 (running kernel: 5.4.60-1-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-6
pve-kernel-helper: 6.2-6
pve-kernel-5.4.60-1-pve: 5.4.60-2
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve2
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-12
pve-cluster: 6.1-8
pve-container: 3.2-1
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-1
pve-qemu-kvm: 5.1.0-1
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-14
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1


New Member
Sep 14, 2020
Hi !

I think I have the same problem at 90%. I'm trying to clone a VM from template. Without the cloudinit configuration, the VM boot normally. But if I apply the cloudinit configuration, the VM will not boot AND the cloudinit conf is'nt applied ! In the Web UI, I have these lines : Capture d’écran, le 2020-09-16 à 19.55.17.png

As you can see, the disk is'nt correct for PVE, the config is not applied, so the VM can boot, but with the wrong config...

This is the part of the script I'm using for apply the cloudinit's config :

curl -k --cookie "$(<cookie)" -H "$(<csrftoken)" \
--data-urlencode "ipconfig0=ip=$2/32,gw=MYGATEWAY" \
--data-urlencode "ide2=local:cloudinit,media=cdrom" \
--data-urlencode "keyboard=fr" \
--data-urlencode "memory=$VM_MEMORY" \
--data-urlencode "nameserver=,,2600:4700:4700::1111,2600:4700:4700::1001" \
--data-urlencode "vcpus=4" \
--data-urlencode "net0=virtio=$MAC_ADDRESS,bridge=vmbr0" \
Hope someone will be able to help.

Thanks everyone,



The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

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 your own in 60 seconds.

Buy now!