ipxe windows boot issue on 2nd interface

[rajeshsg]

Hi,
In ipxe, with windows, I am able to boot windows on net0, with iSCSI. If I try to boot from net1 using iSCSI, the booting happens fine, but the boot procedure stucks with "INACCESSIBLE_BOOT_DEVICE" message. I have disabled "NDIS LWF driver" on both the interfaces, though 2nd interface never gets me past that error message.

I have followed all the steps as per:
1. https://support.microsoft.com/en-in/help...ardware-is
2. http://mistyrebootfiles.altervista.org/d...wfplwf.htm

This is not related to ipxe, but related to windows settings in iSCSI boot. if anyone else has been able to get iSCSI boot over ipxe in windows with 2nd interface? if yes, any pointers much appreciated.

Thanks,
Rajesh

[NiKiZe]

Did you also install windows using "net1" ?

You will probably have to check iSCSI logs, or resort to tcpdump to see if the interface keeps communicating after iPXE closes at all.
My first guess is that windows don't bring up the interface at all.

You might also want to disable "net0" during installation, and once that is completed re-enable "net1" again and see if that get's you going.
Once you/we know what is working and not, there might be a possible workaround.

[rajeshsg]

(2019-11-06 21:53)NiKiZe Wrote:  Did you also install windows using "net1" ?

You will probably have to check iSCSI logs, or resort to tcpdump to see if the interface keeps communicating after iPXE closes at all.
My first guess is that windows don't bring up the interface at all.

You might also want to disable "net0" during installation, and once that is completed re-enable "net1" again and see if that get's you going.
Once you/we know what is working and not, there might be a possible workaround.

Thanks for the quick reply, NIKiZe.

I didn't install on iscsi disks. I did install on local disks, disabled the filter drivers on interfaces (so that iscsi boot is allowed) and then moved the data (sort of full copy) to iscsi disks and then trying to access those iscsi disks (having installed windows,) using ipxe sanboot iscsi commands.

The only issue being second interface lands me into the troubles I mentioned before (links provided in original question,) whereas booting using first interface is always fine. I have made sure, before copying data to iscsi disks, to disable the appropriate filters so that all the interfaces are allowed for iscsi booting.

[NiKiZe]

Again, have you tried installing with "net0" disabled?
You have also excluded information about what these nics are, pciids are always helpful, maybe it is a driver issue (which seems to be common when reading other threads about iSCSI booting windows)

[rajeshsg]

(2019-11-06 22:53)NiKiZe Wrote:  Again, have you tried installing with "net0" disabled?
You have also excluded information about what these nics are, pciids are always helpful, maybe it is a driver issue (which seems to be common when reading other threads about iSCSI booting windows)

Thanks, NiKiZe. I will post with some more testing today.

[rajeshsg]

(2019-11-07 07:24)rajeshsg Wrote:  

(2019-11-06 22:53)NiKiZe Wrote:  Again, have you tried installing with "net0" disabled?
You have also excluded information about what these nics are, pciids are always helpful, maybe it is a driver issue (which seems to be common when reading other threads about iSCSI booting windows)

Thanks, NiKiZe. I will post with some more testing today.

The following document specifies that NDI filters (mainly NDIS LWF driver for my purpose) can be disabled from registry:

https://support.microsoft.com/en-in/help...ernate-isc
https://social.technet.microsoft.com/For...erverfiles

which may solve my issue. But, seems that never version of Windows (Windows 2016 server) don't export that registry value, even adding new one doesn't have any effect on the behavior. That's why I was trying to modify c:\windows\inf\wfplwfs.inf file as per:

https://docs.microsoft.com/en-us/windows...ter-driver

to:
HKR, Ndi,FilterRunType,0x00010001 ,0x00000002

to change the behavior, but that cannot be modified on a running system, gives the obvious "Access is denied" error.

Any hints on how to modify "FilterRunType" on a running system without going into rescue mode, for Win2k16 server?

[rajeshsg]

(2019-11-10 07:09)rajeshsg Wrote:  

(2019-11-07 07:24)rajeshsg Wrote:  

(2019-11-06 22:53)NiKiZe Wrote:  Again, have you tried installing with "net0" disabled?
You have also excluded information about what these nics are, pciids are always helpful, maybe it is a driver issue (which seems to be common when reading other threads about iSCSI booting windows)

Thanks, NiKiZe. I will post with some more testing today.

The following document specifies that NDI filters (mainly NDIS LWF driver for my purpose) can be disabled from registry:

https://support.microsoft.com/en-in/help...ernate-isc
https://social.technet.microsoft.com/For...erverfiles

which may solve my issue. But, seems that never version of Windows (Windows 2016 server) don't export that registry value, even adding new one doesn't have any effect on the behavior. That's why I was trying to modify c:\windows\inf\wfplwfs.inf file as per:

https://docs.microsoft.com/en-us/windows...ter-driver

to:
HKR, Ndi,FilterRunType,0x00010001 ,0x00000002

to change the behavior, but that cannot be modified on a running system, gives the obvious "Access is denied" error.

Any hints on how to modify "FilterRunType" on a running system without going into rescue mode, for Win2k16 server?

The issue turned out to be changed PCI ID. After matching PCI IDs (PCI slot numbers) of the NICs to the original existing NIC PCI IDs (PCI slot numbers), things worked fine.