Hey,
Did you run cluster validation? It might disconnect and connect iSCSI target. You can also restart iSCSI Target Server.
Alternatively, disconnect your targets in iSCSI initiator and connect them again. https://social.technet.microsoft.com/Forums/en-US/32c814da-6799-47f6-bfef-695f01cd3916/iscsi-not-initially-reconnecting-after-reboot?forum=winserverfiles
If you use node for both iSCSI storage and compute, it will be a single point of failure. In case this node fails, entire cluster will go down. You will need shared storage to make 2 nodes redundant. You can use Storage Space Direct as a shared storage.
https://learn.microsoft.com/en-us/azure-stack/hci/concepts/nested-resiliency
As another option, StarWind VSAN can be used. It will create replicated storage pool between 2 nodes, which can be used to create Failover Cluster. Might help: https://www.starwindsoftware.com/starwind-virtual-san
https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyperconverged-scenario-with-windows-server-2016/
Cheers,
Alex Bykovskyi
StarWind Software
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.