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 [2009/02/20 12:20] mcb30 |
sanboot:winnt_iscsi_debug [2009/10/29 15:51] (current) mcb30 |
||
|---|---|---|---|
| Line 177: | Line 177: | ||
| * 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" 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_iscsi_sanbootconf|sanbootconf]] in order to boot via iSCSI.)) | + | * 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.)) |
| - | * If you are using Windows XP, did you download and install [[:sanboot:winnt_iscsi_sanbootconf|sanbootconf]] in addition to the boot-capable Microsoft iSCSI initiator? | + | * 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 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.) | * 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.) | ||
| + | |||
| + | * 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. | ||
| ===== VMware-specific problems ===== | ===== VMware-specific problems ===== | ||
| Line 189: | Line 191: | ||
| scsi0.present = "TRUE" | 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 NIC both present, 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 VM, then detach the hard disk, transfer the contents of the virtual hard disk to your iSCSI target, and try to boot from it. Since you have detached the hard disk, VMware will now assign the NIC as PCI device 00:10.0, Windows will fail to enumerate the NIC, and the iSCSI boot will fail. By setting | + | 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" | 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 return the NIC to being PCI device 00:11.0, as Windows expects.)) | + | 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 ====== | ====== Other useful techniques ====== | ||
