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.
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". See the following guide on how to install and configure iSCSI Target Server and iSCSI Initiator on a Windows Server.
For your Information Only: It was suggested from the image above to a storage test. As you can see, I ran a validation check on the storage and it passed successfully.
Solution: 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. If you have any questions, please let me know in the comment session.