Yup. Start that node up > mark the devices as synchronized manually. You can force synchronization, try using manual synchronization. Use SyncHaDevice.ps1, comment $device.Synchronize([SwHaSyncType]::SW_HA_SYNC_FULL, "") and uncomment #$device.MarkAsSynchronized() Start the VMs and see if...

Cool, just review the StarWind Interfaces in the config files and update them accordingly. Update iSCSI Initiator too (and purge the favorite targets). To bring CSV1 online, stop StarWindService on one node > mark the CSV as synchronized on the remaining node, and check the data. If all is good, st...

Working on this still, but still can't quite figure out what's happening. We have a new 10GbE Dual NIC coming and brought back the IPs the way they were originally (10.21.10.2/10.21.10.3 and 10.22.10.2/10.22.10.3 for data, and 10.23.10.2/10.23.10.3 for control respectively per machine). iSCSI Initia...

Check another node and see if synchronized and if storage can be connected in iSCSI initiator. Make sure the appropriate changes are made to configs. We only have two nodes, unfortunately. From Node 2; it has inactive on Node 1 CSV1, Node 1 CSV2, and Node 2 CSV1. From Node 1; it has Reconnecting on...

Remove cache as described here https://knowledgebase.starwindsoftware.com/guidance/changing-and-disabling-l1-cache/ Or follow https://forums.starwindsoftware.com/viewtopic.php?f=5&t=6779&p=40587&hilit=Sync.+Ps1#p40587 I've removed the caches per the first link. The first CSV is showing ...

There must be no IP address conflicts. Please reconfigure both nodes. Please also remove the cache. On server #1 I changed the IPs to data: 192.168.1.34; control: 10.23.10.3; and data: 192.168.1.11 (the IPs matching server #2) On server #2 I changed the IPs to data: 192.168.1.33; control: 10.23.10....

Thanks. The config should have different IPs. Please make sure to use different IPs. Different IPs per data, control, and data? <link id="2" type="data" priority="1" connections="1"> <peer ip="10.23.10.3" port="3260"/> </link> <link id=&qu...

yaroslav (staff) wrote: ↑

Mon Feb 16, 2026 7:18 pm

Share the config files please.

Here are the swdsk files. I appended which system is which on the file name.
Node 1 (GA-HV-01) is 10.23.10.2 and Node 2 (GA-HV-02) is 10.23.10.3

yaroslav (staff) wrote: ↑

Mon Feb 16, 2026 7:16 pm

Please make sure to make the change on both nodes.

On node 1, I set the IP address to the other side 10.23.10.3; and on node 2, I set the IP to 10.23.10.2.

You need to edit the .swdsk files (requires stopping the service). In Windows, if the Data interface (i.e., one you use for iSCSI) is affected, please remove old partner favorites and reconfigure iSCSI Initiator for each node. Been waiting approximately an hour and seeing no changes on the status. ...

Hi there, Got the changes made, and I'm no longer seeing the error about the IPs missing. It is currently stating that the partners are not synchronized; how long should it be before syncing kicks in? We did go from a 10GbE connection to a 1GbE; so I can assume it'll be considerably slower. Thanks, ...

Good day, We recently had a hardware failure on one of our two nodes in which the 10GbE Fibre Adapter has failed. We cannot seem to find the way to change the IP address mapped to the two synchronization channels. How can we adjust these to a different adapter/IP range on VSAN? Thank you, Kyle McIsaac

All the guest VMs on the Scale Computing nodes are Windows VMs, so that should work.

If I were to do something like P2V, would that work?

We are looking at migrating from a Scale Computing node-set to Microsoft Hyper-V. Not sure what would be the best way to do this or if V2V can directly migrate.