Hi there, I've been seeing some messages like the following in my VSphere logs. iSCSI discovery to 10.1.2.1 on vmhba66 failed. The iSCSI Initiator could not establish a network connection to the discovery address. Lost uplink redundancy on virtual switch vSwitch1. Physical NIC vmnic1 is down. Affect...

I think I made a mistake running the update previously, I forgot to unzip the downloaded files before running the updater. I have run the update on both nodes, restarted and will now try a resynchronisation and let you know how it goes. Thanks.

Hi there,
I have run the starwind_update.run script after downloading the update file and both nodes have reported "No need to update".

(Update: Just checked, there are yum updates available that I could manually install)

After a stable few weeks, I put the StarWind cluster into maintenance mode to restart the VM hosts. After booting everything back up, everything seemed normal for a few hours, however then I started seeing the StarWind VSAN service crashing on both of the HA Nodes, causing the storage to become unav...

Thank you. As an update, the issue happened again. Similar error messages, increasing IOWait/alerts on VMs. Also around 12am, not sure what could trigger it at that time though.

Hi there, The build on both nodes is 13861. The iSCSI issues were diagnosed from VCenter logs: Lost access to volume 609b9cb5-0c006c2e-9af7-74867aee68f6 (VDISK01) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly. 06/21/2021, 5:12:05 AM Lost path redund...

I am using StarWind Virtual SAN for VSphere in a two node setup. Both nodes are running as appliances, with RAID'd SSDs configured with a VDO on top. The servers are connected over 10gig fibre for synch and ethernet links for the heartbeat. Last night, there was a flood of errors across the setup ju...