On 06/16/2011 01:27 PM, Seth Simons wrote: > Hi, > > As suggested, I'm trying iscsistart -b. The be2iscsi module is already > loaded at this point. The iscsi_tcp stuff is irrelevant, that's just > what i've used to get the system booted so I can capture more detailed > log output. > > At the moment i'm in a debian initramfs, which is being booted by the > be3 card's int13h boot (using grub, etc). I've made the initramfs have > a few extra utilities in it for fiddling with things. > > On boot, the be2iscsi module (i've tried 2.6.39, and 3.0.0-rc3 with > the same result) detects both be3 devices: > > (initramfs) dmesg| grep scsi0 > [ 10.075882] scsi0 : ServerEngines 10Gbe open-iscsi Initiator Driver > (initramfs) dmesg| grep scsi1 > [ 16.267943] scsi1 : ServerEngines 10Gbe open-iscsi Initiator Driver > > iscsistart -f also spits out the expected boot info: > > (initramfs) iscsistart -f > iscsistart: transport class version 2.0-870. iscsid version 2.0-872 > # BEGIN RECORD 2.0-872 > iface.initiatorname = iqn.2011-05.com.travelfusion.testserver > iface.hwaddress = d4:85:64:56:90:c9 > iface.bootproto = STATIC > node.name = iqn.2003-10.com.lefthandnetworks:thm-san:25:testserver > node.conn[0].address = 10.10.12.100 > node.conn[0].port = 3260 > # END RECORD > > The expected bits & pieces do appear in /sys/firmware/iscsi_boot_* > however, i'm slightly concerned that the transport version is 2.0-870
This is ok. I just have not udpated the version number in the kernel interface module for a while. I was planning on doing it when there is a change in the interface. > and the iscsid version is 2.0-872. I can't figure out how to get the > kernel modules in the open-iscsi git source to compile against 2.6.39 > or 3.0.0-rc3 I have stopped updating the kernel modules in the tarball. The stable kernels or newest upstream kernel.org kernel is best, or if your distro supports iscsi then that might be best (they normally pick stuff up from the stable upstream kernels). > > Detection with sendtargets via the be2iscsi interfaces does seem to > work correctly, assuming I run the following commands: > > (initramfs) iscsiadm -m iface -I be2iscsi.d4:85:64:56:90:c9 -o update > -n iface.initiatorname -v iqn.2011-05.com.travelfusion.testserver > (initramfs) iscsiadm -m discovery -t st -I be2iscsi.d4:85:64:56:90:c9 > -p 10.10.12.100 Ah, normally you need iscsid running when iscsiadm is run. I think normally people just run iscsistart in the initramfs, then when the system runs on the real root we start iscsid and do discovery. Do you just get an error about not being able to connect to iscsid and that the default initiatorname being used when you ran the command above or does iscsiadm just return a failure or nothing? > > Running iscsistart -b *does* detect the correct target and attempt to > login to it, but fails: > > (initramfs) iscsistart -b > iscsistart: transport class version 2.0-870. iscsid version 2.0-872 > iscsistart: version 2.0-872 > iscsistart: Logging into > iqn.2003-10.com.lefthandnetworks:thm-san:25:thm-vmutil01-root > 10.20.128.100:3260,1 > [ 2468.736422] (beiscsi_process_cq():1953):CQ Error 13, reset CID 0x100... Yeah, seems like from just that the target dropped the connection on us. If you just do a normal boot from local disk then try to use be2iscsi can you login to the target? -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
