Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, January 13, 2018 12:09 AM
Hi guys,
I have a customer that has a vSphere 6.0 with 4 nodes with Microsoft 2016 Server File Server (Cluster). The disks are configured as RDM and physical compatibility and looks like the configuration are made following this doc provide by VMWARE. The cluster is working fine, but we got some warnings on the failover cluster validation report.
My question is, is this safe to ignore or there is something that we miss on the configuration?
This is the warnings on the Storage Category:
This is the warnings on the Storage Category:
List Disks To Be Validated
Physical disk with identifier xxxxxxx 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 xxxxxxx 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 {xxxxxxx - xxxxxxx - xxxxxxx - xxxxxxx - xxxxxxx } 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 xxxxxxx 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 xxxxxxx 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.
Thank you in advance.
All replies (5)
Monday, January 15, 2018 1:08 PM ✅Answered | 1 vote
The second method is definitely a way to clear the issue, but the question is why did this happen in the first place? Too often it comes either from something not being configured correctly in the first place, or something not being handled correctly during the running. The cluster is basically reporting what it is finding. Both issues I list above need to be checked with VMware.
Once you have cleared the error, does the cluster validation report still report warnings on the storage? On a properly configured cluster, there should be no warnings.
Did something happen just prior to you starting to see this error? Power fail? Node failure? If so, can you replicate it? If so, you might want to open a case with VMware to see why it is not properly clearing this.
tim
Wednesday, January 17, 2018 8:45 PM ✅Answered
After checking the cluster configuration and VMWare storage configuration, and test some of the workarounds suggested, the way we have fix the warnings was by configuring MPIO, because we have multi-paths to the storage.
Saturday, January 13, 2018 1:32 PM
Whatever editor you used to enter your post rendered the text mostly unreadable.
But it looks like the bottom line is that your customer needs to contact VMware to ensure they are following VMware's configuration instructions. Disks must be configured exactly according to VMware's specifications before Windows clustering will properly recognize them.
tim
Sunday, January 14, 2018 9:48 AM
Hi Tim,
Looks like the add-on for Grammaly on Edge was replacing the text with another html code! Now I have fix the text after disable the Grammaly add-on.
Regarding this issues, I have take a look on the VMWare configuration and looks like it is well configured, meanwhile I had someone tell me in reddit that the he ran into this before on 2012R2 and used the second method to clear it. Any comment?
Monday, January 15, 2018 9:31 AM
Hi,
According to the validation, that seems still something not correct on your disks.
Which kind of storage device are you using ?
Can you see the disks (luns) in Disk Management on the server?
Please also check articles below
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best Regards,
Mary
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].