<div dir="ltr"><div>If you simply exit out of the script instead of trying a local sanboot, does it work? What model HP ProLiant?</div><div> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 7, 2013 at 4:22 AM, Christoph Schug <span dir="ltr"><<a href="mailto:chris+ipxe-devel@schug.net" target="_blank">chris+ipxe-devel@schug.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
I am currently trying to use iPXE for some staged booting environment where the boot process of each server can be controlled centrally on the boot server by supplying individual iPXE bootstrap configurations (e.g., install operating system, wipe disks,<br>
boot from local disk) without having to alter/reload DHCP configuration at all.<br>
<br>
I have some difficulties to get that working with some older HP ProLiant machines I have available in my lab. Basically everything works except booting from local disk. It doesn't matter if I drive this by an iPXE script or enter the sanboot command on the iPXE<br>
shell manually.<br>
<br>
| iPXE> sanboot --no-describe --drive 0x80<br>
| Booting from SAN device 0x80<br>
<br>
At this point nothing obvious happens and it takes pretty much exactly 300 seconds for the command to return with<br>
<br>
| GRUB Read Error<br>
| Booting from SAN device 0x80 failed: Operation canceled (<a href="http://ipxe.org/0b8080a0" target="_blank">http://ipxe.org/0b8080a0</a>)<br>
| iPXE><br>
<br>
BTW, on consecutive retries of the same command it returns instantly (no 5 minutes delay) with the same error. If I skip PXE booting entirely in the BIOS the machine boots just fine from local disk, so I am tempted to exclude a flawed installation of GRUB or the operating system. I rather assume that there is some memory corruption problem which causes that behavior as similar problems with older HP ProLiants were also reported on similar projects, e.g. <a href="http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#LOCALBOOT_on_HP_ProLiant_servers" target="_blank">http://www.syslinux.org/wiki/<u></u>index.php/Hardware_<u></u>Compatibility#LOCALBOOT_on_HP_<u></u>ProLiant_servers</a><br>
<br>
Unfortunately I don't have any different hardware at hand to verify that I am not running in some generic problem unrelated to the type of hardware. The specs of a machine in question where things break is a HP DL365 G5 (ProLiant System BIOS A10 as of 05/02/2011).<br>
<br>
Again, it is just booting from local disk that is broken, triggering a PXE install of Debian Linux for example works superb. I also tried to workaround by chaining chain.c32 for example but no luck as well.<br>
<br>
| #!ipxe<br>
|<br>
| chain <a href="http://boot.example.com/chain.c32" target="_blank">http://boot.example.com/chain.<u></u>c32</a> hd0<br>
<br>
In this case there is also this some minute delay and the machine dies horrible with "Illegal OpCode" and some garbaged (which even more suggests memory corruption) register dump (white font on red background, I rather assume this error does not originate from iPXE code).<br>
<br>
Has anyone experience with similar hardware and is aware of a feasible workaround? Or any other hints how to debug this issue?<br>
<br>
Thanks in advance<br>
Christoph<br>
<br>
______________________________<u></u>_________________<br>
ipxe-devel mailing list<br>
<a href="mailto:ipxe-devel@lists.ipxe.org" target="_blank">ipxe-devel@lists.ipxe.org</a><br>
<a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/<u></u>mailman/listinfo.cgi/ipxe-<u></u>devel</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>There is never time enough to do it right, but there always seems to be enough time to do it again.<br>
</div>