On 02/08/2013 11:05 PM, David Hostetler wrote: > 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 do not remember you saying anything a no records found error? What command are you running when you get that 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... So do you mean before you run the iscsiadm rescan command you do not see sdb and sdc but when you run the command then you can see it? If so then check dmesg. I noticed some kernel messages in some kernels/distros will send the device scanning info there instead of /var/log/messages. However, when you run the login command it will do a scsi scan, so you should not have to do a login then right after that do a rescan command to see new devices. If you are logged in, then modify the targets luns, then you might have to do a rescan after modifying the luns on the target side though. -- 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.
