StarWind Software

Greetings,

We have a Starwind deployment across 2 physical Hyper-V 2012 R2 servers using iSCSI 10Gb direct links (x2). In this deployment we have 4 CSV targets, not including the quorum. We are running a registered version of Starwind, version 6.0.6339. 2-3 days ago, the Starwind iSCSI SAN service on 1 of the Hyper-V hosts terminated unexpectedly, taking some of the target CSVs offline. Tonight, the same thing appears to have happened on the same host. I've perused the Windows Event Logs fairly deep as well as the Dell OMSA logs with no real answers as to why this is failing. I tried to look in the Starwind logs but they appear to be old dates that aren't relevant any longer. This is critical as we have production VMs deployed in this configuration. Any help is appreciated.

Thanks,

JW

I believe, no one in the world will be capable of helping you without logs since there are millions of reasons why some software would crash and most of them are not starwind related. Try to reproduce the mentioned behavior and get the proper logs

Sad but true, Darklight is right. Logs is the only source for information in such case.

I'd be happy to produce logs. Are we talking Windows Event logs or logs from the Starwind application itself?

Please take a look here: https://knowledgebase.starwindsoftware. ... ogs-bat-2/

Thanks. I appreciate your patience as I'm a first time poster here and wasn't aware of the "CollectLogs.bat" tool.

I tried to upload them but got an error indicating the max allowed size is 256KiB. My output zip file from the CollectLogs.bat tool is 30.5MB.

You can upload zip to dropbox.com or mega.co.nz and email us a link to download. It's OK.

Tarass (Staff) wrote:You can upload zip to dropbox.com or mega.co.nz and email us a link to download. It's OK.

Tarass. I just PM'd you with a public link to my logs.

Hello jward,

I am an engineer who is responsible for this case.

Could you please clarify if you encountered that issue between 30th January to 4th February?

Here is the short excerpt of the processing logs results:

30/01 11:50 AM - Service has stopped by system request (due to shutdown or manual stop).
30/01 12:16 PM – the same.
Then service worked until February 4th

Bogdan (Staff) wrote:Hello jward,

I am an engineer who is responsible for this case.

Could you please clarify if you encountered that issue between 30th January to 4th February?

Here is the short excerpt of the processing logs results:

30/01 11:50 AM - Service has stopped by system request (due to shutdown or manual stop).
30/01 12:16 PM – the same.
Then service worked until February 4th

This occurred 2x prior to 2-4-2016. Just prior to the 2-4-2016 issue, I set the service to automatically restart on failure in the settings. Prior to that, the service would terminate for unknown reasons and then screw up our sync.

Unfortunately I don't have any other logs older than what I provided.

Community update:

Looks like this case requires escalation.

Therefore, jward could you please create new ticket through the web form on our website?

My colleges working on American shift would be glad to assist you then!

Bogdan (Staff) wrote:Community update:

Looks like this case requires escalation.

Therefore, jward could you please create new ticket through the web form on our website?

My colleges working on American shift would be glad to assist you then!

Done - thanks

Community update:

We are already working on this case.

Thank you for cooperation