<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><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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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">Hello Bin,<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">This issue happens with many BIOSes out there. Basically (and I don’t completely understand it myself) it considers gPXE’s handing back of the boot process to be a failure and just wants you to reboot… which can be aggravating :-P<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">Anyway, you basically need to attempt a (failed) sanboot as you have here, but after that you need to load the next step in the process (Windows PE) in the context of what gPXE can launch. Several methods are covered here: </span><a href="http://etherboot.org/wiki/sanboot/win2k8_iscsi_install#alternative_method_using_winpe">http://etherboot.org/wiki/sanboot/win2k8_iscsi_install#alternative_method_using_winpe</a><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">If you can load WinPE from the network, that would be the simplest method (but not the easiest, in my experience), but the PXELINUX method mentioned below that would probably give you the least headache as far as installation goes.<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">Either way, best of luck to you.<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">Regards,<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><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><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>Bin<br><b>Sent:</b> Wednesday, October 06, 2010 10:15 AM<br><b>To:</b> gpxe@etherboot.org<br><b>Subject:</b> [gPXE] install win 7 to SAN - boot fail<o:p></o:p></span></p></div></div><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">I think someone had the same issue in July but I can't find any solutions so far. I have two mahines with the same issue. One is nvidia Nforce 730i Motherboard (and Nvidia NIC/BootAgent), the other is realtek NIC. I am using UNDI only 1.0.1. The chain loading works fine and gpxe got all the infomation. Howerver, the computer refused to boot from next source(CDROM). Instead I only got the option of "PRESS A KEY TO REBOOT". Here is one sample output.<br> <br>DHCP (net XX:XX:XX:XX:XX) ... ok<br>Registered as BIOS drive 0x00<br>Booting from BIOS drive 0x00<br>Boot falied<br>Preserving connection to SAN DISK<br>Could not boot from iscsi:192.168.x.x::::pc01 Operation cancelled 0xb08080a0<br><br>PRESS A KEY TO REBOOT<br><br>Thanks,<o:p></o:p></span></p></div></body></html>