Hi guys,
Now this is the second time i have tried this… our 5 node S2D hyper v cluster have been running without a hickup for over a year now. But this changed when we introduced the new node.
All the nodes are identical. samt patch level (new ish) same firmwares. I join the node into the cluster. and right away i notice that all storage related cmdlets tages several minutes and browsing the clusterstorage shares are slow.
i notice that all storage jobs (add physicaldisk) exits with exception status. and within 30 minutes the node owning the cluster, restarts its cluster service which offline the storagepool and all vm's dies.
im at a loss. i have done several s2d clusters and have never seen this. and everything is looking good prior to joining the new cluster node