Finally resolved the issues with unique EUIs with assistance from support and all is back in working order with no data loss. Big thanks to Yaroslav and the StarWind Team.

Continue to be impressed by the StarWind VSAN and its stability. Keep up the great work!

Hi Yaroslav,

I uploaded the all the headers for both nodes in the following link
https://drive.google.com/drive/folders/ ... sp=sharing

Hi Yaroslav,

The StarWindHeaders folder is empty for both nodes. I have double checked and rerun the log collection but they are still empty.

Apologies, I confused you with my last statement. What I meant to say is that I reconnected the csv on both nodes using multipath, and then run the logs and took the images. Please tell me if you need anything else.

I thought you might say that. Unfortunately there is no such folder in the logs. I have loaded the logs and images of the cluster and VSAN of both nodes in the following link https://drive.google.com/drive/folders/1f87wVcdvJ7_xwJ9MoUNBNqvV3s-mdM2f I have reconnected the csv on both nodes using multi...

I need some help where to find the CSVtoPhysicalDiskMapping folder.

Also, how do you want me to share the logs with you? I assume on a cloud drive rather than send to forum.

Hi Yaroslav, The disks are HA. They are setup identical to the guide https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyperconverged-scenario-with-hyper-v-server-2016/ with HAimage1 (csv), HAImage 2(non csv), HAImage3 (witness). MPIO appears to work fine on b...

Hi, MPIO for iSCSI is indeed on. Oddly after a reboot on gidshc01 the cluster error is now reported on Disk 3 and 5 which is the other VSAN disk (HAImage2). HAImage2 is a non-csv file share drive. This time though Disk 3 appears in the HardDriveInfo after running the log collector. Still no reportin...

Yeap, there is MPIO on both nodes. I run the log collection on gidshc01(node in the error message). It appears I cannot find either Disk 3 or Disk 4. According to disk manager though, Disk 4 is the gidshc01 HAImage1.img disk and Node 3 is the corresponding node's (gidshc02) disk forming a csv. Devic...

Well almost alright... After getting the VSAN working correctly and making sure that it was working and no data was lost, I run Cluster Validation (Hyper-V). I get the following error, which was not there in previous validations. Two disks have been found on node gidshc01.internal.gulfid.com with du...

Got it. Thanks Yaroslav. Cylinder number on both sides is equal and I didn't do any HA device resizing.

Thanks Yaroslav it worked! I took my time to try it out because in the meantime I already started manually editing the StartWind.cfg in both nodes and *_HA.swdsk files in the failed node (node 2). I managed to recover the failed node and all its VSAN disks using this method, which helped me get a mu...

I get the following error when making the changes Request to GIDSHC01.INTERNAL.GULFID.COM ( 10.0.2.12 ) : 3261 - control 0x0000020A858C0240 -AddPartner:"" -PartnerTargetName:"#p1=iqn.2008-08.com.starwindsoftware:gidshc02-partnerha22;#p2=iqn.2008-08.com.starwindsoftware:gidshc02-part n...

Script attached param($addr="10.0.2.12", $port=3261, $user="root", $password="starwind", $deviceName="HAImage4", $addr2="10.0.2.14", $port2=$port, $user2=$user, $password2=$password, #secondary node $imagePath2="My computer\D\starwind", $im...

Thank you for your prompt reply. I used the same variables when I first run the script as you mentioned in your last reply (the same as in StarWindX library) Hi, Make sure to specify $syncInterface2="#p1={0}:3260" -f $addr and $selfSyncInterface="#p1={0}:3260" -f $addr2. $selfHbI...