iPXE discussion forum
iSCSI ipxe.pxe/sanboot error 1d704098 - Printable Version

+- iPXE discussion forum (https://forum.ipxe.org)
+-- Forum: iPXE user forums (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: iSCSI ipxe.pxe/sanboot error 1d704098 (/showthread.php?tid=22669)

iSCSI ipxe.pxe/sanboot error 1d704098 - IBIT.ZEE - 2020-05-15 23:48

I have a Windows 2016 configured as iSCSI Target... Angel

I connect OK to the iSCSI drives from other machines in the LAN
with the Microsoft iSCSI client (iscsicpl.exe) Cool

When I try to connect via ipxe.efi/sanboot it gaves me this error:
"Could not open SAN device: Input/output error (http://ipxe.org/1d704098)" Dodgy

consulting the suggested URL:
Possible sources
This error originated from one of the following locations
within the iPXE source code:
drivers/block/scsi.c (line 494)

the ipxe script lines for the iscsi config/invoke are:
set initiator-iqn iqn.1991-05.com.microsoft:server1
sanboot iscsi: ||

* is the NIC I have on server1 for iSCSI service
* as I said... it connects OK with the Windows iSCSI client

I downloaded the last ipxe.efi binary from "http://boot.ipxe.org"
and try other 2 older binaries with the same result...

?does anyone have any ideas where to look?? HuhAngry

RE: iSCSI ipxe.pxe/sanboot error 1d704098 - IBIT.ZEE - 2020-05-18 17:16

Well--- as "always"... it is a somewhat stupid thing... Undecided

I was assuming that the first-and-only disk I have set in the Server (Target) was LUN0...

and I was using the simple iSCSI URI: Angel


as "always"... there are Microsoft things that only Micro$oft '''understand''': Angry
the target disk (the only one in the system) was beeing set as LUN1???

as I can't see this information in the Windows Server Target
only with a diagnostic tool i could find that LUN1 (and not LUN0)
was being set by the iSCSI Server



works fine... Cool