<HTML dir="ltr"><HEAD><TITLE>Re: [gPXE] SANBOOT failed Input/Output Error</TITLE>
</HEAD>
<BODY>
<DIV id="idOWAReplyText79746" dir="ltr">
<DIV dir="ltr"><FONT face="Arial" size="2" color="#000000">I am going to hook up a serial port to the box and debug it this weekend. I am hoping that I can narrow down the issue once I know what is going on.</FONT></DIV>
<DIV dir="ltr"><FONT face="Arial" size="2">Mike</FONT></DIV></DIV>
<DIV dir="ltr"><BR>
<HR tabIndex="-1">
<FONT face="Tahoma" size="2"><B>From:</B> Guo-Fu Tseng [mailto:cooldavid@cooldavid.org]<BR><B>Sent:</B> Thu 10/7/2010 3:53 AM<BR><B>To:</B> Michael A. Collins<BR><B>Cc:</B> gPXE Mailing List<BR><B>Subject:</B> Re: [gPXE] SANBOOT failed Input/Output Error<BR></FONT><BR></DIV>
<DIV>
<P><FONT size="2">On Wed, 06 Oct 2010 20:27:22 -0400, Mike Collins wrote<BR>> On Wed, 2010-10-06 at 11:43 +0800, Guo-Fu Tseng wrote:<BR>> > On Mon, 4 Oct 2010 23:46:27 -0400, Michael A. Collins wrote<BR>> > > This is offically driving me mad! I just setup a iSCSI-SCST box with<BR>> > > the put_page patches applied and verified that it works by installing<BR>> > > Fedora 13 from a box to a target. Now when I go to boot the dang<BR>> > > thing it doesn't seem to want to. my iqn is right and whether I type<BR>> > > it in from the gPXE command-line or set it with option 17, the result<BR>> > > is the same. I can see the box connect to my target, but after a few<BR>> > > back and forths I get the following in my target logs: iscsi-scst:<BR>> > > __iscsi_state_change:437:***ERROR***: Connection with initiator<BR>> > > iqn.2000-09.org.etherboot:UNKNOWN unexpectedly closed!<BR>> > ><BR>> > > This is the only error message that I can make out. I tried capturing<BR>> > > the traffic at the target box, but that's even more confusing. The<BR>> > > last few packets were the following: target -> client : SCSI: Data In<BR>> > > LUN: 0x00 (Read Capacity(10) Response Data) client -> target : [PSH, ACK]<BR>> > > client -> target : [FIN, PSH, ACK]<BR>> > > target -> client : [FIN, ACK]<BR>> > > target -> client : [FIN, ACK]<BR>> > > target -> client : [FIN, ACK]<BR>> > > target -> client : [FIN, ACK]<BR>> > > target -> client : [FIN, ACK]<BR>> > ><BR>> > > So, my question is what the heck is going on here. Obviously, the<BR>> > > target must be working or I wouldn't have been able to install the<BR>> > > client box in the first place. The partition is bootable and there,<BR>> > > checked by mounting locally and verifying with fdisk and lvm. Where<BR>> > > can I start looking from the gPXE side, is there a way to dump a bunch<BR>> > > of iscsi logs to the screen during sanboot? I want to make sure that<BR>> > > I'm troubleshooting the right piece. Any help would be great! I have<BR>> > > attached a capture file and an exerpt from my target logs. Mike<BR>> > Hi Mike:<BR>> > This issue looks familiar to me.<BR>> > It seems related to the TCP stack fix I worked on before.<BR>> > Could you see if this branch solve the problem:<BR>> > git clone -b tcpfix2 git://git.etherboot.org/scm/people/cooldavid/gpxe.git<BR>> ><BR>> > Guo-Fu Tseng<BR>> ><BR>> No change. Still recieving the same error.<BR>> Mike<BR>Thanks for trying.<BR><BR>So you still got:<BR>> client -> target : [FIN, PSH, ACK]<BR>> target -> client : [FIN, ACK]<BR>> target -> client : [FIN, ACK]<BR>> target -> client : [FIN, ACK]<BR>> target -> client : [FIN, ACK]<BR>> target -> client : [FIN, ACK]<BR>Behavior?<BR><BR>It seem the fix is still missing some check points.<BR>Or something went wrong earlier then gPXE handing<BR>off the control to the OS.<BR><BR>Guo-Fu Tseng<BR><BR></FONT></P></DIV></BODY></HTML>