(2017-03-13 22:56)nvcd7026 Wrote:  Hi all,

I switched to the latest ipxe build (fdcdc) (git://git.ipxe.org/ipxe.git), but somehow I'm not able to sanboot with iscsi anymore. It gives an error, showing "Could not open San device: error 0x3f122003". Both UEFI and BIOS mode encounter the same error.

However if I switch back to the old build 30f9, the San device is correctly registered, no error occurs with booting.

(server: Ubuntu 16.04 with iscsitarget (iSCSI Enterprise Target))

Here is the menu entry:

:Win10-installer
dhcp net0
set net0/gateway 0.0.0.0
set keep-san 1
sanhook --drive 0x81 iscsi:${fog-ip}::::workgroup:install-test
set path /fog/win10-installer-1607
kernel http://${fog-ip}/fog/boot/winpe/wimboot
initrd http://${fog-ip}${path}/bootmgr BOOTMGR
#initrd http://${fog-ip}${path}/bootmgr.exe bootmgr.exe
initrd http://${fog-ip}${path}/bootmgr.efi bootmgr.efi
initrd http://${fog-ip}${path}/boot/bcd bcd
initrd http://${fog-ip}${path}/boot/boot.sdi boot.sdi
initrd http://${fog-ip}${path}/sources/boot.wim boot.wim
imgstat || echo "ERROR at IMGSTAT"; sleep 3
prompt || echo "ERROR at PROMPT"; sleep 3
boot || echo "ERROR AT BOOT"; sleep 3;goto MENU


The attachments are screenshots with debug mode on (iscsi), taken from hyper-v (UEFI mode). I appreciate any helps!

https://imgur.com/a/JT83O

------
Edit:

I tested with the package targetcli today, and the san device registered normally; so I think the problem might be about IET(iSCSI Enterprise Target) and ipxe.