Hi,
What I am trying to say is that StarWind VSAN stumbled into underlying storage delays and could not synchronize. It is not related to the OS drive, but to the underlying storage. The updated version introduced higher timeouts for underlying storage, hence, it may make the VSAN service synchronize. The service became tougher.
It does not defeat the purpose as you are still having 2 mirrors. Even in the 2-way mirror, with a node down the production is running.
If the update is done on your own, you can update it for free. You still can update as VSAN as currently, your system is acting as a 2-way mirror. It is the support contract that needs to be renewed; the product itself does not expire and you can switch to later versions even without an active support plan.
HINT: you might require the key change. Please contact
support@starwind.com (use this thread and 742222 as your references). If you need a key during the update, it will be supplied faster I'd suggest starting with the affected node.