Pardon for the delay in updating this thread.
I want to thank StarWind support for being so helpful in resolving this issue. The problem, in short, was due to expiration of a license I didn't realize I was using (see below).
I had originally installed StarWind Free, expecting to have a test cluster fully configured by the time full-function period elapsed. Due to a family emergency I was unable to do so. When I contacted StarWind sales, they were very helpful in providing a replacement license to allow me to complete the configuration, and I am very grateful for that. What I didn't realized was that the replacement license I was provided (for which I was very happy) was not "Free", and when it expired, _all_ StarWind services (not just the GUI) suddenly stopped.
Here are some suggestions for documentation that might help in future:
1. Document license type expiry behavior more clearly. It isn't mentioned in any KB article I could find, including
https://knowledgebase.starwindsoftware. ... g-options/
2. It wouldn't hurt for the GUI interface to SAY somewhere what was going to expire, and when. In this case, when the license expired, the VSAN just totally stopped. No GUI, no iSCSI, no cluster shares, nothing.
3. Reminder: Despite what one might expect, StarWind does NOT use the visible iSCSI targets and services for replication between hosts. Just because those iSCSI targets refuse to connect does NOT mean StarWind cannot synchronize its images. I actually don't know what StarWind uses for synchronization: it seems almost completely hidden.
It might not hurt to explain that, if one host is flagged as "synchonized" (even if its partner is not, which seems an odd way to say it) it will still allow iSCSI target connections to the one that is synced. If neither is flagged as synced, they will not replicate until we tell it which to consider synced, and it will sync the other to it. I don't know of a way to diagnose sync issues if that doesn't work, but looking at iSCSI target statuses isn't it.
Due to the nature of this issue, once I had the new license installed, all images were shown as not synchronized. I did have to flag one of the hosts as synchronized so that replication could occur, and then iSCSI service to one of the hosts resumed immediately, the other after it was done. Which, in a cluster configuration, was appropriate.
4. Here is how to apply a new license (couldn't find documentation on this either):
1. Open StarWind Management Console
2. If you have expired license, you will see the pop-up which will give a option to install a new license
3. Specify the path for a new license
4. Click OK to install the license
Another way is:
1) In the StarWind console, connect to the server
2) Click "Configuration tab"
3) Click "Register"
4) Choose "Modify" in top right corner
5) Specify path for a new license
6) Click OK to implement it.
I am now back on the proper license.
But I want to say I was impressed how friendly and helpful the folks at StarWind were. Thanks to all!
-- Ken