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
Next revision Both sides next revision
sanboot:win2k8_iscsi_install [2010/04/20 12:03]
jrc3
sanboot:win2k8_iscsi_install [2010/06/15 18:53]
xfgolden
Line 11: Line 11:
   - Boot using gPXE.   - Boot using gPXE.
   - Boot from DVD-ROM.   - Boot from DVD-ROM.
 +
 +<​sub>//​If you can't boot from gPXE from your BIOS read: [[/​howtos#​how_to_deploy_gpxe|How to Deploy gPXE]]. Specifically [[/​pxechaining|Boot gPXE for your PXE enabled network card]] and [[/​removable#​creating_a_bootable_floppy_disk|Loading gPXE from a bootable floppy]] or the ultimate [[/​romburning|Replace your legacy network card PXE ROM]]//</​sub>​
  
 ===== Configure DHCP gPXE options for iSCSI boot ===== ===== Configure DHCP gPXE options for iSCSI boot =====
Line 73: Line 75:
 </​code>​ </​code>​
  
-Note+**NOTE:** 
-when using tftpd32, bootmgr.exe should reside inside the root tftp directory and inside the boot directory.+When using tftpd32, bootmgr.exe should reside inside the root tftp directory and inside the boot directory
 + 
 +**NOTE:** 
 +If the Windows Setup cannot recognize your iSCSI drive be sure that WinPE is recognized your network card. Type "route print" to the WinPE command prompt and look for your network interface. If it is not there, you should load your network card's driver by using the "​loaddrv"​ command of the WinPE. Go to a local or a network folder which has your driver and execute "​loaddrv file.inf"​ to load the driver.
  
 ===== Alternative Method (simple) ===== ===== Alternative Method (simple) =====
Line 99: Line 104:
 set keep-san 1 set keep-san 1
 sanboot iscsi:​192.168.1.11::::​iqn.2007-08.name.dns.target.my:​iscsiboot sanboot iscsi:​192.168.1.11::::​iqn.2007-08.name.dns.target.my:​iscsiboot
-chain tftp://​192.168.1.11/​pxeboot.0+chain tftp://​192.168.1.11/​pxelinux.0
 </​code>​ </​code>​
  
Line 147: Line 152:
   Windows cannot be installed to this disk. This computer'​s hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer'​s BIOS menu   Windows cannot be installed to this disk. This computer'​s hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer'​s BIOS menu
 Solution for this error is quite simple, just add a drive for installation time, if the drive is a Serial-ATA connected then set it to //​Compatibile Mode// not //AHCI// (for Windows 7 this doesn'​t matter, you can leave it as AHCI). If you start windows installer once again you will see an error message only at the physical drive, select iSCSI target and just click next. Solution for this error is quite simple, just add a drive for installation time, if the drive is a Serial-ATA connected then set it to //​Compatibile Mode// not //AHCI// (for Windows 7 this doesn'​t matter, you can leave it as AHCI). If you start windows installer once again you will see an error message only at the physical drive, select iSCSI target and just click next.
 +
 +XFGolden Begin Edit -> This is totally contradictory to the above. But it worked for me when the above did not.
 +
 +In some cases such as mine using an asus m3n-HT Deluxe motherboard with the latest pheonix/​award bios having Serial ATA mode set to IDE(compatibility mode) caused the Windows 7 Ultimate x86_64 installer to view the the iscsi connected drive as a non-bios boot drive. There are three options in this bios for how Serial ATA drives are handled IDE/​AHCI/​RAID . Once the access mode for Serial ATA drives was set to AHCI the Windows Installer saw the physically attached drive as non-bios bootable and the iSCSI attached drive as a valid install target. On subsequent boots the installer completed and I was presented with a freshly installed Windows 7 desktop served from my SAN.
 +
 +<- End Edit XFGolden

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