Gentlemen, please hang on with moving to 5.5
We're tring to reproduce and working on a solution for this issue and will release a hotfix in the nearest time.
Meanwhile if you have same problem I'll recommend to disconnect the failing node and work in a single-server scenario.

Hello guys,

Do you reset your ms cluster nodes before problem occurred, or do something with ms cluster nodes before problem occurred?

Yes, *.mdump files will stay after roll back. So it's not event log bug.
Guys, please archive and send your log files to as.
And inform as what day and approximately time the problem occurred?

Hello,

Possible we already know answer, it's can be bug in event logger, and we already have fix for it.
Do you have *.mdump files in folder ..\Program Files\StarWind Software\StarWind\ ?
If yes then please send it to swsdev@starwindsoftware.com or upload to mediafire.com.

In situation when both nodes was shutdown you can recreate HA device using existing image files. And on "Initialization method" wizard page you select "Do not synchronize virtual disks". In this case both nodes of HA device will be created in synchronized state without synchroniz...