Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HP server exit iPXE boot from disk red screen with illegal opcode error
2017-10-30, 04:59
Post: #1
HP server exit iPXE boot from disk red screen with illegal opcode error
Hi,

HP ProLiant rack server 'localboot' to disk hang with :

PHP Code:
:localboot
sanboot 
--no-describe --drive 0x80 

I have try to use 'exit' replace 'sanboot' :

PHP Code:
:localboot
exit 

sanboot --drive 0x80 (localboot) hangs 2013-04-05

Use iPXE `exit` rather than `sanboot 0x80` on most machines #409 2013-02-21

HP server 'exit' iPXE boot from disk failed into red screen with 'illegal opcode' error message :

[Image: tNluUui.png]
Find all posts by this user
Quote this message in a reply
2017-10-30, 06:20
Post: #2
RE: HP server exit iPXE boot from disk red screen with illegal opcode error
so you are using pcbios and not efi?

in most cases you probably want "exit 1" in efi.

You should report this to HP so that they can fix their firmware.
Provide full information to them to reproduce (for now you are at least missing about mode, and which ipxe binary you are using)

sanboot --local is just a hack that works most of the time but with no guarantee. exit is flakey in pcbios mode but should work if bios is implemented correctly. exit 1 should always work for efi - but remember that exit equals "boot next device" and not "boot first local drive"
Find all posts by this user
Quote this message in a reply
2017-10-30, 06:44
Post: #3
RE: HP server exit iPXE boot from disk red screen with illegal opcode error
@NiKiZe Thanks.

HP ProLiant DL360 Gen9 server used BIOS boot, NOT UEFI mode :

[Image: tNmvsCn.png]

Let me try to boot with 'sanboot --local'.
Find all posts by this user
Quote this message in a reply
2017-11-02, 07:38 (This post was last modified: 2017-11-02 07:40 by lvii.)
Post: #4
RE: HP server exit iPXE boot from disk red screen with illegal opcode error
(2017-10-30 06:20)NiKiZe Wrote:  so you are using pcbios and not efi?

in most cases you probably want "exit 1" in efi.

You should report this to HP so that they can fix their firmware.
Provide full information to them to reproduce (for now you are at least missing about mode, and which ipxe binary you are using)

sanboot --local is just a hack that works most of the time but with no guarantee. exit is flakey in pcbios mode but should work if bios is implemented correctly. exit 1 should always work for efi - but remember that exit equals "boot next device" and not "boot first local drive"

@NiKiZe

I have try to boot from disk use 'sanboot --local' command, but it did NOT work :

[Image: lh3QCrr.png]

I have built the 'undionly.kkpxe' file base on the last ipxe git commit :

Code:
# git log -1
commit 1b67a0564657b6fcef18b1588ea6491ca1b1996d
Author: Michael Brown <mcb30@ipxe.org>
Date:   Sun Sep 24 19:26:58 2017 +0100

    [efi] Allow for building with older versions of elf.h system header
    
    Signed-off-by: Michael Brown <mcb30@ipxe.org>
Find all posts by this user
Quote this message in a reply
2017-11-02, 18:26
Post: #5
RE: HP server exit iPXE boot from disk red screen with illegal opcode error
I never said that you should use "sanboot --local" that was just referring to the command you where already using, please read again.

(2017-10-30 06:20)NiKiZe Wrote:  You should report this to HP so that they can fix their firmware.
Provide full information to them to reproduce (for now you are at least missing about mode, and which ipxe binary you are using)

sanboot --local 0x80 is just a hack that works most of the time but with no guarantee. exit is flakey in pcbios mode but should work if bios is implemented correctly.

And never use undionly.kkpxe that is also a hack for extremely buggy bios implementations, but it should only be used for those buggy implmentations.
always use undionly.kpxe (one k)
Find all posts by this user
Quote this message in a reply
2017-11-21, 16:22
Post: #6
RE: HP server exit iPXE boot from disk red screen with illegal opcode error
My workaround for those cases like ProLiant servers in legacy BIOS mode is to chain grub4dos (verified on DL160 G5/G6 and DL360/DL380 G5/G6/G7/Gen8/Gen9 servers).

Code:
:boot_local_disk
chain http://boot.example.net/grub.exe --config-file="rootnoverify (hd0);chainloader +1" || reboot

Please note that grub4dos seems to be a more or less dead project but the lastest available release on Source Forge (http://grub4dos.sourceforge.net/) works for me.
You can safely ignore any references to gna.org on the web site. GNA was shut down earlier this year, but the project's older web site on Source Forge is still alive. To my knowledge there was never a newer release than 0.4.4 which you can still find on Source Forge as well (http://prdownloads.sourceforge.net/grub4...-0.4.4.zip).
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)