Event ID 15

Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics), iSCSI accelerator and RAM disk

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

Post Reply
lewis
Posts: 1
Joined: Thu Sep 24, 2009 3:21 pm

Mon Sep 28, 2009 5:16 pm

Hi,

I am getting lots of Event ID 15 errors in a Windows 2003 server SP1. This is what I have:

- StarPort 3.6.3 (build 20081210). Driver version 00030001, build 20081125)
- Windows server standard edition 2003 SP1
- Intel Pro/1000 PT Dual Server adapter. Latest drivers (9.12.36.0)
- CORAID SR1521. Latest firmware (20090728)
- Direct cat6 cable between NIC and CORAID

Once the error happens, disk appears as "Failed" in the startPort management GUI. CORAID shows all LUN as "Normal" and no error in pushed to the SNMP server.

Any hint ?
Thanks,
Luis
Robert (staff)
Posts: 303
Joined: Fri Feb 13, 2009 9:42 am

Tue Sep 29, 2009 4:13 pm

The reason of database corruption can be related to Lanmanserver service that is not dependent on StarPort and it’s requests are handled prior to StarPort driver can handle it.

Please do the following as a workaround:
You need to set the LanmanServer service dependent on StarPortService. So all share management will wait until the AoE devices are ready.
Use the Microsoft Service Control utility (Sc.exe) to create service dependencies.
This method is the preferred way to create service dependencies because the user does not have to manually modify the registry.
• Open the Command Prompt.
• Type and run the following command:
sc config lanmanserver depend= StarPortService
It's possible to set up service dependencies manually editing the Registry keys, but this way is not safe and can lead to serious problems that may require you to reinstall the operating system. So please use the previous method whenever it's possible.

thanks
Robert
StarWind Software Inc.
http://www.starwindsoftware.com
curt.mills
Posts: 2
Joined: Tue Jan 12, 2010 10:38 pm

Tue Jan 12, 2010 10:42 pm

I'm getting the same errors with version 4.2 Build 0x20090702, Driver version 0x00030001 Build 0x20090615.

Did this fix the problem for you?
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Sat Jan 16, 2010 5:49 pm

You may wish to give a try to the V5.2 StarPort we'll release this Monday.
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
curt.mills
Posts: 2
Joined: Tue Jan 12, 2010 10:38 pm

Thu Jan 21, 2010 6:28 am

Anton, any update to this - I don't see that 5.2 was released on Monday.
Constantin (staff)

Thu Jan 21, 2010 8:54 am

Sorry, for wrong information, but it wasn`t released. In most cases Event ID15 means that disk doesn`t response. We`ll be able to investigate your case, if you will send us logs at support at starwindsoftware dot com. Thanks
Constantin (staff)

Fri Jan 22, 2010 3:55 pm

Dear, Curt Mills sorry for long time response. We will be very appreciative, if you will help us to investigate your case to fix it as soon as possible. For this you need to do following:
Go to Device Manager in your Control Panel. In storage controllers must be StarPort Storage Controller, update it`s driver with attached one. Then reboot the server. Unpack from this archive file starportctl.exe and run it with parametr debug 3. Then go to http://technet.microsoft.com/en-us/sysi ... 96647.aspx and download tool DebugView. Run it and in menu choose Capture - Capture kernel, and try to re-create the error. Then save the log to file, and send it to us. Thanks a lot for coordination.
--
Attachments
StarPortDrv_Debug_20100122.zip
(1.18 MiB) Downloaded 846 times
Post Reply