iSCSI allows access to a remote server (target) disk by making it virtually available as a local disk. When you configure iSCSI SAN, the iSCSI target Server is configured and therefore offers access to the shared storage. The server that connects to the iSCSI Target is referred to as the iSCSI Initiator. Below are some related HyperV guides: HyperV – Unable to create a new VM, Unable to shutdown a HyperV Virtual Machine, Backup: How to create a HyperV checkpoint, Unable to PXE boot a HyperV VM: F12 key does not work anymore, A boot image was not found for HyperV Virtual Machine, and Pass-Through Authentication Authentication and ADFS environment setup on Hyper-V for Hybrid Identity integration. In this article, you will learn how to fix No disks suitable for the cluster were found.
Why was the error “Fix No disks suitable for the cluster were found” prompted?
No disks suitable for the cluster were found: For diagnostic info about disks available for the cluster, use the Validate a Configuration Wizard to run Storage tests. See the following guide on how to install and configure iSCSI Target Server and iSCSI Initiator on a Windows Server, Quarantine state in Windows Failover Clusters: How to resolve quarantined Cluster Node on Hyper-V, how to fix DNS Bad key 9017: The Cluster Name registration failed of one or more associated DNS names,
While configuring a failover cluster, you may occasionally get the following error “No disks suitable for cluster disks were found as shown in the figure below. For diagnostic information about disks available for the cluster, use the Validate a Configuration Wizard to run Storage tests”.
For your Information Only: It was suggested from the image above for a storage test. As you can see, I ran a validation check on the storage and it passed successfully. Please see How to install and configure Hyper-V Cluster On Windows Server via PowerShell and Server Manager, and Failover Cluster Manager failed while managing one or more clusters, the error was unable to determine if the computer exists in the domain.
The solution to fixing No disks suitable for the cluster were found
The cluster disks are unavailable and also, not important for your cluster configuration. This is why the message is being prompted.
There should be no cluster disks if you have a 2-node Failover Cluster instance. There should be only local disks, no cluster disks. None of the disks should be chosen by cluster disks. The cluster validation wizard is warning you that the cluster disks are inaccessible and not recognized.
For SQL Server: If you have required (utilized) cluster disks, you have to uninstall the SQL Server, fix disk configuration, and then install SQL Server freshly
I hope you found this blog post helpful on how to fix No disks suitable for the cluster were found. If you have any questions, please let me know in the comment session.