Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
sanboot:winnt_iscsi_debug [2008/01/24 08:50] mcb30 |
sanboot:winnt_iscsi_debug [2009/10/29 15:51] (current) mcb30 |
||
|---|---|---|---|
| Line 101: | Line 101: | ||
| Delay for Disk Complete, continue with boot | Delay for Disk Complete, continue with boot | ||
| NIC device \??\PCI#VEN_10EC&DEV_8139&SUBSYS_00000000&REV_20#3&13c0b0c5&0&18#{cac88484-7515-4c03-82e6-71a87abac361} has PCI bus type | NIC device \??\PCI#VEN_10EC&DEV_8139&SUBSYS_00000000&REV_20#3&13c0b0c5&0&18#{cac88484-7515-4c03-82e6-71a87abac361} has PCI bus type | ||
| + | ISCSI Boot Status 0, (0, 0, 0, 0) | ||
| + | |||
| + | If you are using [[:sanbootconf|sanbootconf]] then a successful boot will look something like | ||
| + | |||
| + | iSCSI Boot Parameter Driver initialising | ||
| + | Found iBFT at 9cfb0 OEM ID "FENSYS" OEM table ID "gPXE" | ||
| + | Found iBFT Initiator 0: | ||
| + | Flags = 0x3, valid, boot selected | ||
| + | iSNS = 0.0.0.0 | ||
| + | SLP = 0.0.0.0 | ||
| + | Radius = 0.0.0.0, 0.0.0.0 | ||
| + | Name = iqn.2000-01.org.etherboot:host_10_0_0_90.home | ||
| + | Found iBFT NIC 0: | ||
| + | Flags = 0x3, valid, boot selected | ||
| + | IP = 10.0.0.90/24 | ||
| + | Origin = 0 | ||
| + | Gateway = 10.0.0.6 | ||
| + | DNS = 10.0.0.6, 0.0.0.0 | ||
| + | DHCP = 0.0.0.0 | ||
| + | VLAN = 0000 | ||
| + | MAC = 52:54:00:33:22:11 | ||
| + | PCI = 00:03.0 | ||
| + | Hostname = host_10_0_0_90.home | ||
| + | Found NIC with MAC address 52:54:00:33:22:11 at "\??\PCI#VEN_10EC&DEV_8139&SUBSYS_00000000&REV_20#3&13c0b0c5&0&18#{ad498944-762f-11d0-8dcb-00c04fc3358c}\{7C0E3A80-E8E7-4B81-933E-C997BF973430}" | ||
| + | iBFT NIC 0 is interface "\??\PCI#VEN_10EC&DEV_8139&SUBSYS_00000000&REV_20#3&13c0b0c5&0&18#{ad498944-762f-11d0-8dcb-00c04fc3358c}\{7C0E3A80-E8E7-4B81-933E-C997BF973430}" | ||
| + | iBFT NIC 0 is PDO 8124DCF8 | ||
| + | iBFT NIC 0 is NetCfgInstanceId "{7C0E3A80-E8E7-4B81-933E-C997BF973430}" | ||
| + | Found iBFT target 0: | ||
| + | Flags = 0x3, valid, boot selected | ||
| + | IP = 10.0.0.6 | ||
| + | Port = 3260 | ||
| + | LUN = 0000-0000-0000-0000 | ||
| + | CHAP type = 0 (None) | ||
| + | NIC = 0 | ||
| + | Name = iqn.2006-05.home.dolphin:winxp | ||
| + | CHAP name = | ||
| + | CHAP secret = | ||
| + | Reverse CHAP name = | ||
| + | Reverse CHAP secret = | ||
| + | iSCSI Boot Parameter Driver initialisation complete | ||
| + | iSCSI boot parameters requested | ||
| + | iSCSI boot parameters requested | ||
| + | Found iSCSI Boot Parameters at 81208008, attempting iSCSI boot | ||
| + | Allocating the Boot Connection Pool of size 30 | ||
| + | Allocating Connection Pool 81205850 | ||
| + | Allocating the Boot Connection Pool entry 0 SUCCESS | ||
| + | Allocating the Boot Connection Pool entry 1 SUCCESS | ||
| + | ... | ||
| + | Waiting 60 seconds for boot disk | ||
| + | iSpSystemWorkerThread: Entering | ||
| + | iSpSystemWorkerThread: Coming out of wait | ||
| + | iSpSystemWorkerThread: Start Logon Completion Thread 81205008 | ||
| + | Delay 10 seconds for Disk to arrive....... | ||
| + | iSpSystemWorkerThread: After Logon Completion Thread | ||
| + | Will notify BusChangeDetected | ||
| + | Delay for Disk Complete, continue with boot | ||
| ISCSI Boot Status 0, (0, 0, 0, 0) | ISCSI Boot Status 0, (0, 0, 0, 0) | ||
| For an unsuccessful boot, the messages will end with a "Bugcheck Analysis"; this is the debugging equivalent of the Blue Screen of Death that occurs when the debugger is not attached. | For an unsuccessful boot, the messages will end with a "Bugcheck Analysis"; this is the debugging equivalent of the Blue Screen of Death that occurs when the debugger is not attached. | ||
| + | |||
| + | ===== Using the output from the debugger ===== | ||
| Save the debugging transcript to a file using //Edit// -> //Write Window Text to File//. | Save the debugging transcript to a file using //Edit// -> //Write Window Text to File//. | ||
| - | ===== Diagnosing the problem ===== | + | You can e-mail the saved debugging transcript to <etherboot-discuss@lists.sourceforge.net>, along with any other information that you think may be relevant. Please note that the debugging transcript is the most important information; if you provide a full description of your setup and your problem, but do not provide the debugging transcript, then we will probably not be able to solve your problem. |
| - | {{ :screenshots:win2k3_iscsi_install.png?400x300|Installing the Microsoft iSCSI initiator}} | + | You can also often find us in the #etherboot IRC channel on FreeNode. |
| - | === No "IscsiBP" messages appear === | + | ====== Common problems ====== |
| - | If you do not see any IscsiBP messages appear, then you do not have the boot-capable iSCSI initiator installed on the iSCSI-booting machine. | + | {{ :screenshots:win2k3_iscsi_install.png?400x300|Installing the Microsoft iSCSI initiator}} |
| - | * Did you download the boot-capable Microsoft iSCSI initiator from [[http://connect.microsoft.com]]? If you installed the standard (non-boot-capable) Microsoft iSCSI initiator, then you will not be able to boot via iSCSI. | + | * Did you download and install the special boot-capable Microsoft iSCSI initiator as documented in [[:sanboot:winnt_iscsi|Adding iSCSI boot support to Microsoft Windows]]? If you installed the standard (non-boot-capable) Microsoft iSCSI initiator, then you will not be able to boot via iSCSI. |
| * Did you install the checked build (the file ending in //-x86chk.exe//)? If you installed the free build (the file ending in //-x86fre.exe//, then you may not see any diagnostic messages. | * Did you install the checked build (the file ending in //-x86chk.exe//)? If you installed the free build (the file ending in //-x86fre.exe//, then you may not see any diagnostic messages. | ||
| - | * When you installed the boot-capable Microsoft iSCSI initiator, did you tick the option to "Configure iSCSI Network Boot Support"? | + | * When you installed the boot-capable Microsoft iSCSI initiator, did you tick the option to "Configure iSCSI Network Boot Support" and select the correct network card to be used for iSCSI boot? ((This option is not available on Windows XP; you will need to also download and install [[:sanboot:winnt_sanbootconf|sanbootconf]] in order to boot via iSCSI.)) |
| - | === "IscsiBP Found device" message does not appear === | + | * If you are using Windows XP, did you download and install [[:sanboot:winnt_sanbootconf|sanbootconf]] in addition to the boot-capable Microsoft iSCSI initiator? |
| - | If you do not see a message starting with "IscsiBP Found device", then your network card is not being detected at boot time. | + | * If you are using iSCSI CHAP authentication, are all passwords at least 12 characters long? (The Microsoft iSCSI initiator will refuse to attempt authentication with shorter passwords.) |
| - | * When you installed the boot-capable Microsoft iSCSI initiator, did you select the correct network card to be used for iSCSI boot? | + | * Norton Internet Security's (at least 2009 and 2010) firewall is known to cause boot-time problems on XP. Disable the firewall before transferring your disk image to the iSCSI server. |
| - | === Other problems === | + | ===== VMware-specific problems ===== |
| - | You can e-mail the saved debugging transcript to <etherboot-discuss@lists.sourceforge.net>, along with any other information that you think may be relevant. Please note that the debugging transcript is the most important information; if you provide a full description of your setup and your problem, but do not provide the debugging transcript, then we will probably not be able to solve your problem. | + | VMware has a nasty habit of changing the PCI bus:dev.fn number assigned to the virtual NIC, which breaks the Windows driver bindings and so prevents a successful iSCSI boot. In most cases, you should ensure that the ''.vmx'' file for the VM that you are attempting to boot via iSCSI contains |
| + | |||
| + | scsi0.present = "TRUE" | ||
| + | |||
| + | even though there is no local hard disk attached.((VMware seems to assign PCI bus:dev.fn numbers dynamically. If you have a hard disk and a NIC in your virtual machine then VMware will typically assign the hard disk controller as PCI device 00:10.0 and the NIC as PCI device 00:11.0. You perform the Windows installation within the virtual machine then detach the hard disk, transfer the contents of the virtual hard disk to your iSCSI target, and try to boot from it. VMware will now reassign the NIC as PCI device 00:10.0, which will prevent Windows from enumerating the NIC correctly. By setting | ||
| + | |||
| + | scsi0.present="TRUE" | ||
| + | |||
| + | you can force VMware to create a hard disk controller (with no disks attached) as PCI device 00:10.0 and so reassign the NIC as PCI device 00:11.0, which is where Windows expects to find it.)) | ||
| + | |||
| + | ====== Other useful techniques ====== | ||
| + | |||
| + | ===== Displaying the boot driver list ===== | ||
| + | |||
| + | The Windows Sysinternals [[http://live.sysinternals.com/LoadOrd.exe|LoadOrd.exe]] utility can be used to produce a list of boot drivers on your system, which should look something like: | ||
| + | |||
| + | Start Group Tag Service Display Name | ||
| + | ~~~~+~~~~~~~~~~~~~~~~~~~~~~~+~~~~+~~~~~~~~~+~~~~~~~~~~~~ | ||
| + | Boot Boot Bus Extender 1 ACPI Microsoft ACPI Driver | ||
| + | Boot Boot Bus Extender 2 PCI PCI Bus Driver | ||
| + | Boot Boot Bus Extender 3 isapnp PnP ISA/EISA Bus Driver | ||
| + | Boot Boot Bus Extender 5 ACPIEC Microsoft Embedded Controller Driver | ||
| + | Boot System Bus Extender 6 Compbatt Microsoft Composite Battery Driver | ||
| + | Boot System Bus Extender 4 IntelIde | ||
| + | Boot System Bus Extender 1 Pcmcia | ||
| + | Boot System Bus Extender 8 MountMgr Mount Point Manager | ||
| + | Boot System Bus Extender 9 Ftdisk Volume Manager Driver | ||
| + | Boot System Bus Extender 12 dmload | ||
| + | Boot System Bus Extender 13 dmio Logical Disk Manager Driver | ||
| + | Boot System Bus Extender 5* PartMgr Partition Manager | ||
| + | Boot System Bus Extender n/a* VolSnap | ||
| + | Boot NDIS Wrapper n/a* NDIS NDIS System Driver | ||
| + | Boot NDIS 13 E1000 Intel(R) PRO/1000 Adapter Driver | ||
| + | Boot Base 1 KSecDD | ||
| + | Boot Base 20 iscsiboot | ||
| + | Boot PNP_TDI 5 IPSec IPSEC driver | ||
| + | Boot PNP_TDI 3 Gpc Generic Packet Classifier | ||
| + | Boot PNP_TDI 4 Tcpip TCP/IP Protocol Driver | ||
| + | Boot PNP_TDI 7 PSched QoS Packet Scheduler | ||
| + | Boot SCSI miniport 25 atapi Standard IDE/ESDI Hard Disk Controller | ||
| + | Boot SCSI Class 2 Disk Disk Driver | ||
| + | Boot FSFilter Infrastructure 1 FltMgr FltMgr | ||
| + | Boot Filter n/a* PxHelp20 PxHelp20 | ||
| + | Boot n/a* n/a* BTKRNL Bluetooth Protocol Stack | ||
| + | Boot n/a* n/a* iScsiPrt iScsiPort Driver | ||
| + | Boot Network* 2* Mup Mup | ||
| + | Boot n/a* n/a* ohci1394 Texas Instruments OHCI Compliant IEEE 1394 Host Controller | ||
| + | |||
| + | You need to run //LoadOrd.exe// on the system that you will attempt to boot via iSCSI, **before** transferring the disk image to the iSCSI target. | ||
| - | You can also often find us in the #etherboot IRC channel on FreeNode. | ||
