I have it working now. I am guessing that when I did the Tarball install for open-iscsi, it polluted the CentOS kernel drivers. Since this was a fresh build, I just did a new install of CentOS 5.3, followed your instructions and everything just worked. Life is good and I learned alot along the way about iSCSI, openfiler, etc.
Thanks for your help on this. Much appreciated. Clint On Tue, Jul 28, 2009 at 12:15 PM, Mike Christie <micha...@cs.wisc.edu>wrote: > Clint wrote: > >> Going to try to replay to this again... >> >> I am stopped now with a message "12 - iSCSI driver not found" I >> performed the yum install of the iscsi-initiator-utils and service >> iscsi starts clean with the only message of "No records found!" >> > > That just means you have not run the discovery command yet or there were > not targets found when you run it. It is ok. > > > >> Here is what I have on boot now: >> >> [r...@iscsi ~]# service iscsi status >> iscsid (pid 1387 1386) is running... >> [r...@iscsi ~]# iscsiadm -m discovery -t st -p 192.168.100.4 >> 192.168.100.4:3260,1 iqn.1986-03.com.hp:storage.msa2012i.0824d5872b.a >> 192.168.100.5:3260,2 iqn.1986-03.com.hp:storage.msa2012i.0824d5872b.a >> [r...@iscsi ~]# iscsiadm -m node -l >> Logging in to [iface: default, target: iqn. >> 1986-03.com.hp:storage.msa2012i.0824d5872b.a, portal: >> 192.168.100.4,3260] >> Logging in to [iface: default, target: iqn. >> 1986-03.com.hp:storage.msa2012i.0824d5872b.a, portal: >> 192.168.100.5,3260] >> iscsiadm: Could not login to [iface: default, target: iqn. >> 1986-03.com.hp:storage.msa2012i.0824d5872b.a, portal: >> 192.168.100.4,3260]: >> iscsiadm: initiator reported error (12 - iSCSI driver not found. >> Please make sure it is loaded, and retry the operation) >> iscsiadm: Could not login to [iface: default, target: iqn. >> 1986-03.com.hp:storage.msa2012i.0824d5872b.a, portal: >> 192.168.100.5,3260]: >> iscsiadm: initiator reported error (12 - iSCSI driver not found. >> Please make sure it is loaded, and retry the operation) >> [r...@iscsi ~]# iscsiadm -m session >> iscsiadm: No active sessions. >> >> Listing what is loaded.... >> >> lsmod | grep iscsi >> libiscsi 43148 0 >> scsi_transport_iscsi 35212 2 libiscsi >> scsi_mod 141589 9 >> >> libiscsi,scsi_transport_iscsi,scsi_dh,libata,sg,mptspi,mptscsih,scsi_transport_spi, >> >> I am still wondering about iscsi_tcp which won't load and if that is >> the driver that is missing. >> > > Yeah, iscsi_tcp is what you need. > > It is strange that libiscsi and scsi_transport_iscsi got loaded but > iscsi_tcp did not. > > You can do > > modprobe iscsi_tcp > > manually to load it. If you run that command do you then see iscsi_tcp when > you run lsmod? > > > > >> Thanks in Advance for your help. >> >> Clint >> >> On Jul 27, 3:35 pm, Mike Christie <micha...@cs.wisc.edu> wrote: >> >>> On 07/25/2009 12:34 PM, Clint wrote: >>> >>> >>> >>> >>> >>> Hello, >>>> I am fairly new to iSCSI implementations on Linux (and Windows). I >>>> had an existing implementation that was running on Slackware 12.1 but >>>> "self distruction" and was never documented. I have attempted to >>>> rebuild the connection as data exists that I need to recover but can't >>>> even get iscsiadm to run on the Slackware 12.1 system. I have build a >>>> new Centos 5.3 (el5), fully updated, and have installed the latest >>>> stable build of open-iscsi. I had to do the make KSRC command to get >>>> a succesful build, a straight make install did not work but running >>>> make install after the make KSRC did complete succesfully. However >>>> when I try to start open-isci, I get the following error (kernerl is >>>> 2.6.18-128.2.1.el5 #1 SMP): >>>> /etc/init.d/open-iscsi start >>>> Starting iSCSI initiator service: FATAL: Error inserting iscsi_tcp (/ >>>> lib/modules/2.6.18-128.2.1.el5/kernel/drivers/scsi/iscsi_tcp.ko): >>>> Unknown symbol in module, or unknown parameter (see dmesg) >>>> FATAL: Error inserting ib_iser (/lib/modules/2.6.18-128.2.1.el5/kernel/ >>>> drivers/infiniband/ulp/iser/ib_iser.ko): Unknown symbol in module, or >>>> unknown parameter (see dmesg) >>>> Are these really FATAL errors or do I need to deal with this? I did >>>> some Googling and did not arrive at a definitive answer. >>>> >>> If you are using iser you should be concerned. If not then then you can >>> ignore. >>> >>> You can actually just use the iscsi-initiator-utils package and kernel >>> that comes with Centos 5.3 and do not need the open-iscsi.org tarball. >>> >>> To install the iscsi tools in Centos do >>> >>> yum install iscsi-initiator-utils >>> >>> >>> >>> Should I consider a different distribution? >>>> Given the above resolution, what are my next steps, the README is not >>>> clear on this. Do I need to configure the iscsid.conf file first. >>>> What about the iface0 file? Does it need a hardware address and is >>>> that the same as eth0 or something else? When to use iscsiadm, it >>>> appears to be able to some of the heavy listing. >>>> Would appreaciate any direction I can get on this. Some additional >>>> information that may or may not be helpful. >>>> initiatorname.iscsi: >>>> InitiatorName=iqn.2005-03.org.open-iscsi:292f1499dcaa >>>> >>> For the basics you only need to follow 7.0 of the README (Centos follows >>> the red hat notes in there). >>> >>> After you have done >>> yum install iscsi-initiator-utils >>> >>> >>> >>> target info: >>>> ign.1986-03.com.hp:storage.msa1012i.0824d5872b.a >>>> HP MAS1012i SCSI Disk Drive >>>> 192.168.100.4:3260 >>>> >>> you can do >>> >>> #service iscsi start >>> # iscsiadm -m discovery -t st -p 192.168.100.4 >>> >>> you should then see some targets and portals get spit out >>> >>> you can then >>> >>> do >>> >>> # iscsiadm -m node -l >>> >>> this will log into all the targets. Then do >>> >>> # iscsiadm -m session -P 3 >>> >>> to see some iscsi info (more info on that is in the readme section 9). >>> >>> Then you can run iscsiadm by hand to logout or you can do >>> >>> service iscsi stop >>> >>> Then on the next reboot, the iscsi service should get started >>> automatically and login to the targets found above. >>> >>> You only need to the iface stuff if you want to bind a session to a >>> specific nic. Probably best to try the basics above first. >>> >>> >>> >>> I can ping the target from the Linux system.- Hide quoted text - >>>> >>> - Show quoted text -- Hide quoted text - >>> >>> - Show quoted text - >>> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
