Eric Hill said: > I haven't tried running a debug build of the initiator yet. > Doesn't that require installing a debug/checked build of Windows as well?
No, you do NOT need to be running a checked build of Windows. I'm running the checked build version of the iscsi initiator on a normal Windows Server 2003. I'm still using version 2.03 of the initiator as that works ok for me. Using that arrangement, I was able to help trace a bug in the Solaris iscsi target related to StatSN back last year, as mentioned here: http://mail.opensolaris.org/pipermail/storage-discuss/2007-January/002295.html ..but that bug was fixed along time ago. > The log file doesn't show anything about a core dump in any way. > Basically, I see the regular service stopping/starting messages. Ok, fine. (It's best just to check this first.) In that case, I would recommend running the checked build of the Microsoft iscsi initiator, as described in the link in my last post, and try to reproduce the problem. Then see if it says anything in the 'DebugView' window when the problem occurs. >From the Solaris side, you could try running a DTrace script: http://www.solarisinternals.com/wiki/index.php/DTrace_Topics_iSCSI ..but I cannot remember if they have back-ported the iscsi target provider to the version of Solaris 10 you are using. Thanks Nigel Smith This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
