[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: StorCenter ix2-200 Network Storage over open-iscsi package.



sorry -- this is the error i get when i restart /etc/init.d/open-iscsi :

Logging in to [iface: default, target:
iqn.1992-04.com.emc:storage.mjhstg.iscsi, portal: 10.168.2.57,3260]
iscsiadm: Could not login to [iface: default, target:
iqn.1992-04.com.emc:storage.mjhstg.iscsi, portal: 10.168.2.57,3260]:
iscsiadm: initiator reported error (15 - already exists)
iscsiadm: Could not log into all portals. Err 15.


On Tue, Oct 4, 2011 at 10:40 AM, Joey L <mjh2000@gmail.com> wrote:
> I am getting a strange error with the open-iscsi package on debian
> using nas StorCenter ix2-200 Network Storage.
>
> I think i setup the device correctly following this:
> iscsiadm -m node -T iqn.1992-04.com.emc:storage.xxxstg.iscsi -p
> 10.168.2.57 --op update -n node.session.auth.username -v admin
> iscsiadm -m node -T iqn.1992-04.com.emc:storage.xxxstg.iscsi -p
> 10.168.2.57 --op update -n node.session.auth.password -v adminadmin
>
>  iscsiadm -m node -T iqn.1992-04.com.emc:storage.xxxstg.iscsi -p
> 10.168.2.57 --op update -n node.startup -v automatic
>
>
> iscsiadm -m discovery -t sendtargets -p 10.168.2.57:3260
> 10.168.2.57:3260,1 iqn.1992-04.com.emc:storage.xxxstg.iscsi
>
>
> when i execute this command:
> iscsiadm -m node -T iqn.1992-04.com.emc:storage.xxxstg.iscsi -p 10.168.2.57 -l
>
> I get error:
>
>
> Oct  4 10:34:07 rider iscsid: iSCSI logger with pid=30766 started!
> Oct  4 10:34:07 rider iscsid: transport class version 2.0-870. iscsid
> version 2.0-871
> Oct  4 10:34:07 rider iscsid: iSCSI daemon with pid=30767 started!
> Oct  4 10:34:08 rider iscsid: could not read session targetname: 5
> Oct  4 10:34:08 rider iscsid: could not find session info for session1
> Oct  4 10:34:08 rider iscsid: could not read session targetname: 5
> Oct  4 10:34:08 rider iscsid: could not find session info for session1
> Oct  4 10:34:08 rider iscsid: session
> [iqn.1992-04.com.emc:storage.mjhstg.iscsi,10.168.2.57,3260] already
> running.
>


Reply to: