Just installed the latest build from today (I was already on 5.7.1733) and so far it seems to have stopped the issue!

gstephenson wrote:Yes, the solution in my case was to change iscsiPingPeriod value to 20 in Starwind.cfg on the first server, restart Starwind, let sync finish, then do the same on the second Starwind server.

I am only running one StarWind server?

The only change seems to be that these messages are appearing. There seems to be a write spike every few minutes. There's barely any activity on it. Its just used to store Windows Server Update data so there's no activity until updates are released.

anton (staff) wrote:Do you run two node cross-linked configuration or do you run StarWind inside VMs?

Starwind runs on a native Windows 2008 server, the iSCSI client runs on SBS2003 on a virtual server

I'm just updated to 5.7 from 5.6 and am receiving 2 messages every minute in my logs: iScsiPrt Error Event ID 20 Connection to the target was lost. The initiator will attempt to retry the connection iScsiPrt Error Event ID 34 A connection to the target was lost, but Initiator successfully reconnecte...