After stopping the service, cleaning up the many lingering <device ... /> entries in the config file, restarting the service, and then running CreateHA_2 again, it looks like it worked! The web UI showed that it was synching, and then shows the LUN as Online / High Availability. I'll soon proceed wi...

Thank you. By management console, I assume you mean the computer from which I'm running the PowerShell scripts? That workstation is on a different network than the StarWind VMs, but there is an explicit "permit all" rule from that network to the 172.17.x.x network - no traffic restrictions...

Thank you. That seems to have made some progress. I had the bitmap parameters commented out from seeing multiple replies from you in other, similar threads, suggesting that. However, it's not quite there: PS C:\WINDOWS\system32> D:\PersistentData\Users\TechSupport\Desktop\CreateHA_2.ps1 Request to 1...

Here you go: param($addr="172.17.6.31", $port=3261, $user="root", $password="starwind", $addr2="172.17.6.32", $port2=$port, $user2=$user, $password2=$password, #common $initMethod="NotSynchronize", $size=1024, $sectorSize=512, $failover=0, $bmpType=1...

Yes, the volume were successfully created before attempting this, and show up correctly in the web UI. Yes, on the first node (172.17.6.31), the following were created: /mnt/sdb1/shared/test2.img /mnt/sdb1/shared/test2.swdsk.bak /opt/starwind/starwind-virtual-san/drive_c/starwind/headers/test2/test2...

Thank you for the prompt reply! Unfortunately, I still have the same results: Request to 172.17.6.31 ( 172.17.6.31 ) : 3261 - control HAImage -CreateHeader:"Headers\test2\test2_HA.swdsk" -pathDirHeaderBackup:"/mnt/sdb1/shared" -file:"imagefile 14" -size:"1024"...

Hello, I attempting to deploy a two-node shared storage setup, and am running up against a wall with the PowerShell script, "CreateHA_2.ps1" Getting some details out of the way: - StarWind Virtual SAN (VSAN) v8.0.0 (Build 15469), Free license StarWindX.dll properties: - Version: 1.0.0.664 ...