Hi,
I am running an initiator on FC9 64-bit (Linux
2.6.27.21-78.2.41.fc9.x86_64 #1 SMP) connecting to a NexSan SATA boy
over 1GB ethernet with iSCSI.
I am running open-iscsi 2.0-870.
When I try to connect I get a conn error (1011) and I am struggling
to know where to go next. The NexSan has
hissing_sid wrote:
Hi,
I am running an initiator on FC9 64-bit (Linux
2.6.27.21-78.2.41.fc9.x86_64 #1 SMP) connecting to a NexSan SATA boy
over 1GB ethernet with iSCSI.
I am running open-iscsi 2.0-870.
Are you using a open-iscsi.org release or fedora iscsi-initiator-utils one?
When
I downloaded and compiled the open-iscsi release, so I think I am
using that.
However, just to be sure I uninstalled iscsi-initiator-utils (yum
remove ) so I only have open-scsi.
Now, when I try to start iscsid ( ./iscsid -f ) I get the following:
iscsid: Missing or Invalid version from
All sorted. Definitely running only open-iscsi now.
Still broken though
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
iscsi: registered transport (iser)
scsi6 : iSCSI Initiator over TCP/IP
connection1:0: detected conn error (1011)
session1: host reset succeeded
hissing_sid wrote:
I downloaded and compiled the open-iscsi release, so I think I am
using that.
However, just to be sure I uninstalled iscsi-initiator-utils (yum
remove ) so I only have open-scsi.
Now, when I try to start iscsid ( ./iscsid -f ) I get the following:
iscsid: Missing or
hissing_sid wrote:
All sorted. Definitely running only open-iscsi now.
Ok ignore the request to use iscsi-initiator-utils.
Still broken though
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
iscsi: registered transport (iser)
scsi6 : iSCSI Initiator over
Just looked at the trace myself. I can see it trying to contact LUN 00
but I do not have that configured on my target. I am using LUN 01
That is why is it failing. When I change my Target LUN to 00 it
works.
So, how or where is the initiator deciding on the LUN? Is it
configured or should
hissing_sid wrote:
Just looked at the trace myself. I can see it trying to contact LUN 00
but I do not have that configured on my target. I am using LUN 01
That is why is it failing. When I change my Target LUN to 00 it
works.
So, how or where is the initiator deciding on the LUN? Is
