No disk device created when iSCSI initiator logs in
Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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 ....
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.
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?
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.