iSCSI Initiator crashes

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

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

Post Reply
rgs
Posts: 4
Joined: Fri Nov 12, 2010 11:28 pm

Fri Nov 12, 2010 11:45 pm

I'm using the free iSCSI Initiator to try to connect to an 8TB FreeNAS iSCSI target.
When I use the Add Device wizard I get as far as entering the IP address and clicking Next, then it crashes with the standard Microsoft error dialog "StarWind iSCSI Initiator has encountered a problem and needs to close. We are sorry for the inconvenience."
I've tried this on two XP SP3 PCs with the same result. I can connect to the target OK from a Windows Server machine using the MS iSCSI Initiator.
The following is from the log file.

11/13 12:39:05.976 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
11/13 12:39:06.194 >> CStarPortAPI::GetTargets(dwIPAddress=0xA0F3623, DWORD dwPort=3260, listTargets=...)
11/13 12:39:06.194 CStarPortAPI::GetTargets: Calling STARPORT_IOCTL_GET_TARGETS
11/13 12:39:06.194 CStarPortAPI::GetTargets: Input buffer:
11/13 12:39:06.194 CStarPortAPI::GetTargets: ServerAddress = #iscsi:10.15.54.35:3260
11/13 12:39:06.194 CStarPortAPI::GetTargets: Parameter[0] = InitiatorName=iqn.2003-06.com.starwindsoftware.starport:sysmon2
11/13 12:39:06.226 CStarPortAPI::GetTargets: Session failed, status == 317 !
11/13 12:39:06.382 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2

Any ideas on what might be causing this?
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Sat Nov 13, 2010 9:58 am

Absolutely no! Can you reproduce situation and send us zipped crash dump files?
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
rgs
Posts: 4
Joined: Fri Nov 12, 2010 11:28 pm

Sun Nov 14, 2010 10:43 pm

Thanks for the reply Anton, I've sent you the file.
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Sun Nov 14, 2010 11:35 pm

Got logs from you but I've asked for Windows crash dump files. Unfortunately StarPort logs are not enough to put light on issue and we don't have referenced SAN to test StarPort or iSCSI initiator against it...
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
rgs
Posts: 4
Joined: Fri Nov 12, 2010 11:28 pm

Mon Nov 15, 2010 12:25 am

Ahhh, sorry about that. Monday morning, no coffee... :oops:
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Mon Nov 15, 2010 4:20 pm

No coffee sucks!

P.S. Got both log and crash dump, forwarded to responsible software engineer and he's checking what's wrong. Thank you for cooperation!
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
User avatar
Vitalii (staff)
Staff
Posts: 44
Joined: Mon Jun 07, 2010 8:49 am

Wed Nov 24, 2010 3:39 pm

Please, try this debug build:
http://www.starwindsoftware.com/tmplink ... _debug.exe

Just put this file into iSCSI initiator directory.

Try to reproduce that error and send a crash log made with that build.
rgs
Posts: 4
Joined: Fri Nov 12, 2010 11:28 pm

Mon Nov 29, 2010 8:08 pm

Thanks Vitalii, I'll test this as soon as I can.
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Mon Nov 29, 2010 8:09 pm

Please keep us updated. Thank you very much for cooperation.
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
Post Reply