Can you check for error 129 / 153 in Windows System logs? Are they present?

You would need to reinstall the StarWind VSAN software and when creating a new device you would use an existing disk rather than creating a new one.

Daniel, The thing about LSFS is that it does grow over time as data operations are processed. Your device's size is not just 1TB, it's 2.49TB. And taking into account the 2x overprovisioning ratio for an LSFS device you would need at least 7.47TB of the physical storage. Your value of 7.48TB is pret...

I'm not 100% sure if the network is fine. How can i test it?

Simply by using ping. That would give you an idea whether networking is fine.

OK, waiting for the logs.

Can you confirm the network connectivity is not broken? What scripts and on which nodes have you tried to make the sync process happen?

bertram,

I am not sure you can get the status of sync/heartbeat interfaces from StarWindX. You might want to monitor that using networking monitoring tools. StarWind relies on the physical networking, so that way will definitely work. batiati's approach does make sense, I believe.

In the view of that, you will either need to increase the capacity of the current disk, if possible. If not, perform data migration to another location and then recreate the disk. Yet keep in mind an imagefile based one could be better for your environment. If you prefer using LSFS, you can create a...

Well... At least I believe it works for you now, right? If you ever try upgrading to the next builds and get the same reproduced just keep this thread in mind. We will definitely want to check the logs on our side. This particular build was supposed to resolve the issue, yet you are the second perso...

Sorry, totally missed it...
Could you collect logs from your hosts using StarWind Log Collector and share them with me? Do not forget to send your license file used there, too.

Do you have any snapshots for that device?

https://www.starwindsoftware.com/starwind-v2v-converter states the formats StarWind V2V supports, and it lists only QCOW2 as supported, but no QCOW3.

Looks like an issue with licensing. What build gives you this issue?

Is at least one of the nodes synchronized? What is the build that you had this issue appearing with?

Our KB article at https://knowledgebase.starwindsoftware.com/guidance/recommended-raid-settings-for-hdd-and-ssd-disks/ offers all relevant settings for all types of supported RAID arrays. In your case, you would use "write-through" for write operations and "no read ahead" for rea...