LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Red Hat (https://www.linuxquestions.org/questions/red-hat-31/)
-   -   No disk device created when iSCSI initiator logs in (https://www.linuxquestions.org/questions/red-hat-31/no-disk-device-created-when-iscsi-initiator-logs-in-916250/)

lhenders326 11-29-2011 03:15 PM

No disk device created when iSCSI initiator logs in
 
I am trying to get Open-iSCSI to work on a Red Hat Enterprise Server v5.5. I can log in to the target just fine and see the sessions with teh iscsiadm -m node command. This happens across reboots of the system. What I never see is a drive device created for the iSCSI volume. There is no /dev/sde created, nothing in /dev/disk/by_path that points to an iSCSI path, no indication that a disk device was created. This happens on two Red Hat servers with different hardware. I can use the initiator in Windows 2008 R2 and create a volume with no problem on the target, but not on the Red Hat servers. I have contacted Red Hat support, but they are no help.

kbp 12-01-2011 04:17 PM

Quote:

and see the sessions with teh iscsiadm -m node command.
.. not sure how you see sessions with the node command.. try 'iscsiadm -m session'

mikey99 12-02-2011 04:17 AM

Quote:

Originally Posted by lhenders326 (Post 4537661)
I am trying to get Open-iSCSI to work on a Red Hat Enterprise Server v5.5. I can log in to the target just fine and see the sessions with teh iscsiadm -m node command. This happens across reboots of the system. What I never see is a drive device created for the iSCSI volume. There is no /dev/sde created, nothing in /dev/disk/by_path that points to an iSCSI path, no indication that a disk device was created. This happens on two Red Hat servers with different hardware. I can use the initiator in Windows 2008 R2 and create a volume with no problem on the target, but not on the Red Hat servers. I have contacted Red Hat support, but they are no help.

Assuming you are doing the following on the client to your server on 192.168.0.200 ....

Code:

# iscsiadm -m discovery -t sendtargets -p 192.168.0.200

# iscsiadm -m node -T iqn.2011-11.com.somedomain:diskname -p 192.168.0.200 -l

It is important to use the IP address, not the hostname of your server when logging in to the target.

If successful, the kernel should report the event. To see this, type

Code:

# dmesg
and check the kernel messages. It should tell you the name of the device created.

lhenders326 12-05-2011 02:11 PM

Quote:

Originally Posted by kbp (Post 4539541)
.. not sure how you see sessions with the node command.. try 'iscsiadm -m session'

Here is the output of the two commands:

# iscsiadm -m node
10.112.100.54:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging2
10.110.1.108:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging2
10.112.100.54:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging1
10.110.1.108:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging1

# iscsiadm -m session
tcp: [1] 10.112.100.54:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging2
tcp: [2] 10.110.1.108:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging2
tcp: [3] 10.112.100.54:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging1
tcp: [4] 10.110.1.108:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging1

They output essentially the same information. I'm starting to think that becaue teh same target shows up on two different networks that MPIO needs to be installed.

lhenders326 12-05-2011 02:14 PM

Quote:

Originally Posted by mikey99 (Post 4540010)
Assuming you are doing the following on the client to your server on 192.168.0.200 ....

Code:

# iscsiadm -m discovery -t sendtargets -p 192.168.0.200

# iscsiadm -m node -T iqn.2011-11.com.somedomain:diskname -p 192.168.0.200 -l

It is important to use the IP address, not the hostname of your server when logging in to the target.

If successful, the kernel should report the event. To see this, type

Code:

# dmesg
and check the kernel messages. It should tell you the name of the device created.

I have used the discovery and login commands many times already. Looking through dmesg I see where the iscsi software is intialized but no devices are created. Since the discovery finds the same target on two different IP networks does MPIO need to be installed?

dudegolfin 02-21-2013 10:05 AM

Resolution?
 
Were you able to resolve this issue? I'm facing the same issue, so if you have, I'd be interested to know about the resolution.

Thank You

rhel5 10-09-2014 12:33 AM

also having this issue
 
Sorry to Necro... but I am having the same issue. I confirmed I am logged in but no storage devices were created. I was able to get a device listed as /dev/sdb the first time, but afterwards, I never got it back. I already re-installed my RHEL6.5 machine, but no luck.

If anyone can chime in, that would be great. Thanks much.

[root@station6 log]# iscsiadm -m discovery -t st -p 192.168.1.6
Starting iscsid: [ OK ]
192.168.1.6:3260,1 iqn.1994-05.com.redhat:9dea827d1bf8

[root@station6 log]# iscsiadm -m node -T iqn.1994-05.com.redhat:9dea827d1bf8 -p 192.168.1.6 -l
Logging in to [iface: default, target: iqn.1994-05.com.redhat:9dea827d1bf8, portal: 192.168.1.6,3260] (multiple)
Login to [iface: default, target: iqn.1994-05.com.redhat:9dea827d1bf8, portal: 192.168.1.6,3260] successful.

[root@station6 log]# dmesg | tail
Chelsio T4 iSCSI Driver cxgb4i v0.9.1 (Aug. 2010)
iscsi: registered transport (cxgb4i)
cnic: Broadcom NetXtreme II CNIC Driver cnic v2.5.16 (Dec 05, 2012)
Broadcom NetXtreme II iSCSI Driver bnx2i v2.7.6.2 (Jun 06, 2013)
iscsi: registered transport (bnx2i)
iscsi: registered transport (be2iscsi)
In beiscsi_module_init, tt=fa4333e0
scsi2 : iSCSI Initiator over TCP/IP
scsi 2:0:0:0: RAID IET Controller 0001 PQ: 0 ANSI: 5
scsi 2:0:0:0: Attached scsi generic sg2 type 12

[root@station6 log]# service iscsi status
iSCSI Transport Class version 2.0-870
version 6.2.0-873.10.el6
Target: iqn.1994-05.com.redhat:9dea827d1bf8
Current Portal: 192.168.1.6:3260,1
Persistent Portal: 192.168.1.6:3260,1
**********
Interface:
**********
Iface Name: default
Iface Transport: tcp
Iface Initiatorname: iqn.1994-05.com.redhat:9551d3923f9c
Iface IPaddress: 192.168.1.10
Iface HWaddress: <empty>
Iface Netdev: <empty>
SID: 1
iSCSI Connection State: LOGGED IN
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE
*********
Timeouts:
*********
Recovery Timeout: 120
Target Reset Timeout: 30
LUN Reset Timeout: 30
Abort Timeout: 15
*****
CHAP:
*****
username: <empty>
password: ********
username_in: <empty>
password_in: ********
************************
Negotiated iSCSI params:
************************
HeaderDigest: None
DataDigest: None
MaxRecvDataSegmentLength: 262144
MaxXmitDataSegmentLength: 8192
FirstBurstLength: 65536
MaxBurstLength: 262144
ImmediateData: Yes
InitialR2T: Yes
MaxOutstandingR2T: 1
************************
Attached SCSI devices:
************************
Host Number: 2 State: running
scsi2 Channel 00 Id 0 Lun: 0


All times are GMT -5. The time now is 08:05 PM.