Thank you for contacting Intel Customer Support.
Can you provide more information on the error that you've encountered? Error messages, if any?
We look forward to you reply.
First I have contact Synology because I thought it was a
bug in the firmware of Sinology.
This is what they say to me:
compare the log with recorded packets, we discover the root cause is Initiator
doesn't response, then Target Server close iSCSI session.
situation happens three times, Initiator didn't connect to Target again in last
time, so it boot failed.
check attached screenshots, the line in blue highlight which means the last I/O
request from Initiator.
As you can
see it shows (Good) in the info field, it means this request have execute
is no any request in next 20 seconds, Target server will send "NOP
In" packet, to check(ping) Initiator whether alive.
Initiator doesn't have any response(so you will see a lot TCP Retransmission),
then Target server close session.
consult Hardware Provider to know why Initiator doesn't response, thanks.
dump Pcap file.
We did a bit of research on this. This is not an adapter issue...that's just a symptom. Appears to install on a VM but not physical without a workaround. Review this information below and see if this is something that can be helpful to you.
See information in this thread: http://www.computeraudiophile.com/f10-music-servers/diskless-windows-10-pc-setup-procedure-27363/
*This link will take you off of the Intel website. Intel does not control the content of the destination website.
Also one user had to include the following to get it to work.
6C. Launch iSCSI Initiator
- Type "iscsicpl" <enter> at the Command Prompt window and answer Yes to the prompt
- This will configure Win10 to auto launch the iSCSI initiator service at OS startup
i installed it on the physical disc as described in the article and activated iscsi initiator. then i cloned the disc from another computer like:
dd if=/dev/sdb of=/tmp/iscsi-image.dd bs=512 conv=noerror,sync count =12345678
assuming you are doing the default installation windows will create 2 partitions, so if you are doing fdisk -l /dev/sdb you get
Sector size... 512 bytes => bs=512
where 12345678 is the "End" of /dev/sdb2 plus 1, also from fdisk -l /dev/sdb, e.g.:
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 1026047 .............
/dev/sdb2 1026048 40962047 ..............
your count will be 40962047 + 1 = 40962048
Hope this is helpful.