(2019-06-09 14:20)ax2401 Wrote:  I had make some workarounds to solve this issue, but I don't know whether it's applicable for you, because when I do the test, I use WinTarget( windows server 2012) as iscsi target, not ISCSI Console.

(2019-06-09 20:31)misty Wrote:  

(2019-06-09 14:20)ax2401 Wrote:  I had make some workarounds to solve this issue, but I don't know whether it's applicable for you, because when I do the test, I use WinTarget( windows server 2012) as iscsi target, not ISCSI Console.

I do not have a Windows Server 2012 system to test this on at the moment. I installed Microsoft iSCSI Software Target 3.3 (an older verison of WinTarget) and tested the ipxe.efi binary file that you linked to (http://sym.ax2401.com:9999/ipxe.efi). Using an Initiator with UEFI Firmware the system still failed at Stage 2 of the Windows installation - crashing the Target and no activity visible on the Initiator system. This appeared identical to the test I carried out myself with a binary I compiled in May of this year.

Misty

(2019-06-09 21:41)ax2401 Wrote:  It's a bad news, but the good things is your issue is the same as which I meet two month ago. (carshing the target when booting windows.)

(2019-06-09 21:41)ax2401 Wrote:  ...I had update the ipex.efi a minute ago , please try again:
http://sym.ax2401.com:9999/ipxe.efi

Because I had made lots of changes to the source in the last two month, it's a little complex to show every changes to you, so please test it again and tell me the result...

(2019-06-09 21:41)ax2401 Wrote:  ...If it still not work, I will make a diff with the origin ipxe source and send to you , so you can research it by yourself.

(2019-06-09 14:20)ax2401 Wrote:  Yes, I test it two month ago, the result is same as yours.

I researched it for tow days and two nights, at last , I fixed it.
I had make some workarounds to solve this issue, but I don't know whether it's applicable for you, because when I do the test, I use WinTarget( windows server 2012) as iscsi target, not ISCSI Console.

You can retry with the follow binaries( compiled with workarounds):

BIOS: http://sym.ax2401.com:9999/ipxe.pxe
UEFI: http://sym.ax2401.com:9999/ipxe.efi


Whether it works or not, please feedback , So I can decide if I need to make a pull request from github to IPXE.

(2019-06-10 19:40)NiKiZe Wrote:  

(2019-06-09 14:20)ax2401 Wrote:  Yes, I test it two month ago, the result is same as yours.

I researched it for tow days and two nights, at last , I fixed it.
I had make some workarounds to solve this issue, but I don't know whether it's applicable for you, because when I do the test, I use WinTarget( windows server 2012) as iscsi target, not ISCSI Console.

You can retry with the follow binaries( compiled with workarounds):

BIOS: http://sym.ax2401.com:9999/ipxe.pxe
UEFI: http://sym.ax2401.com:9999/ipxe.efi


Whether it works or not, please feedback , So I can decide if I need to make a pull request from github to IPXE.

I strongly discourage running binaries built by someone else. Also please remember that iPXE is GPL, so if you provide a (modified) binary you are also reguired to provide source on request
I know your intentions is good, I would still recommend that you make the source available, might be good to send patches to the mailinglist, see http://ipxe.org/admin for preferred ways.