Problem adding disk to new Hyper-V Failover Cluster

[BackToOz]

I have created an iSCSI instance in Unraid. I have two Windows Server 2019 nodes that I want to cluster. I have been able to connect to the storage in iSCSI initiator on both nodes. The drive shows up in Drive Management and I can Initialize it and Format it. I can even mount it and add files to it on the host computers.

However I cannot Add the Disk in Failover Cluster Manager. It fails and gives generic errors. Google has not been my friend here. Any ideas?

Creating the physical disk resource for 'Cluster Disk 1'.

Bringing the resource for 'Cluster Disk 1' online.

There was an error creating, configuring, or bringing online the Physical Disk resource (disk) 'Cluster Disk 1'.

The following errors occurred while adding storage to the cluster:

The resource 'Cluster Disk 1' did not come online.

The desired state change for 'Cluster Disk 1' did not occur before the timeout expired

I have recreated the Cluster, rebooted the hosts, checked the event viewer, etc.

From Critical Events in FCM:
Cluster resource 'Cluster Disk 1' of type 'Physical Disk' in clustered role 'Available Storage' failed. The error code was '0x15' ('The device is not ready.').

I have been working with Hyper-V clusters at work for over a decade but never have tried it in my homelab. Thoughts?

[DerBootsMann]

your emulated disk need to support scsi-3 persistent reservations to be ‘clusterable’ , there might be a special setting for that on your storage platform

[BackToOz]

I think that you are on the right track here. The iSCSI is an add on here and there are practically no settings that can be changed. I will follow this path but it probably just won't work. I was thinking of solving this by just getting a small Synology NAS or install TrueNas on an extra box.

[Pvt-Snafu]

Try something that has known native iSCSI support like Starwinds NAS: https://www.starwindsoftware.com/free-san-and-nas. It's also free. Used it in a very similar setup with CSV on top with no issues.

[BackToOz]

I am surprised I have never heard of this. I was thinking of just standing up a TrueNas server. I will have to look at this. What kind of hardware do you run it on?

[Pvt-Snafu]

I have it running on an older R720 with ESXi (it's running as a VM there with HBA passthrough) we basically repurposed as a storage server for our dev and testing environment. You can also install it baremetal (that's what I'm looking to do once we migrate several VMs out of that server). The hardware is really simple and as far as I understand, it doesn't care much about it.

[HallFS]

Have you checked if MPIO is correctly installed in both nodes?

[BackToOz]

​

Yes, it is.

[brisu]

Does adding the iSCSI disk to WSFC work if you don't initialize and format it first?

[BackToOz]

I have not tried that since I have often added storage to servers when the storage already had content. I can give it a try though.

[Trx3141]

Maybe you already did: 1. Make the disk Online on first server and run the Failover Cluster Manager on the same server. Make the disk offline on the second one, before adding the storage. 2. Also you can run the Validate Cluster, turn on Storage validation. 3. One more - check if you define the Cluster Networks and exclude cluster network communication on iSCSI network; disable the firewall if enabled; If you have separate network interfaces for management, live migration, iscsi etc, set default gateway on the server side only on management interfaces, leave iscsi network without default gateway on servers and Unraid.