Application Error - Starwind won't start

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
User avatar
Branin
Posts: 31
Joined: Mon May 04, 2015 5:22 pm

Tue Jun 16, 2015 7:42 pm

I seem to be getting all sorts of errors, but can't figure out what I'm doing wrong. I've downloaded and am now using version 8116 (the most recent, as far as I can tell). I've followed the instructions in the Hyper-Converged 2 Nodes Scenario 2 Nodes with Hyper-V Cluster document, while also following the instructions at http://knowledgebase.starwindsoftware.c ... tner-node/ for creating devices from scratch and applying L2 cache to them. Everything seems to go great up until the point that I configure MPIO to include iSCSI devices and reboot my first node. As soon as I do that, my second node crashes. I'm able to restart the service manually. However, my first node never starts Starwind again. Manually trying to start Starwind on the first node returns an "Error 1607: The process terminated unexpectedly." error from Services.

Both of the servers have errors in the Application event log:

Log Name: Application
Source: Application Error
Date: 6/16/2015 12:24:18 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: NW-VMHOST01.xxxxxx.local
Description:
Faulting application name: StarWindService.exe, version: 8.0.0.8116, time stamp: 0x55707a66
Faulting module name: ntdll.dll, version: 6.3.9600.17736, time stamp: 0x550f4336
Exception code: 0xc0000374
Fault offset: 0x00000000000f0f20
Faulting process id: 0xb6c
Faulting application start time: 0x01d0a86a0272568e
Faulting application path: C:\Program Files\StarWind Software\StarWind\StarWindService.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 47e0e11e-145d-11e5-80bd-cdfa99941e4a
Faulting package full name:
Faulting package-relative application ID:

followed by the same error twice from Windows Error Reporting:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: StarWindService.exe
P2: 8.0.0.8116
P3: 55707a66
P4: StackHash_a012
P5: 6.3.9600.17736
P6: 550f4336
P7: c0000374
P8: PCH_A3_FROM_ntdll+0x000000000009177A
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_StarWindService._e5fa0eb58ba452b919d7fe9d9d01dfa7b65a7_df808a2c_100471b0

Analysis symbol:
Rechecking for solution: 0
Report Id: 47e0e11e-145d-11e5-80bd-cdfa99941e4a
Report Status: <either 0 or 4100>
Hashed bucket:

---

The attached file is:
Version=1
EventType=APPCRASH
EventTime=130789562585258498
ReportType=2
Consent=1
ReportIdentifier=47e0e11f-145d-11e5-80bd-cdfa99941e4a
IntegratorReportIdentifier=47e0e11e-145d-11e5-80bd-cdfa99941e4a
NsAppName=StarWindService.exe
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=StarWindService.exe
Sig[1].Name=Application Version
Sig[1].Value=8.0.0.8116
Sig[2].Name=Application Timestamp
Sig[2].Value=55707a66
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_a012
Sig[4].Name=Fault Module Version
Sig[4].Value=6.3.9600.17736
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=550f4336
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_A3_FROM_ntdll+0x000000000009177A
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.400.8
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=a012
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=a012c8df73c47255607f93da49cfd6a5
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=8c02
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=8c0227acc11d1b9ab4249a425d5e88e9
UI[2]=C:\Program Files\StarWind Software\StarWind\StarWindService.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=StarWind Virtual SAN stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Program Files\StarWind Software\StarWind\StarWindService.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[5]=C:\Windows\system32\WS2_32.dll
LoadedModule[6]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[7]=C:\Windows\system32\USER32.dll
LoadedModule[8]=C:\Windows\system32\RPCRT4.dll
LoadedModule[9]=C:\Windows\system32\ole32.dll
LoadedModule[10]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[11]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[12]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[13]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[14]=C:\Program Files\StarWind Software\StarWind\VersionTracker.dll
LoadedModule[15]=C:\Program Files\StarWind Software\StarWind\libiconv.dll
LoadedModule[16]=C:\Windows\system32\SHELL32.dll
LoadedModule[17]=C:\Windows\system32\msvcrt.dll
LoadedModule[18]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[19]=C:\Windows\system32\NSI.dll
LoadedModule[20]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[21]=C:\Windows\system32\GDI32.dll
LoadedModule[22]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[23]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[24]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[25]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[26]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[27]=C:\Windows\SYSTEM32\clbcatq.dll
LoadedModule[28]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[29]=C:\Windows\system32\rsaenh.dll
LoadedModule[30]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[31]=C:\Windows\SYSTEM32\shcore.dll
LoadedModule[32]=C:\Windows\system32\napinsp.dll
LoadedModule[33]=C:\Windows\system32\NLAapi.dll
LoadedModule[34]=C:\Windows\System32\mswsock.dll
LoadedModule[35]=C:\Windows\SYSTEM32\DNSAPI.dll
LoadedModule[36]=C:\Windows\System32\winrnr.dll
LoadedModule[37]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[38]=C:\Windows\System32\rasadhlp.dll
LoadedModule[39]=C:\Program Files\StarWind Software\StarWind\DDDiskEx.dll
LoadedModule[40]=C:\Program Files\StarWind Software\StarWind\DatabaseWrapper.dll
LoadedModule[41]=C:\Program Files\StarWind Software\StarWind\lsfs.dll
LoadedModule[42]=C:\Program Files\StarWind Software\StarWind\RamDisk.dll
LoadedModule[43]=C:\Windows\system32\PSAPI.DLL
LoadedModule[44]=C:\Program Files\StarWind Software\StarWind\ImageFile.dll
LoadedModule[45]=C:\Windows\system32\CRYPT32.dll
LoadedModule[46]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[47]=C:\Windows\system32\MSASN1.dll
LoadedModule[48]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[49]=C:\Program Files\StarWind Software\StarWind\VirtualDvd.dll
LoadedModule[50]=C:\Program Files\StarWind Software\StarWind\IBVolume.dll
LoadedModule[51]=C:\Program Files\StarWind Software\StarWind\Mirror.dll
LoadedModule[52]=C:\Program Files\StarWind Software\StarWind\DiskBridge.dll
LoadedModule[53]=C:\Program Files\StarWind Software\StarWind\VirtualTape.dll
LoadedModule[54]=C:\Program Files\StarWind Software\StarWind\HAImage.dll
LoadedModule[55]=C:\Program Files\StarWind Software\StarWind\iSCSITransportLib.dll
LoadedModule[56]=C:\Program Files\StarWind Software\StarWind\VTL.dll
LoadedModule[57]=C:\Program Files\StarWind Software\StarWind\SysMan.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=StarWind Virtual SAN
AppPath=C:\Program Files\StarWind Software\StarWind\StarWindService.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=6598E028959FBD5F2D34D1C9F1B90C61


