You can try to connect the device with the help of the ISCSI initiator and then make changes you need.
You can convert device in StarWind V2V Converter to the necessary format.

Hi Dav,

So two Raid 0 arrays ? or raid 1 for OS disk ? rest for vsan ? what about caching ? Intel raid has an SSD Cache 2.0 feature

RAID 1 will be better and more reliable solution in your case, for OS and for vsan.
As for the cache, you can find recommended settings here.

Hi Benoire,
You did a lot!
Thank you for the good words about StarWind.
Linux StarWind VSA is in the testing stage now and should be available soon.

It should work.
Let the community know if it works for you.

Yes, I mean thick device.
Thank you for the logs, will proceed investigation.

The improved functionality of StarWind Cloud VTL to be implemented alongside with Azure blob storage and S3 compatible block storage is currently under development.
StarWind representative will contact you regarding your environment configuration in the nearest time.

Yes, I have already sent your request to our R&D team. This feature will be added in the further StarWind builds.

Glad to hear the issue resolved

DC virtualizing is a good idea, but you should store this VMs locally (on underlying storage) on the StarWind hosts and replicate them on the AD level. It is Microsoft recommendation to store AD VMs outside the Failover Cluster. The other VMs you plan to run should be stored on the failover cluster ...

Hello Vladimir,
Thank you for so detailed investigation.
I already escalated this case to R&D Department.

Benoire,
You did really impressive investigation
Actually, you did not mention about RAID arrays for the hosts, you can find recommended settings here.
Also, you can find step by step guide here.

Hello s3, Let me try to answer your questions. 1. As I want a big all-flash setup (6TB+ each server), I was wondering if there are any consequences not using local raid on each server? As you will understand, such big SSD SAS/NVMe disks are really expensive. I already searched the forum regarding th...

Kevin, Also, please check if your NIC supports iSER. OK, it's replicated without specifiy it especially in the _HA.swdsk file? You need to specify the size of L2 cache during creating a device and during the process of replica creation. If you are going to use NVME as the L2 cache, you will boost on...

Hi GRIDLOK,
Unfortunately, create DiskBribge option is not available from PowerShell.

I have one additional question. Do you have L1 cache configured for StarWind disks? If yes, the process of full sync stated after you turned on the second host to avoid any data loss. StarWind was in sync process there and then the first host went down. And actually, StarWind marked "not synchr...