We have a Hyper-V 3.0 Failover Cluster (2 servers) each running Windows Server 2012 RC. We have Shared Storage (HP P4300) which is reporting no errors and is working just fine as either a standalone disk or witness disk within the cluster. We have also installed the HP P4000 DSM which is also working fine (this is on one of the Hyper-V nodes and has full access to the disk).
The issue is that when we add the Cluster Disk (which initially reports as
Online with 'Available Storage' status) as a Cluster Shared Volume, it briefly reports as
Online until reverting to
Online (No Access). They do not appear in
C:\ClusterStorage as they should on either of the member nodes. There are no errors or warnings in the log and the only informational message is that the disk was brought online.
To further confuse things, enabling 'Maintenance Mode' on the disk changes the status to
Online (Maintenance Mode) and the disk now appears in
C:\ClusterStorage (on the node where the cluster disk is located) and allows read/write access just fine.
There doesn't appear to be any information regarding
Online (No Access) on the internet, so any information at all would be very much appreciated right now.
Results of a 'Validate Cluster' only brought back the following relevant errors:
Successfully issued call to Persistent Reservation REGISTER using Invalid RESERVATION KEY 0xc, SERVICE ACTION RESERVATION KEY 0xd, for Test Disk 0 from node PRODHV1.prodhv.local.
Test Disk 0 does not support SCSI-3 Persistent Reservations commands needed to support clustered Storage Pools. 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.
These errors do seem most relevant to the issue and would probably cause it, although the P4300 supports SCSI-3 as far as I can tell. (source)
EDIT: Just some more information to fuel the fire, this works perfectly well on Server 2008 R2, so I know that SCSI-3 is actually supported on the device. Whether the DSM Driver works well under 2012 or not is a different matter, but it may well be that.