Yes you essentially have it right. I tried to logout / login to the LUNS and I am getting the same "no record found" error.
I just booted the hosts up (they weren't working, I was at work, why suck the electrons right?) and tried to logout / login on the LUNS, rescan the session etc... but no entries beyond initializing NTP are showing up on the initiator in question. When I rescan the session I get the following output... Rescanning session [sid: 1, target: iqn.2013-02.com.example:LUN1, portal: 192.168.5.1,3260] Rescanning session [sid: 2, target: iqn.2013-02.com.example:LUN2, portal: 192.168.5.1,3260] However, when I run fdisk -l on the host, sure enough, both LUNS show up where they ought, in /dev/sdb, and /dev/sdc... Which brings the brain to wondering... Why the no record found errors? Why no log entries giving me info on the login? I haven't changed anything with syslog, or in the iscsi config to put the log elsewhere, although possibly Conga might have done it for me... > So one of the luns (the one for ISCSI_QUORUM_LV) shows up on the se > initiator side initially, but when you reboot the target after adding a > lun for ISCSI_DATA_LV it disappears on the initiator side? The initiator > side does not delete luns unless you run the logout command. It just > adds them (it uses the scsi layer scan interface and it just supports > addition). > > Do you run the iscsiadm command to logout then login again? > > If you stay logged in the entire time, and if you do > > iscsiadm -m session --rescan > > > do you see the luns show up? > > Can you send the /var/log/messages for the initiator side? > > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/open-iscsi?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
