Hi there, I have just set up a 1.5.1 single node test harvester node. I was able to create one vm originally. i have since made some changes to replica count for longhorn, rancher addon etc. Now when I try and create a vm, it seems to have issues mapping the drives. longhorn is not showing any errors . This is the type of error I'm getting:

MapVolume.MapPodDevice failed for volume "pvc-ba769b7a-6091-4495-afa3-b41045d7646b" : rpc error: code = Internal desc = failed to bind mount "/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc-ba769b7a-6091-4495-afa3-b41045d7646b/pvc-ba769b7a-6091-4495-afa3-b41045d7646b" at "/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc-ba769b7a-6091-4495-afa3-b41045d7646b/111898b6-fadb-46ca-ade2-8432f0b0f6fd": mount failed: exit status 32 Mounting command: mount Mounting arguments: -o bind /var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc-ba769b7a-6091-4495-afa3-b41045d7646b/pvc-ba769b7a-6091-4495-afa3-b41045d7646b /var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc-ba769b7a-6091-4495-afa3-b41045d7646b/111898b6-fadb-46ca-ade2-8432f0b0f6fd Output: mount: /var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/publish/pvc-ba769b7a-6091-4495-afa3-b41045d7646b/111898b6-fadb-46ca-ade2-8432f0b0f6fd: special device /var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/staging/pvc-ba769b7a-6091-4495-afa3-b41045d7646b/pvc-ba769b7a-6091-4495-afa3-b41045d7646b does not exist. dmesg(1) may have more information after failed mount system call.

did you remove and readd the image?

Yeah I tried that also ended up doing the same thing

did you create a new storageclass or update the old one?

I cloned the existing and changed, Maybe that was the issue? ``````

Maybe. Try creating a new one.

Thank you Andy, I went back to using the 2 replica default but it did the same thing

Try reinstalling and changing the default to 1 replica before you load any images.

So worked this out, it was because I was selecting migratable: false when creating the storage class. I thought since i was setting the replica count to 1, that made sense but obviously not 😄 . will just have to make those decisions on the vm settings

Interesting.