Community
cancel
Showing results for 
Search instead for 
Did you mean: 
GMart14
Beginner
1,839 Views

I try to install windows 10 on a ISCSI disk but during the second phase of installation the ISCSI Disk become inaccessible during the boot.

I try to install windows 10 on a ISCSI disk but during the second phase of installation the ISCSI Disk become inaccessible during the boot.

I use the latest NDIS 4 driver version 21.0 Network card is X540-T2.

All other OS version its working fine.

Tags (1)
0 Kudos
10 Replies
idata
Community Manager
256 Views

Hi MartinoAutomatisering,

 

 

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.

 

 

Sincerely,

 

Sandy
GMart14
Beginner
256 Views

Hi Sandy,

First I have contact Synology because I thought it was a

 

bug in the firmware of Sinology.

This is what they say to me:

After

 

compare the log with recorded packets, we discover the root cause is Initiator

 

doesn't response, then Target Server close iSCSI session.

This

 

situation happens three times, Initiator didn't connect to Target again in last

 

time, so it boot failed.

Please

 

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

 

successfully.

Then there

 

is no any request in next 20 seconds, Target server will send "NOP

 

In" packet, to check(ping) Initiator whether alive.

However,

 

Initiator doesn't have any response(so you will see a lot TCP Retransmission),

 

then Target server close session.

Please

 

consult Hardware Provider to know why Initiator doesn't response, thanks.

See screen

 

dump Pcap file.

Regards,

Giuseppe

idata
Community Manager
256 Views

Hi Giuseppe,

 

 

Thank you for your information. I'll further check on this and will update you accordingly.

 

 

Sincerely,

 

Sandy
idata
Community Manager
256 Views

Hi Giuseppe,

 

 

For Windows* 10, use drivers in NDIS65 folder and please let us know if this works. Thanks.

 

 

Sincerely,

 

Sandy
idata
Community Manager
256 Views

Hi Giuseppe,

 

 

I would like to check if you were able to try the NDIS5 drivers. Hope it help resolve the network problem.

 

 

Sincerely,

 

Sandy
GMart14
Beginner
256 Views

Hello

 

Sandey,

NDIS65 gives me the same problem and where can I find NDIS5 driver?

Regards,

Giuseppe

idata
Community Manager
256 Views

Hi Giuseppe,

 

 

It should be NDIS65 for Windows* 10. Sorry for the confusion.

 

 

I would like you to try flashing the adapter's BootROM. Please provide the serial number of your card. You can find the serial number on the small white barcode sticker.

 

 

Sample Photo:

 

 

GMart14
Beginner
256 Views

Hello Sandey,

Latest BootRom is installed on this adapter from version 21.0 Release.

Regards,

Giuseppe

idata
Community Manager
256 Views

Hello Giuseppe,

 

 

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.

 

 

Source: http://it-joe.com/howtos/winiscsi.php

 

6C. Launch iSCSI Initiator

 

- Type "iscsicpl" 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

 

-- snap

 

 

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.

 

 

Sincerely,

 

Sandy
idata
Community Manager
256 Views

Hello Giuseppe,

 

 

Were you able to try the recommendations on my previous post?

 

 

Hope to hear from you again.

 

 

Sincerely,

 

Sandy
Reply