Please check if the following information could be of help:
Generally, the issue can be caused by one of these situations:
If you are attempting to set up a Cluster in a Single Host, and the shared disk (or disks) for the cluster is RDM (Raw Device Mapping, or Raw Disk Mapping), in Physical Compatibility Mode. If this is the case, you can either change the disks to Virtual Compatibility mode, or if you wish to use Physical Compatibility Mode, the cluster nodes must be on different hosts.
If the storage array is not configured correctly to support SCSI-3 compliant commands.
A third-party plug-in is interfering with the SCSI reservation process (such as the PowerPath/VE PSA).
If virtual machines are running under the MSCS configuration on two separate ESX/ESXi hosts, and the .vmdk files are on a VMFS datastore which is configured as physical bus sharing mode. (This configuration of CAB is unsupported). For more information, see the Cluster Virtual Machines on One Physical Host section of the Setup for Failover Clustering and Microsoft Cluster Service Guide.
(Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.)
Thanks for your time!
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.