Cannot add cluster disk on windows 2012

Question

I have 2 servers connected to a shared storage array using Fibre Channel.  Currently there are 2 luns on the storage device.  
From the Failover Cluster Manager, when I select “Add Disk” from Storage – Disks, both luns show up and I can add them without problems.  But if I choose to only
add one of them first (it doesn't make a difference which one is added first), then it will not allow adding the second one later.  I get a message: "No disks suitable for cluster disks were found. For diagnostic information about disks available to the
cluster, use Validate a Configuration Wizard to run Storage tests."
When I do add one (or both disks at the same time), they work just fine for failover clustering.
I can’t imagine this is by design. Is this a known/unknown issue, or is there something special that needs to be done?
Thanks

Answer 1

Ok, no problem. I run the validation tests (Validate Cluster - Storage only) and I received the details shown below. I can clearly see that Cluster Validation tool does not find any disk suitable for 2012 cluster, and even I can see why (it is plain English).
Unfortunately this still does not explain how to fix the problem. Recommendations like "run Clear-ClusterDiskReservation PowerShell cmdlet to remove the Persistent Reservation from the disk" do not work - this discussion is available in another thread where
people having the same issue and no luck so far. I guess that I'm using old SAN (and I know that) that simply does not support SCSI-3 persistent reservation so those disks cannot be used in 2012 cluster. Oh well, will have to wait fro new SAN and then I can
play again...
Validation test results:
Physical disk with identifier {95059d50-a173-49bd-b029-fec326acd78c} has an existing Persistent Reservation placed on it, and will be removed from the validation set. This disk may already be clustered, on a different cluster or in use by another system.
Please verify the storage configuration and LUN zoning. If you wish to cluster this disk, you can use the Clear-ClusterDiskReservation PowerShell cmdlet to remove the Persistent Reservation from the disk.
Physical disk with identifier {0b301c72-c88f-47ee-9389-11efdeed6cdb} has an existing Persistent Reservation placed on it, and will be removed from the validation set. This disk may already be clustered, on a different cluster or in use by another system.
Please verify the storage configuration and LUN zoning. If you wish to cluster this disk, you can use the Clear-ClusterDiskReservation PowerShell cmdlet to remove the Persistent Reservation from the disk.
Physical disk with identifier {eec0be37-5dfe-47f7-a149-4f1dec18450b} has an existing Persistent Reservation placed on it, and will be removed from the validation set. This disk may already be clustered, on a different cluster or in use by another system.
Please verify the storage configuration and LUN zoning. If you wish to cluster this disk, you can use the Clear-ClusterDiskReservation PowerShell cmdlet to remove the Persistent Reservation from the disk.
Physical disk with identifier {dcb8b1fe-7671-41c9-b996-da26c0b93751} has an existing Persistent Reservation placed on it, and will be removed from the validation set. This disk may already be clustered, on a different cluster or in use by another system.
Please verify the storage configuration and LUN zoning. If you wish to cluster this disk, you can use the Clear-ClusterDiskReservation PowerShell cmdlet to remove the Persistent Reservation from the disk.
No disks were found on which to perform cluster validation tests. To correct this, review the following possible causes:
* The disks are already clustered and currently Online in the cluster. When testing a working cluster, ensure that the disks that you want to test are Offline in the cluster.
* The disks are unsuitable for clustering. Boot volumes, system volumes, disks used for paging or dump files, etc., are examples of disks unsuitable for clustering.
* Review the "List Disks" test. Ensure that the disks you want to test are unmasked, that is, your masking or zoning does not prevent access to the disks. If the disks seem to be unmasked or zoned correctly but could not be tested, try restarting the servers
before running the validation tests again.
* The cluster does not use shared storage. A cluster must use a hardware solution based either on shared storage or on replication between nodes. If your solution is based on replication between nodes, you do not need to rerun Storage tests. Instead, work
with the provider of your replication solution to ensure that replicated copies of the cluster configuration database can be maintained across the nodes.
* The disks are Online in the cluster and are in maintenance mode. No disks were found on which to perform cluster validation tests.