What Target are you using? I beat my head on a issue when I first setup regarding access permissions. If you don't have the permissions right on the array, open-iscsi will let you see it but not log in. Another thing you may want to check, if you are sharing luns between systems, some arrays require you to explicitly allow that behavior. And last but not least, if you have a backend and a front end connection make sure you are connecting to the array with the right interface. Make sure one connection does not have a matching MTU *jumbo frames with the array it can cause strange behavior.
On Apr 15, 10:27 pm, sundar mahadevan <sundarmahadeva...@gmail.com> 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. > Apr 15 21:10:20 sunny2 kernel: [ 1606.064265] scsi3 : iSCSI Initiator > over TCP/IP > Apr 15 21:10:21 sunny2 iscsid: Could not verify connection 2:3. Dropping > event. > Apr 15 21:10:21 sunny2 iscsid: Could not verify connection 2:3. Dropping > event. > Apr 15 21:10:21 sunny2 kernel: [ 1607.592257] scsi4 : iSCSI Initiator > over TCP/IP > Apr 15 21:10:22 sunny2 iscsid: Could not verify connection 3:4. Dropping > event. > Apr 15 21:10:22 sunny2 iscsid: Could not verify connection 3:4. Dropping > event. > Apr 15 21:10:23 sunny2 kernel: [ 1609.120249] scsi5 : iSCSI Initiator > over TCP/IP > Apr 15 21:10:24 sunny2 iscsid: Could not verify connection 4:5. Dropping > event. > Apr 15 21:10:24 sunny2 iscsid: Could not verify connection 4:5. Dropping > event. > Apr 15 21:15:00 sunny2 kernel: [ 1886.664257] scsi6 : iSCSI Initiator > over TCP/IP > Apr 15 21:15:01 sunny2 iscsid: Could not verify connection 5:6. Dropping > event. > Apr 15 21:15:01 sunny2 kernel: [ 1886.946886] scsi 6:0:0:0: > Direct-Access IET VIRTUAL-DISK 0 PQ: 0 ANSI: 4 > Apr 15 21:15:01 sunny2 kernel: [ 1886.952267] sd 6:0:0:0: [sdb] > 1892352 512-byte hardware sectors (969 MB) > Apr 15 21:15:01 sunny2 kernel: [ 1886.956338] sd 6:0:0:0: [sdb] Write > Protect is off > Apr 15 21:15:01 sunny2 kernel: [ 1886.956365] sd 6:0:0:0: [sdb] Mode > Sense: 77 00 00 08 > Apr 15 21:15:01 sunny2 kernel: [ 1886.964101] sd 6:0:0:0: [sdb] Write > cache: disabled, read cache: enabled, doesn't support DPO or FUA > Apr 15 21:15:01 sunny2 kernel: [ 1886.976089] sd 6:0:0:0: [sdb] > 1892352 512-byte hardware sectors (969 MB) > Apr 15 21:15:01 sunny2 kernel: [ 1886.986197] sd 6:0:0:0: [sdb] Write > Protect is off > Apr 15 21:15:01 sunny2 kernel: [ 1886.986228] sd 6:0:0:0: [sdb] Mode > Sense: 77 00 00 08 > Apr 15 21:15:01 sunny2 kernel: [ 1887.000082] sd 6:0:0:0: [sdb] Write > cache: disabled, read cache: enabled, doesn't support DPO or FUA > Apr 15 21:15:01 sunny2 kernel: [ 1887.002741] sdb: unknown partition table > Apr 15 21:15:01 sunny2 kernel: [ 1887.042501] sd 6:0:0:0: [sdb] > Attached SCSI disk > Apr 15 21:15:01 sunny2 kernel: [ 1887.043773] sd 6:0:0:0: Attached > scsi generic sg1 type 0 > Apr 15 21:15:02 sunny2 iscsid: connection5:0 is operational now > Apr 15 21:15:20 sunny2 iscsid: Could not get host for sid 5. > Apr 15 21:15:20 sunny2 iscsid: could not get host_no for session 6. > Apr 15 21:15:20 sunny2 iscsid: could not find session info for session5 > Apr 15 21:15:20 sunny2 iscsid: session > [iqn.2001-04.com.ubuntu:scsi.disk.vg1.vote,192.168.20.22,3260] already > running. > Apr 15 21:15:28 sunny2 iscsid: Nop-out timedout after 15 seconds on > connection 5:0 state (3). Dropping session. > Apr 15 21:15:28 sunny2 iscsid: connection5:0 is operational after > recovery (1 attempts) > Apr 15 21:15:33 sunny2 iscsid: Could not get host for sid 5. > Apr 15 21:15:33 sunny2 iscsid: could not get host_no for session 6. > Apr 15 21:15:33 sunny2 iscsid: could not find session info for session5 > Apr 15 21:15:33 sunny2 iscsid: session > [iqn.2001-04.com.ubuntu:scsi.disk.vg1.asm,192.168.20.22,3260] already > running. > Apr 15 21:15:54 sunny2 iscsid: Nop-out timedout after 15 seconds on > connection 5:0 state (3). Dropping session. > Apr 15 21:15:54 sunny2 iscsid: connection5:0 is operational after > recovery (1 attempts) > > Could someone help me please. I have been battling to figure this out > for a while. It really is frustrating that nothing works. Thanks in > advance. > > On Wed, Apr 15, 2009 at 3:58 PM, sundar mahadevan > > <sundarmahadeva...@gmail.com> wrote: > > Could someone please help me with this issue..... > > > On Wed, Apr 15, 2009 at 11:41 AM, sundar mahadevan > > <sundarmahadeva...@gmail.com> wrote: > >> Hi, > >> I'm a newbie trying to setup open-iscsi on ubuntu 8.10(kernel 2.6.27-11). > > >> I created 3 logical volumes(asm : 37G, ocr: 2G and vote 1G) under a > >> volume group vg1 comprising of 3 physical volumes (totalling 40G) > > >> Here are my commands from client side: > > >> sudo iscsiadm -m discovery -t st -p 192.168.20.22 > > >> lists: > >> 192.168.20.22:3260,1 iqn.2001-04.com.ezhome:scsi.disk.vg1.asm > >> 192.168.20.22:3260,1 iqn.2001-04.com.ezhome:scsi.disk.vg1.ocr > >> 192.168.20.22:3260,1 iqn.2001-04.com.ezhome:scsi.disk.vg1.vote > > >> sudo /etc/init.d/open-iscsi restart > > >> sudo iscsiadm -m node -T iqn.2001-04.com.ezhome:scsi.disk.vg1.asm > >> -p 192.168.20.22 -o update -n node.conn[0].startup -v automatic > > >> sudo iscsiadm -m node -T iqn.2001-04.com.ezhome:scsi.disk.vg1.ocr > >> -p 192.168.20.22 -o update -n node.conn[0].startup -v automatic > > >> sudo iscsiadm -m node -T iqn.2001-04.com.ezhome:scsi.disk.vg1.vote > >> -p 192.168.20.22 -o update -n node.conn[0].startup -v automatic > > >> sudo /etc/init.d/open-iscsi restart > > >> fdisk -l and dmesg > > >> 1) list a new drive /dev/sdb of size 39.7 GB but there should be 2 > >> more drives and the size of /dev/sdb is surprising because there are > >> no drives of size 39.7G > > >> 2) What am i missing here for other 2 drives to be visible. > > >> 3) Changes made to /etc/ietd.conf and then /etc/init.d/open-iscsi > >> restart does not get reflected. I have to reboot the system to notice > >> the changes. Any ideas? > > >> 4) am i supposed to use /etc/init.d/iscsitarget stop/restart to stop > >> and restart iscsitargets? > > >> Thanks in advance. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
