Known Issues for Intel® iSCSI Remote Boot





Click or the topic for details:

Windows known issues

Adding/updating hardware or software to Microsoft Windows Server* 2003

After adding or updating hardware or software that might impact the Networking stack e.g. Network Drivers, OS service packs etc., you must run iscsibcg.exe with /verify /fix command line options. This utility is installed as part of Microsoft* iSCSI Software installation. It is strongly recommended that this utility is setup to run at each system shutdown so you will not forget and break the system. To setup this utility to run at system shutdown follow these steps.

  1. Run gpedit.msc. This will start the group policy editor; in this utility:
  2. Expand Computer Configuration
  3. Expand Windows Settings
  4. Expand or select Scripts (startup/shutdown)
  5. Double click Shutdown
  6. This will open a Shutdown Properties dialog; click the Add button and add this executable or a batch file to run this.
Microsoft* Initiator does not boot without link on boot port

After setting up the system for iSCSI Remote Boot with two ports connected to a target and successfully booting the system, if you later try to boot the system with only the secondary boot port connected to the target, Microsoft Initiator will continuously reboot the system.

To work around this limitation follow these steps:

  1. Using Registry Editor, expand the following registry key:
  2. Create a DWORD value called DisableDHCPMediaSense and set the value to 0.
Moving iSCSI adapter to a different slot

In a Windows* installation, if you move the iSCSI adapter to a PCI slot other than the one that it was in when the drivers and MS ISCSI Boot Initiator were installed, then a System Error (Blue Screen) may occur during the middle of the Windows Splash Screen. This issue goes away if you return the adapter to its original PCI slot. We recommend not moving the adapter used for iSCSI installation. This is a known OS issue.

If you must move the adapter to another slot, then you must install a new adapter to another slot and setup that adapter for Intel iSCSI Remote Boot and then move the previous adapter.

Follow these steps:

  1. Install a new adapter into another slot
  2. Setup the new adapter for iSCSI Boot
  3. Perform iSCSI boot to the OS via the original adapter
  4. Make the new adapter iSCSI-bootable to the OS
  5. Reboot
  6. Move the old adapter into another slot
  7. Repeat steps 2 - 5 for the old adapter you just moved
Uninstalling driver can cause blue screen

If the driver for the device in use for Intel iSCSI Remote Boot is uninstalled via Device Manager, Windows will blue screen on reboot and the OS will have to be re-installed. This is a known Windows issue.

Adapters flashed with iSCSI image are not removed from the Device Manager during uninstall

During uninstallation all other Intel Network Connection Software is removed, but drivers for iSCSI Remote Boot adapters that have boot priority assigned as Primary or Secondary are not uninstalled.

Intel® I/OAT offload may stop with Intel® iSCSI Remote Boot or with Microsoft Initiator installed

A workaround for this issue is to change the following registry value to 0:


Only change the registry value if Intel iSCSI Remote Boot is enabled and if you want I/OAT offloading. A blue screen will occur if this setting is changed to when Intel iSCSI Remote Boot is not enabled. It must be set back to 3 if Intel iSCSI Remote Boot is disabled or a blue screen will occur on reboot.

NDIS driver may not load during Intel iSCSI Remote Boot F6 install With Intel® PRO/1000 PT Server Adapter

If you are using two Intel PRO/1000 PT Server Adapters in two PCI Express x8 slots, Windows installation can be done only via a local HDD procedure.

Invalid CHAP settings may cause Windows Server 2008* to blue screen

If an iSCSI Remote Boot port CHAP user name and secret do not match the target CHAP user name and secret, Windows Server 2008 may blue screen or reboot during installation or boot. Ensure that all CHAP settings match those set on the target(s).

F6 driver does not support standby mode

If you are performing an F6 Windows without a Local Disk installation, do not use Standby Mode.

Windows Server 2008 installation when performing a WDS Installation

If you perform a WDS installation and attempt to manually update drivers during the installation, the drivers load but the iSCSI Target LUN does not display in the installation location list. This is a known WDS limitation with no current fix. You must therefore either perform the installation from a DVD or USB media or inject the drivers on the WDS WinPE image.

iSCSI Boot and teaming in Windows*

Teaming is not supported with iSCSI Boot. Creating a team using the primary and secondary iSCSI adapters and selecting that team during the Microsoft initiator installation may fail with constant reboots. Do not select a team for Intel iSCSI Remote Boot, even if it is available for selection during initiator installation.

For load balancing and failover support, you can use MSFT MPIO instead. Check the Microsoft Initiator User Guide on how to setup MPIO.

