Jay Nelson wrote:
> sks# iscsifs -u jdn -h acp /iscsi
> pid 13232:/usr/src/dist/iscsi/src/initiator.c:1912: ***ERROR*** Bad Status-Class: got 2, expected 0
> Nov 27 08:45:53 sks iscsifs: pid 13232:/usr/src/dist/iscsi/src/initiator.c:1912: ***ERROR*** Bad Status-Class: got 2, expected 0 
> pid 13232:/usr/src/dist/iscsi/src/initiator.c:1737: ***ERROR*** initiator_cmd_t failed
> pid 13232:/usr/src/dist/iscsi/src/initiator.c:566: ***ERROR*** login_phase_i() failed
> Nov 27 08:45:53 sks iscsifs: pid 13232:/usr/src/dist/iscsi/src/initiator.c:1737: ***ERROR*** initiator_cmd_t failed 
> Nov 27 08:45:53 sks iscsifs: pid 13232:/usr/src/dist/iscsi/src/initiator.c:566: ***ERROR*** login_phase_i() failed 
> pid 13232:/usr/src/dist/iscsi/src/initiator.c:1084: ***ERROR*** enqueue_worker: discovery_phase() failed (ignoring command)
> Nov 27 08:45:53 sks iscsifs: pid 13232:/usr/src/dist/iscsi/src/initiator.c:1084: ***ERROR*** enqueue_worker: discovery_phase() failed (ignoring command)
>
> And on the target:
>
> Nov 27 08:49:49 acp iscsi-target: pid 751:/usr/src/dist/iscsi/src/parameters.c:648: ***ERROR*** Initiator authentication failed 79 1d 
> Nov 27 08:49:49 acp iscsi-target: pid 751:/usr/src/dist/iscsi/src/target.c:1087: ***ERROR*** login_command_t() failed 
> Nov 27 08:49:49 acp iscsi-target: pid 751:/usr/src/dist/iscsi/src/target.c:1207: ***ERROR*** execute_t() failed
>
>   
FWIW, I've been playing with the initiator under MacOS 10.5.1 (ppc), and
this is exactly what I see.  I'm looking to see if I can learn anything
new this evening - I'll be playing with it on an intel machine.

+j