---

I never had this problem with the previous released version of Starwind, although I wasn't trying to do anything with L2 caching back then, obviously.

Any ideas? Is this just another weird problem with my system that other people aren't getting? Is there a better way of getting L2 caches on replicated devices/targets beyond just the Knowledge Base?

Thanks!

Branin
User avatar
Branin
Posts: 31
Joined: Mon May 04, 2015 5:22 pm

Tue Jun 16, 2015 9:27 pm

I went to lunch and when I came back, I was able to start Starwind on the first node. Neither of my replicated targets/devices synchronized though. I had to manually pick one and "Mark as synchronized".

Is this normal?

Thanks!

Branin
Vladislav (Staff)
Staff
Posts: 180
Joined: Fri Feb 27, 2015 4:31 pm

Wed Jun 17, 2015 12:35 pm

OMG :shock:

Branin you've encountered with all possible and impossible issues.

Please drop us an email support@starwindsoftware.com with the StarWind logs and System & Application logs. And also attach minidump files of StarWind service if they were created.
Branin wrote:I went to lunch and when I came back, I was able to start Starwind on the first node. Neither of my replicated targets/devices synchronized though. I had to manually pick one and "Mark as synchronized".

Is this normal?
It requires investigation as it might be normal. http://knowledgebase.starwindsoftware.c ... -blackout/

The only ways of getting L2 caches are described in the Knowledge Base. There is no better way unfortunately.
User avatar
Branin
Posts: 31
Joined: Mon May 04, 2015 5:22 pm

Wed Jun 17, 2015 11:18 pm

Vitaliq,

Thank you very much! I know this will all be worth it in the end. :- )

I just emailed the requested documents (except for the minidump files, which don't seem to have been generated this time).

Thanks!

Branin
Vladislav (Staff)
Staff
Posts: 180
Joined: Fri Feb 27, 2015 4:31 pm

Mon Jun 22, 2015 4:55 pm

Ok, community

The reason of the issue is the size of cache. Branin uses too large cache and we are going to make StarWind usage with even larger cache possible.
User avatar
Branin
Posts: 31
Joined: Mon May 04, 2015 5:22 pm

Mon Jul 06, 2015 8:38 pm

I can confirm that the most recent build (8198) still has the same problem with "large" caches (~33GB L1 and 1TB L2), attached to a 1GB device (that gets expanded to a 5TB device after initial synchronization). The problem previously appeared with build 8116.

Thanks.

Branin
Vladislav (Staff)
Staff
Posts: 180
Joined: Fri Feb 27, 2015 4:31 pm

Wed Jul 08, 2015 3:03 pm

Thank you for the update.

We are working on it.
Post Reply