Validate SCSI-3 Persistent Reservation error

Piloto 6 Reputation points

I'm creating a Windows 2016 cluster with 2 nodes and a couple of shared disks from a 3PAR 8440 and the cluster validation is failing with the following warning from both nodes:

"The test has detected that the Presistent Reservation command took longer than 3 seconds to complete. This may impact cluster stability."

If I ignore the warning and proceed to create the cluster it takes a long time and then it fails with these errors:

Creating the physical disk resource for 'Cluster Disk 1'.

Bringing the resource for 'Cluster Disk 1' online.

There was an error creating, configuring, or bringing online the Physical Disk resource (disk) 'Cluster Disk 1'.

Creating the physical disk resource for 'Cluster Disk 2'.

Bringing the resource for 'Cluster Disk 2' online.

There was an error creating, configuring, or bringing online the Physical Disk resource (disk) 'Cluster Disk 2'.

In the past I was able to create similar configurations in Windows 2012 R2 with no issues. Any suggestion?

Thank you.

Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
941 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Xiaowei He 9,866 Reputation points


    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!
    Best Regards,


    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.

    0 comments No comments

  2. Piloto 6 Reputation points

    I'm setting the windows cluster with two nodes. I'm no sure how to change the disk mode in windows (this might apply to VMware), I don't have VMware, I just want to configure a basic Windows 2016 cluster with a couple of clustered disks from a SAN. Disk are RAID 6, SAN is a 3PAR 8440.

    0 comments No comments

  3. Alex Bykovskyi 1,351 Reputation points


    Did you initialize the connected drives as NTFS or ReFS on the hosts before running the validation? It is required for Failover Cluster.
    Another thing, did you configure MPIO properties with 3par? You can find more information here:

    I haven't found full Failover Cluster configuration guide with 3par, but the following guide might help:


    Alex Bykovskyi

    StarWind Software

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    0 comments No comments

  4. Piloto 6 Reputation points

    Hi Alex,
    I did initialize the drives as NTFS in the first node and verified they were visible in the second node from Disk Management. I did configure MPIO by adding the 3PARdataVV id to the device list. The option Patch Verify Enable is not checked since I understand that this is for multisite deployments. I checked the guide in the second link but could find anything there. Any other suggestion?
    Thank you,

    0 comments No comments