[ipxe-devel] Input/Output error (1d0d6039)

[Lee Bradshaw]

Thanks, Michael.

I've rebuilt and now the recent build is working, although I still get the
same error.

QNAP says it's a login failure, but doesn't tell me why.

This forum thread seems to match:
http://forum.qnap.com/viewtopic.php?f=180&t=23803

Someone said he had a fix for gPXE (which I've attached) but I don't think
I'd care to try inserting a whole source file from another project and a
year ago into the current version. I wonder whether this is any help?

Lee.

-----Original Message-----
From: Michael Brown [mailto:mbrown at fensystems.co.uk] 
Sent: Wednesday, 23 February 2011 9:19 PM
To: ipxe-devel at lists.ipxe.org
Cc: Lee Bradshaw
Subject: Re: [ipxe-devel] Input/Output error (1d0d6039)

On Wednesday 23 Feb 2011 08:35:36 Lee Bradshaw wrote:
> Today I received a QNAP server and configured it for iSCSI.
> 
> Unfortunately iPXE will not connect to the target. I get input/output 
> error 1d0d6039.
> 
> I've attached a trace.

Thanks.  Your trace shows that the target is returning status 0301 "The
iSCSI service or target is not currently operational", which falls within
status class 03 "Target Error - indicates that the target sees no errors in
the initiator's Login Request, but is currently incapable of fulfilling the
request".

I've added a small amount of code to disambiguate this error, which means
that you should see error http://ipxe.org/1d0d6139 with the latest build.
However, I don't know for sure why the target is responding this way.

It's possible that the status 0301 is misleading, and is the way that the
QNAP reports errors such as "initiator not allowed" (which ought to be 0202)
etc.

> I tried doing a git pull and recompiling to get the latest version of 
> iPXE, but this one just hangs at the initial TFTP stage.

Do you mean the stage of downloading undionly.kpxe via TFTP, before iPXE
starts running?  What is the last thing that you see on screen?

Incidentally, there seems to be a major problem with your network; most of
the packets in the trace are duplicated, in some cases hundreds of times,
with decreasing IP TTL.  There are also some spurious ICMP Redirects from
10.10.10.2.  It looks as though the machine 10.10.10.2 (an HP machine with
MAC address 00:18:fe:fd:d5:d6) is somehow set up to forward traffic from the
10.10.10.0/24 subnet back to the same subnet, creating an infinite
forwarding loop for each packet that persists until the IP TTL expires.  You
should probably fix this problem first.

Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: iscsi.rar
Type: application/octet-stream
Size: 12107 bytes
Desc: not available
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20110224/43157c90/attachment.obj>