Re: INQUIRY result too short (5), using 36
Matthew Schumacher wrote: Matthew Schumacher wrote: Thanks Mike, I'll try another kernel and report back. If I use kernels 2.6.27.7, 2.6.27.34, or 2.6.28.10 (what I had on hand) I get the very same error message after iscsi connects: scsi2 : iSCSI Initiator over TCP/IP scsi scan: INQUIRY result too short (5), using 36 Why it works in my initram fs is beyond me. One thing that is interesting is what /sys/bus/scsi/devices shows. I see a host entry for iscsi, but no targets or devices. It looks like everything comes up except the scsi layer. schu Ok, I'm a complete retard. It's very embarrassing to admit publicly, but I failed to bind a lun to the target on the iscsi server side so that is why it didn't find one. Sounds like I need to slow down and only work one project at a time. Sorry for the waisted time, hopefully this will help someone in the future. schu --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: INQUIRY result too short (5), using 36
Matthew Schumacher wrote: Thanks Mike, I'll try another kernel and report back. If I use kernels 2.6.27.7, 2.6.27.34, or 2.6.28.10 (what I had on hand) I get the very same error message after iscsi connects: scsi2 : iSCSI Initiator over TCP/IP scsi scan: INQUIRY result too short (5), using 36 Why it works in my initram fs is beyond me. One thing that is interesting is what /sys/bus/scsi/devices shows. I see a host entry for iscsi, but no targets or devices. It looks like everything comes up except the scsi layer. schu --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
INQUIRY result too short (5), using 36
I'm setting up open-iscsi on slackware 12.2. I built a initrd image that loads up the modules, logs in, and mounts root on iscsi and all is well until after the machine is running and I want to connect to another iscsi target. This causes strange behavior: 1. I can kill iscsid and everything keeps working. I've not seen this before. In the past I needed to have iscsid running in order to do anything since root is on iscsi. Anyone know why this is? 2. If try to login to a target right after boot I get: iscsiadm: initiator reported error (13 - daemon access denied) however, after I restart iscsid I get, Login to [iface: default, target: mail, portal: x.x.x.x,3260]: successful which looks good except I don't get my scsi disks setup in /dev. Looking at dmesg shows: scsi2 : iSCSI Initiator over TCP/IP scsi scan: INQUIRY result too short (5), using 36 This was working fine in slackware 12.1 so the only major difference is the kernel which is now 2.6.27.7. Anyone know what is up with this and how to fix it? Is git head stable enough to try it? schu --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
