topic SCSI-3 Persistent Reservation Error - Hyper-V Cluster with MSA 2060 in MSA Storage

SCSI-3 Persistent Reservation Error - Hyper-V Cluster with MSA 2060

ccsdtech — Thu, 05 Dec 2024 01:17:22 GMT

I am attempting to create a Hyper-V cluster on Windows Server 2025. My two hosts are DL360 Gen11 and storage is MSA 2060 SAS. The servers are connected directly to the MSA... server 1 to ports A1 and B1, and server 2 to ports A3 and B3. The hosts are configured and grouped properly in the MSA. Volumes are created and mapped to the hosts.

When I run the Hyper-V cluster validation, I am receiving SCSI-3 Persistent Reservation errors on the three volumes from the MSA as shown below. Does the MSA 2060 support persistent reservations and if so how do I enable that feature? Thanks for any help!

Node CCSDVM4.clairton.local successfully issued call to Persistent Reservation RESERVE for Test Disk 1 which is currently reserved by node CCSDVM5.clairton.local. This call is expected to fail.
Node CCSDVM4.clairton.local successfully issued call to Persistent Reservation RESERVE for Test Disk 0 which is currently reserved by node CCSDVM5.clairton.local. This call is expected to fail.
Node CCSDVM4.clairton.local successfully issued call to Persistent Reservation RESERVE for Test Disk 2 which is currently reserved by node CCSDVM5.clairton.local. This call is expected to fail.
Test Disk 0 does not provide Persistent Reservations support for the mechanisms used by failover clusters. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.
Test Disk 1 does not provide Persistent Reservations support for the mechanisms used by failover clusters. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.
Test Disk 2 does not provide Persistent Reservations support for the mechanisms used by failover clusters. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.

Re: SCSI-3 Persistent Reservation Error - Hyper-V Cluster with MSA 2060

BPSingh — Wed, 04 Dec 2024 05:12:08 GMT

The MSA is a block-level device and does not provide an option to enable or disable persistent reservations. This issue needs to be investigated at the operating system level.

Re: SCSI-3 Persistent Reservation Error - Hyper-V Cluster with MSA 2060

ccsdtech — Wed, 04 Dec 2024 14:03:43 GMT

Thanks for the reply. I was actually just able to get this resolved yesterday by reinstalling Windows Server on the hosts. I think the issue may have originated due to incorrect SAS cabling between the hosts and the MSA during initial configuration. I did eventually correct that, but I think MPIO in Windows was already confused/broken by then. In any case, I'm good now. Thanks!

Re: SCSI-3 Persistent Reservation Error - Hyper-V Cluster with MSA 2060

Sunitha_Mod — Thu, 05 Dec 2024 07:38:22 GMT

Hello @ccsdtech,

That's Excellent!

We are extremely glad to know the issue has been resolved and we appreciate you for keeping us updated.

Re: SCSI-3 Persistent Reservation Error - Hyper-V Cluster with MSA 2060

pmcfee2924 — Wed, 28 May 2025 12:55:49 GMT

We had the same issue when setting up a Server 2025 failover cluster for Hyper-V on 2, ProLiant DL380 Gen 11 servers with a Smart array E208-p Gen 10 storage controller, direct attach SAS MSA 2070. When a server was rebooted it would take down the cluster and corrupt the VMs. After collecting logs the driver had to be updated.

-All the vms had to be moved to a single host with a single volume (from the MSA), and then the controller driver was installed on the 2nd server.

Run the failover cluster validation report, and it should pass instead of fail.

erver 2025.

-After installing the driver on a single host, all the vms had to be moved to the other host, and then the controller driver was installed.

HPE Smart Array Gen10, Gen10Plus and Gen11 Controller Driver for Windows Server 2019, Windows Server 2022 and Windows Server 2025 Version: 1016.10.0.1004 (17 Mar 2025) Enhancements

Added support for Windows Server 2025.
Added support to enable DMA remapping feature for Windows Server 2025.

https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_645dd55692614fcfad194b731b&tab=revisionHistory