All CSVs are connected. I'm wondering if restarting the Cluster Service on the affected node might be the way forward. Looking at the logs, seems like there was some resyncing following the restart.

I have a 2-node hyperconverged setup between two Windows Server 2019 machines using VSAN Free. Windows updates were installed on Node 2 last night and it restarted. I can now no longer move roles to that node using Failover Cluster Manager. I can see the ClusterStorage folder mounted on the root of ...

And just like that, all sorted. Thanks once again for your support of this excellent solution.

Which is the correct script please? Thanks once again.

Thank you for the info about the DC. That was the case, and this is the only time it has been an issue - it is now removed from the cluster. The syncing is still going (not the fastest hardware in the land) but I can now access the storage and our infrastructure is back up and running. The Witness i...

Our two StarWind servers were restarted incorrectly, and it appears to have upset the cluster. I can see the main CSV1 drive is doing a full synchronize (upwards of 7 hours) but at present, the Witness drive is not synchornized. Should I expect the Witness drive to kick back in to life when the CSV1...

This was a license change issue following the upgrade. All sorted with the assistance of the excellent StarWind team!

Another update, have run the PowerShell script "SyncHaDeviceAdvanced". On the non-updated node, I get the following: HAImage1 Device synchronized HAImage2 Device synchronized However, on the updated node, it displays: HAImage1 Device not synchronized. Synchronize current node from partner ...

Hi Yaroslav. Thank you once again for the reply - the Management Console doesn't let me do monitoring, when I attempt to connect to either node I get a pop-up about the free license and that it only operates during a 30-day trial and then it disconnects. To be clear, is your next suggestion to press...

Having looked in the logs, I can see several lines as below: 5/23 14:51:00.556840 1b8c Srv: *** iScsiServer::listenConnections: *LICENSE* Rejected iSCSI connection to 172.16.10.10:3260 from 172.16.10.20:63594.Maximum of 0 allowed clients already connected to the server! Does the free license need up...

I have just performed an in place upgrade of VSAN Free version 8.0.0.11818 to version 8.0.15020.0. All seemed to go okay, but now the iSCSI targets for the local upgraded node are stuck with status "Reconnecting". On the non-upgraded node, the witness target from the upgraded node is now n...

In theory, could I:

• 1. upgrade Node 1 to 2016
  2. then, upgrade Node 2 to 2019
  3. then, upgrade Node 1 to 2022
  4. and finally, upgrade Node 2 to 2022

All while keeping the guests systems online?

Thanks,

Ed

Hi Yaroslav,

Thank you for the excellent response. The first (but longer option) actually sounds okay as it will result in minimal (to zero) downtime. I will consider this further then begin planning my next steps...

Thanks again,

Ed

Hello, I have been using VSAN Free at the small business I work for to enable a 2-node hyperconverged setup between two Windows Server 2012R2 servers for several years now. The servers are long overdue an upgrade and I have purchased new Server 2022 licenses and was wondering if there was a best pra...