Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
sanboot:winnt_iscsi_debug [2009/02/19 11:13]
mcb30
sanboot:winnt_iscsi_debug [2009/10/29 15:51] (current)
mcb30
Line 103: Line 103:
     ISCSI Boot Status 0, (0, 0, 0, 0)     ISCSI Boot Status 0, (0, 0, 0, 0)
  
-If you are using [[:sanboot:​sanbootconf|sanbootconf]] then a successful boot will look something like+If you are using [[:​sanbootconf|sanbootconf]] then a successful boot will look something like
  
     iSCSI Boot Parameter Driver initialising     iSCSI Boot Parameter Driver initialising
Line 160: Line 160:
  
 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 authenticationare 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 ​full description of your setup and your problembut do not provide ​the debugging transcriptthen 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 NICwhich 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 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 targetand try to boot from it.  VMware will now reassign ​the NIC as PCI device 00:10.0which 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. 

QR Code
QR Code sanboot:winnt_iscsi_debug (generated for current page)