Thanks for the help! doing the upgrade on all three nodes has triggered the sync. I'll let you know how it goes. I didn't need a new key either

Storage is fine, however we have a planned maintenance window to replace the drive which is part of a RAID 1 and only used for the OS. The VSAN Array is fine and is a RAID 10 so even if the drive failed the VSAN would be okay so I am not sure the problem " Due to delays, StarWind VSAN can't syn...

Sure

Node 2 https://drive.google.com/file/d/1-DIfVN ... sp=sharing

Node 1 https://drive.google.com/file/d/1oW-TTa ... sp=sharing

Sure, Uploaded here https://drive.google.com/file/d/1mE_8BV ... sp=sharing

I have restarted the service and the entire node on multiple occasions. I don't have support anymore the cost to Bring them up to support would cost the same as a physical SAN :( I am wondering now if the problem isn't Node 3 Here are the iSCSI connections on all three Node 1: cluster_node_1.xxxxx N...

The other nodes are fine Node 1 can connect to itself and 2 and 2 can connect to itself and node 1 Node 3 is having the problem connecting to itself, 1 and 2 Favorites tab attached: iSCSI Favorites.jpg I read the article however Node 1 and 2 that are fine do not give the “Mark as Synchronized” optio...

My issue is almost exactly like in https://forums.starwindsoftware.com/viewtopic.php?f=5&t=4792 However the difference is that I have a 3 node cluster. After a reboot the node came up with the iSCSI targets for the Witness and the Volume inactive. I tried all of the Microsoft debugging but when ...