<html xmlns="http://www.w3.org/TR/REC-html40" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml"><head><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body vlink="purple" link="blue" lang="EN-US"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Good morning Matt,<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The issue that you’re having is that in order to boot from PXE/CD/DVD/etc after connecting to a SAN, gPXE relies on the SAN boot failing. That’s what the “set keep-san 1” is all about: “keep-san” basically tells gPXE to leave a SAN disk attached to the BIOS and to write the iBFT (that magic bit of memory that lets an OS detect the SAN disk you’ve attached) in spite of the fact that the disk isn’t bootable. You can see here, from the output text that you’ve posted, that your iSCSI target <i>is</i> a bootable drive:<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal">DHCP (net0 00:01:02:03:04:05). ok<br>Registered as BIOS Drive 0x80<br>Booting from BIOS Drive 0x80<br><br>BOOTMGR is missing<br>Press Ctrl+Alt+Del to restart<o:p></o:p></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">A drive is bootable when it has an MBR and an active partition. <i>This</i> drive appears to have NT6+ (Vista/7) boot code in its MBR. That boot code checks the active partition for BOOTMGR (the Windows Boot Manager, the NT6 replacement for the Windows 2000/XP/2003 NTLDR) and chainloads it when found. Since there’s no OS installed on the drive, you’re getting that error message.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">To delete the MBR on your target, connect to it using the Microsoft iSCSI Initiator, open a command prompt and run diskpart (you’ll be prompted to elevate via UAC if it’s enabled).<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In diskpart type: LIST DISK<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In the output, determine which disk corresponds to your iSCSI target. For the purposes of the screenshot here, assume it is disk 5, and SELECT the DISK number like so: SELECT DISK 2<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You can see that the SELECTed disk has become highlighted by typing LIST DISK again.<o:p></o:p></span></p><p class="MsoNormal"><img src="cid:image001.png@01CB9D08.25D7A5E0" id="Picture_x0020_1" height="251" width="481"> <img src="cid:image002.png@01CB9D08.25D7A5E0" id="Picture_x0020_2" height="238" width="453"><o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">From here, type CLEAN and diskpart will erase all partition and MBR information from the disk:<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><img src="cid:image003.png@01CB9D08.25D7A5E0" id="Picture_x0020_3" height="117" width="371"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Disconnect from your iSCSI target, and try your netboot again, and you should be good to go!<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Cheers,<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Andrew Bobulsky<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> gpxe-bounces@etherboot.org [mailto:gpxe-bounces@etherboot.org] <b>On Behalf Of </b>Matthew Helton<br><b>Sent:</b> Wednesday, December 15, 2010 3:03 PM<br><b>To:</b> gpxe@etherboot.org<br><b>Subject:</b> [gPXE] Unable to get past iSCSI drive message for SAN Installation...<o:p></o:p></span></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">All,<br><br> This one has me stymied. I have a fairly complete TFTP/PXE/gPXE environment running with full DHCP/DNS services, however a native gPXE Windows 7 iSCSI installation has eluded me this far.<br><br>iSCSI Target: Windows Storage Server 2008 R2. <br><br>gPXE is working great.. I just can't get past it!<br><br>My gPXE Boot Script:<br><br>#!gpxe<br>dhcp net0<br>set keep-san 1<br>set initiator-iqn iqn.1991-05.com.microsoft:mywin7box.homelab.local<br>sanboot iscsi:myiscsitargetbox.homelab.local::::iqn.1991-05.com.microsoft:myiscsitargetbox-mywin7box-target<br>chain tftp://mytftpserverbox.homelab.local/boot/<a href="http://pxeboot.com">pxeboot.com</a><br><br>The box boots normally:<br><br>gPXE 1.0.1 blah ~we all love gPXE and this is where we can get it ~ blah<br>Features: iSCSI DNS TFTP Multiboot PXE PXEXT<br> <br>DHCP (net0 00:01:02:03:04:05). ok<br>Registered as BIOS Drive 0x80<br>Booting from BIOS Drive 0x80<br><br>BOOTMGR is missing<br>Press Ctrl+Alt+Del to restart<br>_<br><br>Note the _Cursor... it won't Chain (I think).<br> <br>The bootstrap program referenced in "chain tftp://mytftpserverbox.homelab.local/boot/<a href="http://pxeboot.com">pxeboot.com</a>" boots a fully-functional WinPE3.0 image<br><br>BOOTMGR.exe is present in both the root TFTP directory and the /BOOT directories.<br><br>The WinPE3.0 image will boot via PXE if I change the boot program to <a href="http://pxeboot.com">pxeboot.com</a><br><br>What am I missing here?<br><br><br>Thanks in advance,<br><br>Matt Helton<br><br> <o:p></o:p></p></div></body></html>