[gPXE] Interesting tidbit in dmesg

[Shao Miller]

Dustin Eward wrote:
> [81009.839258] iSCSI Enterprise Target Software - version 1.4.19
> [81009.840067] iscsi_trgt: Registered io type fileio
> [81009.840077] iscsi_trgt: Registered io type blockio
> [81009.840083] iscsi_trgt: Registered io type nullio
> [81195.328539] iscsi_trgt: ioctl(248) can't find the target 1
> [81195.328773] iscsi_trgt: ioctl(248) can't find the target 1
> For every Target I set that has a LUN != 0, ietd tells me it cannot 
> find that Target and lists the LUN number.  Even if that Target was 
> previously LUN 0 and not complained about, simply having a LUN other 
> than 0 results in "can't find the target N"
>  
> The Windows iSCSI Initiator can still utilize it just fine, regardless 
> of whether ietd tells me it can't find it....  I was just looking for 
> a reason why gPXE was giving me "Input/Output error."  This is 
> probably not it (since Windows has no problem with it), but 
> interesting/odd none the less. Figured I'd report....

So are you saying that gPXE cannot boot from this SAN?  Also, are you 
able to read and write to such a SAN target from Windows, restart IETD, 
reconnect from Windows, and find your data intact?

- Shao Miller