sundar mahadevan wrote:
> I tried the same connecting another hard drive of 20 G with 3 logical
> volumes namely: asm 17G , ocr 924M and vote 760M.
> 
> iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.ocr -p 192.168.20.22 
> -l
> iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.vote -p
> 192.168.20.22 -l
> iscsiadm -m node -T iqn.2001-04.com.ubuntu:scsi.disk.vg1.asm -p 192.168.20.22 
> -l
> 
> Looks like it only created the first one: ocr
> 
> Here is the log from /var/log/syslog
> Apr 15 21:10:17 sunny2 kernel: [ 1603.409561] Loading iSCSI transport
> class v2.0-870.
> Apr 15 21:10:17 sunny2 kernel: [ 1603.486634] iscsi: registered transport 
> (tcp)
> Apr 15 21:10:18 sunny2 kernel: [ 1603.848719] iscsi: registered transport 
> (iser)
> Apr 15 21:10:18 sunny2 iscsid: iSCSI logger with pid=5912 started!
> Apr 15 21:10:18 sunny2 kernel: [ 1604.408284] scsi2 : iSCSI Initiator
> over TCP/IP
> Apr 15 21:10:19 sunny2 iscsid: transport class version 2.0-870. iscsid
> version 2.0-865
> Apr 15 21:10:19 sunny2 iscsid: iSCSI daemon with pid=5914 started!
> Apr 15 21:10:19 sunny2 iscsid: Could not verify connection 1:2. Dropping 
> event.
> Apr 15 21:10:19 sunny2 iscsid: Could not verify connection 1:2. Dropping 
> event.

Are you building the open-iscsi tools or are they part of the distro you 
are using?

Are you also using qla4xxx or just using iscsi_tcp?

If you are building your own tools make sure if you are using a 64 bit 
kernel then the tools are also compiled as 64 bits.

Make sure that you only have one set of tools installed. Do a whereis 
iscsid and whereis iscsiadm.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to