Thu Nov 05, 2009 7:28 pm
Yeah, I was somewhat hesitant to do post it in the same thread as it's probably not related, the more I think about it. All the evidence I have is that the Starwind service crashes. That's it. Nothing else in the system log, application log, or any other Windows logging. Of course, when the Starwind service stops, this kills the LUNs and thus the cluster resources. There is no Windows crash or restart or any other error. Everything keeps on chugging save for iSCSI related services. Starwind management console still works. If I restart the service I can go back to cluster admin, bring the drives back on-line, and then restart Hyper-V vm's with no problem. I sent Bob Boule a log file and mini-dump last week, but I haven't heard anything back yet. I know you guys are busy with the 5.0 rollout. When this first appeared in early Oct, I was sent an updated version (v4.2.3 I think?) Didn't make a difference. Upgraded to v5.0 a few days ago and it has occurred twice since then. I can't seem to correlate it to anything. Oddly, there are no other Windows 'hiccups' other than the Starwind crash. I haven't tried a full uninstall and reinstall, yet.
When perusing various software vendors' forums, I am usually amused by users experiencing problems when the vast majority might use the software with no errors. I suppose I'll have a bit more compassion now!
Thanks,
Matt