Virtual SAN Free crashing

Michael.Bromund · Wed May 31, 2017 10:51 am

Hello, I have a compute and storage seperate setup which run for over a year without problems. Since last week the file server cluster (named SAN01 + SAN02) becomes unavailable while one node freezes completely (login via rdp or console not possible). Updated Starwind and all network drivers, checked every network connection, tried running with either node solo which works for about 12 hrs and the node freezes, tried running with two nodes (one marked as synchronized), sync worked but one node freezes after about 12 hours. Any suggestions what could cause that weird behaviour? Thank You,

Wed May 31, 2017 3:27 pm

There was an update from Microsoft that was crashing all iSCSI setups. Did you apply and updated in the recent 2-3 weeks?

Michael.Bromund · Thu Jun 01, 2017 6:29 am

Yes, I did. Which one was it?

kaitwo · Thu Jun 01, 2017 11:58 pm

Same here!

Seems to be related to KB4019215 and KB4019213 (also probably KB4019217) bugging iSCSI as per:

https://social.technet.microsoft.com/Fo ... 51be3cf300

https://www.reddit.com/r/sysadmin/comme ... rformance/

Fri Jun 02, 2017 12:19 am

They are KB4015553 and KB4019215.
To fix this issue, go to iSCSI Initiator and delete the reconnecting target from the Favorite Targets tab. After you have done this, follow to the Targets tab, disconnect the reconnecting target manually by pressing the Disconnect button and connect it again. This will help you to eliminate the reconnecting status of your iSCSI targets. This should be followed by server reboot. Prior to rebooting the server, make sure that all StarWind devices are synchronized on both StarWind nodes. After this you can reboot the server. Once the server is in operation again, check the devices for the Synchronized state again and proceed with the other StarWind node.
More Information:
https://social.technet.microsoft.com/Fo ... serverwsus
https://social.technet.microsoft.com/Fo ... f=required