Performing F6 diskless installation with removable/temporary storage device when running Windows Server 2003

Performing an F6 diskless installation while a removable or temporary storage device (such as a USB flash drive or FireWire* drive) is loaded may cause a change in the BIOS boot order. If this occurs, you must re-start the F6 diskless installation. For this reason we recommend not loading a removable or temporary storage device while performing an F6 diskless installation.

This is a known issue for Windows Server 2003 and cannot be rectified by Intel iSCSI Remote Boot. Additional information about this Windows Server 2003 issue can be found in Microsoft support article kb816793.

Setting LAA (Locally Administered Address) on an iSCSI Boot-Enabled Port Will Cause System Failure on Next Reboot

Do not set LAA on ports with iSCSI Boot enabled.

F6 installation may fail with some EMC targets

An F6 installation may fail during the reboot in step 10 of Installing Windows 2003 without a Local Disk because of a conflict between the Intel F6 driver, the Microsoft iSCSI Initiator and the following EMC target model firmware versions:

  • AX4-5 arrays: or higher
  • CX300, CX500, CX700, and CX-3 Series arrays: or higher.
  • CX-4 Series arrays: or higher, including all revisions.

To avoid the failure, ensure that the secondary iSCSI port cannot reach the target during the reboot in step 10.

With high iSCSI traffic on Microsoft* Windows 2003 Server* R2, link flaps can occur with 82598-based silicon

This issue is caused by the limited support for Large Send Offload (LSO) in this Operating System. Please note that if ISCSI traffic is required for Windows 2003 Server R2, LSO will be disabled.

Intel® Ethernet iSCSI Boot version does not match between displayed versions on Intel® PROSet and the scrolling text during boot

If a device is not set to primary but is enumerated first, the BIOS will still use that device's version of iSCSI Boot. Therefore the user may end up using an earlier version of Intel® Ethernet iSCSI Boot than expected. The solution is that all devices in the system must have the same version of iSCSI Boot. To do this the user should go to the Boot Options Tab and update the devices' flash to the latest version.

iSCSI and DCB known issues

iSCSI over DCB using Microsoft* Windows Server* 2012

iSCSI over DCB (priority tagging) is not possible on the port on which VMSwitch is created. This is by design in Microsoft* Windows Server* 2012.

Automatic creation of iSCSI traffic filters for DCB is only supported on networks which make use of IPv4 addressing

The iSCSI for Data Center Bridging (DCB) feature uses Quality of Service (QOS) traffic filters to tag outgoing packets with a priority. The Intel iSCSI Agent dynamically creates these traffic filters as needed on networks using IPv4 addressing.

Automatic creation of iSCSI traffic filters for DCB, using Virtual Adapters created by Hyper-V, is only supported on Microsoft* Windows Server* 2008 releases R2 and later.

The iSCSI for Data Center Bridging (DCB) feature uses Quality of Service (QOS) traffic filters to tag outgoing packets with a priority. The Intel iSCSI Agent dynamically creates these traffic filters as needed for Windows Server 2008 R2 and later.

Linux known issues

Channel bonding

Linux Channel Bonding has basic compatibility issues with Intel iSCSI Remote Boot and should not be used.

Authentications errors on EqualLogic target may show up in dmesg when running Red Hat* Enterprise Linux 4

These error messages do not indicate a block in login or booting and may be safely ignored.

iBFT System using RHEL 5.2

In an iBFT system using RHEL 5.2, Anaconda does not automatically start networking upon installation. The user has to manually bring up networking through a console. Please refer to the RedHat documentation for details on how to manually force up the network.

CHAP Support with RHEL 5.2

RHEL 5.2 does not support CHAP during installation time. If you use CHAP authentication on the target, please disable CHAP during installation and enable it after the installation is complete.

RHEL 5.1

On RHEL5.1 systems, the wrong network interface is brought up on the first iSCSI Boot after installation. This causes the system to hang and requires a reinstallation at the very least. The workaround for this issue is to edit the init script soon after installation and change the interface you wish to bring up. We strongly encourage our users to use RHEL5.2 to avoid this issue.

LRO and iSCSI Incompatibility

LRO (Large Receive Offload) is incompatible with iSCSI target or initiator traffic. A panic may occur when iSCSI traffic is received through the ixgbe driver with LRO enabled. To workaround this, the driver should be built and installed with:


From a remote LUN, iSCSI boot only works on the same port that was used to install to the remote LUN. You cannot boot from an alternate LAN port after iSCSI is installed.

Related topics
How Do I Troubleshoot Intel® iSCSI Remote Boot Issues?
LRO and iSCSI Incompatibility