Microsoft Windows Server Failover Clustering is used with the SQL DB server configuration.
A new clustered vmdk is added on one of the VM, however unable to add it live on the other VM.
Receiving below error,
Failed to add disk scsi0:5. Failed to lock the file Cannot open the disk '/vmfs/volumes/vsan:528354dae18e44ec-0dac61c2f9d39acf/5e834268-688a-be51-4e78-bc97e145fc02/vmname.vmdk' or one of the snapshot disks it depends on. Failed to power on scsi0:5.
vCenter 7.x, 8.x
ESXi 7.x, 8.x
Below log entries are seen in vmware.log of the VM,
yyyy-mm-ddThh:mm:ss.970Z In(05) vmx esxi-1054200-auto-mlfd-h5:70184238-c8-01-84-9948 DISKLIB-LIB : Failed to open '/vmfs/volumes/vsan:528354dae18e44ec-0dac61c2f9d39acf/5e834268-688a-be51-4e78-bc97e145fc02/vname.vmdk' with flags 0xa Failed to lock the file (16392).
yyyy-mm-ddThh:mm:ss.970Z Er(02) vmx esxi-1054200-auto-mlfd-h5:70184238-c8-01-84-9948 DISK: Cannot open disk '/vmfs/volumes/vsan:528354dae18e44ec-0dac61c2f9d39acf/5e834268-688a-be51-4e78-bc97e145fc02/vmname.vmdk': Failed to lock the file (16392).
yyyy-mm-ddThh:mm:ss.971Z In(05) vmx esxi-1054200-auto-mlfd-h5:70184238-c8-01-84-9948 DiskHotRemoveAction: Device 'scsi0:5' was not found for hot removal!
yyyy-mm-ddThh:mm:ss.971Z In(05) vmx esxi-1054200-auto-mlfd-h5:70184238-c8-01-84-9948 VigorTransport_ServerSendResponse opID=esxi-1054200-auto-mlfd-h5:70184238-c8-01-84-9948 seq=5410: Completed Disk request with messages.
'SCSI bus sharing' option on the vSCSI controller under both VMs set to 'None'.
'SCSI bus sharing' option on the vSCSI controller under both VMs need to set to 'Physical'.
Powered off both the VMs, set SCSI bus sharing to 'Physical' state.
confirmed 'vSCSI Controller type' is set to one of the supported type