[gPXE] SANBOOT failed Input/Output Error

[Mike Collins]

On Mon, 2010-10-04 at 23:46 -0400, Michael A. Collins wrote:
> This is offically driving me mad!  I just setup a iSCSI-SCST box with
> the put_page patches applied and verified that it works by installing
> Fedora 13 from a box to a target.  Now when I go to boot the dang
> thing it doesn't seem to want to.  my iqn is right and whether I type
> it in from the gPXE command-line or set it with option 17, the result
> is the same.  I can see the box connect to my target, but after a few
> back and forths I get the following in my target logs:
> iscsi-scst: __iscsi_state_change:437:***ERROR***: Connection with
> initiator iqn.2000-09.org.etherboot:UNKNOWN unexpectedly closed!
> 
> This is the only error message that I can make out.  I tried capturing
> the traffic at the target box, but that's even more confusing.  The
> last few packets were the following:
> target -> client : SCSI: Data In LUN: 0x00 (Read Capacity(10) Response
> Data)
> client -> target : [PSH, ACK]
> client -> target : [FIN, PSH, ACK]
> target -> client : [FIN, ACK]
> target -> client : [FIN, ACK]
> target -> client : [FIN, ACK]
> target -> client : [FIN, ACK]
> target -> client : [FIN, ACK]
> 
> So, my question is what the heck is going on here.  Obviously, the
> target must be working or I wouldn't have been able to install the
> client box in the first place.  The partition is bootable and there,
> checked by mounting locally and verifying with fdisk and lvm.  Where
> can I start looking from the gPXE side, is there a way to dump a bunch
> of iscsi logs to the screen during sanboot?  I want to make sure that
> I'm troubleshooting the right piece.  Any help would be great!  I have
> attached a capture file and an exerpt from my target logs.
> Mike
> 
> 
Interesting.  I removed gPXE and sanboot from the equation and setup
pxelinux to serve up the kernel and initrd off the boot partition of the
installed target disk and it booted no problems.  This seems like I need
to look at gPXE's implementation of iSCSI and see if I can turn on some
logging to determine the issue.  Sounds like a fun weekend project!
Mike