Hi Eric Thanks for the feedback on using the checked build of the Microsoft iscsi initiator.
Take a look back at my posts here: http://www.opensolaris.org/jive/thread.jspa?messageID=88568 And you will see almost the exact same error. Eric, your debug output seems to be lacking some level of detail. In my post, I was also seeing logged "Invalid status seq num " which ties up with the event log. Please check the times of the errors in the event log, against the times of the messages in the DebugView window. Presumably they match. Did you remember to set the following value in the registry: \Software\Microsoft\Windows NT\Current Version\ISCSI\Discovery DebugSpewLevel = 0x006f0007 ..plus you need to reboot after that change. The DebugSpewLevel is a bit mask as follows: #define SPEW_ALL 0xffffffff #define SPEW_FATAL 0x00000001 #define SPEW_ERROR 0x00000002 #define SPEW_WARNING 0x00000004 #define SPEW_INFORMATION 0x00000008 #define SPEW_RECURRING 0x00000010 #define SPEW_DRIVER_PROBLEM 0x00010000 #define SPEW_WMI_API 0x00020000 #define SPEW_MEMORY 0x00040000 #define SPEW_TCP 0x00080000 #define SPEW_REFCOUNT 0x00100000 #define SPEW_PROCTHREADIDS 0x00200000 #define SPEW_TIMESTAMP 0x00400000 Please try this & see if it gives more detail. But this is beginning to look like the same problem as 12 months ago! The problem then that the 'StatSN' field (Status Sequence number) was incrementing during "NOP In" packets, when it should not have done. This was fixed in Nevada (by Rick McNeal) a long time ago. Surely that fix was putback into Sol10u4 !! But it's beginning to look like someone at Sun needs to double check this putback was made. The source code for Solaris 10 is not public, so we cannot do this from the outside. Regards Nigel Smith This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
