Table of Contents

Fix iSCSI problems

Wireshark is the best tool for finding network problems. Install it on the iSCSI target server, or on any device that can see all the traffic. You may need to set a switch port to mirror traffic so Wireshark can see it.

There are many ways to set up iSCSI. Wireshark shows you how far a PC gets before it stops, which tells you where to look.

Blue screen: INACCESSIBLE_BOOT_DEVICE

This is the most common problem. It means Windows cannot see the iSCSI disk. Nearly always, the network driver did not start with Windows.

If Windows shows its logo first

If iPXE connects to the disk, the Windows logo and spinner show for a few seconds, and then the blue screen appears (0x7B), the hand over worked. Windows just could not start its network driver in time to keep hold of the disk.

Check these, in this order:

  1. The network driver is the right version. Some driver packs install fine but do not load early enough. For the Intel I219-LM or I219-V, use the PRO1000\NDIS68\e1d driver (service name e1dexpress). For the Intel I210, use PRO1000\NDIS68\e1r68x64. The Intel I225 and I226 use the e2f drivers.
  2. The network driver's Start value is 0. Look in HKLM\SYSTEM\CurrentControlSet\Services\<service name>.
  3. There is no StartOverride key under the network driver's service. If there is, delete the whole key. It quietly undoes Start=0.
  4. The service group is right. The network driver's service should have a Group value of NDIS, so it loads at the right time.
  5. No filter driver is bound to the iSCSI network card. A second network card that was not set up for iSCSI can have a filter bound to it that breaks iSCSI. Run Get-NetAdapterBinding -Name "<card name>" to see them, and turn off ms_wfplwf_lower and similar filters on the iSCSI card.

Change the registry on the disk file

To fix these settings without booting the disk, mount the disk file on another PC so it has a drive letter. Then load its registry:

reg load HKLM\TempHive "D:\Windows\System32\config\SYSTEM"

The services are now under:

HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\

These services must have Start set to 0 (a REG_DWORD):

  • Tcpip, the network stack. It is usually 0 already.
  • iScsiPrt, the iSCSI driver.
  • MSiSCSI, the iSCSI service.
  • NDIS, the network driver interface.
  • Your network card's own driver.

When you are done, unload the registry:

reg unload HKLM\TempHive

The boot start script sets Start=0 for a long list of drivers at once.

Blue screen: DRIVER_IRQL_NOT_LESS_OR_EQUAL

This is caused by the page file on the iSCSI disk. Sometimes a couple of restarts fix it. If it keeps happening, turn the page file off and delete it.

Without a page file, Windows cannot move memory to disk, so make sure the PCs have plenty of memory.

Turn the page file off:

$computerSystem = Get-CimInstance Win32_ComputerSystem
if ($computerSystem.AutomaticManagedPagefile) {
    Set-CimInstance -InputObject $computerSystem -Property @{ AutomaticManagedPagefile = $false }
}

Delete the page files:

Get-CimInstance Win32_PageFileSetting | Remove-CimInstance

Also make sure hibernation is off:

powercfg.exe /hibernate off

Error 0xc000000e or a Windows Recovery loop

The Windows boot manager starts, then shows an error about \Boot\BCD and offers to start recovery.

This nearly always means the boot settings point at partition=C:, or at a disk such as \Device\HarddiskVolume1 that does not exist over iSCSI.

Mount the disk file on another PC, then set the boot settings again. Change <Drive> to the drive letter of the disk's EFI partition:

bcdedit /store <Drive>:\EFI\Microsoft\Boot\BCD /set "{bootmgr}" device boot
bcdedit /store <Drive>:\EFI\Microsoft\Boot\BCD /set "{default}" device boot
bcdedit /store <Drive>:\EFI\Microsoft\Boot\BCD /set "{default}" osdevice boot
bcdedit /store <Drive>:\EFI\Microsoft\Boot\BCD /set "{default}" recoveryenabled no
bcdedit /store <Drive>:\EFI\Microsoft\Boot\BCD /set "{default}" bootstatuspolicy IgnoreAllFailures

If resumeobject is set on the default entry, delete it too. Hibernation is off, so an old resume entry will make the boot manager hang:

bcdedit /store <Drive>:\EFI\Microsoft\Boot\BCD /deletevalue "{default}" resumeobject