Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
 Experiencing red screen of death on boot
#1
Hi!

I'm trying to PXE boot into iVentoy from an HPE DL360 G6 and I keep on getting the red screen of death. As far as I can tell, everything is working correctly (meaning the server is getting an IP through DHCP from iVentoy and is able to communicate with it) until iVentoy serves the boot file which shows the list of bootable ISOs.

I'm not really sure where to begin debugging this so if anyone has any suggestions that would be great! Thanks!

iVentoy Logs:
Code:
2023/07/16 01:22:39.721 [DHCP] Proc DHCP DISCOVER pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:39.721 [DHCP] The client already exist, 192.168.3.200 1cc1-de6f-fa68 dhcp_rfc_proc_discover 1432
2023/07/16 01:22:39.721 [DHCP] Use the Last IP for PXE Client(1c-c1-de-6f-fa-68) in normal mode.
2023/07/16 01:22:39.722 [DHCP] Recv DHCP Discover from 1cc1-de6f-fa68, response DHCP OFFER with ip 192.168.3.200/255.255.255.0
2023/07/16 01:22:39.722 [DHCP] DHCP boot file is <ipxe.bios.0>
2023/07/16 01:22:44.774 [DHCP] Proc DHCP REQUEST pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:44.775 [DHCP] Recv DHCP Offer Request from 1cc1-de6f-fa68, response DHCP ACK
2023/07/16 01:22:44.775 [TFTP] Parse tftp option(tsize,0)
2023/07/16 01:22:44.775 [TFTP] TFTP RRQ client 192.168.3.200:2070 download <ipxe.bios.0> start ...
2023/07/16 01:22:44.775 [TFTP] Start send file ipxe.bios.0 to 192.168.3.200:2070 with blksize 512, has oack 1
2023/07/16 01:22:44.776 [TFTP] Recv an ERROR opcode pkt from client 192.168.3.200:2070.
2023/07/16 01:22:44.776 [TFTP] Parse tftp option(blksize,1456)
2023/07/16 01:22:44.776 [TFTP] TFTP RRQ client 192.168.3.200:2071 download <ipxe.bios.0> start ...
2023/07/16 01:22:44.776 [TFTP] Start send file ipxe.bios.0 to 192.168.3.200:2071 with blksize 1456, has oack 1
2023/07/16 01:22:44.802 [TFTP] Finished send file to 192.168.3.200:2071 with blksize 1456 blks 92
2023/07/16 01:22:53.009 [DHCP] Proc DHCP DISCOVER pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:53.009 [DHCP] The client already exist, 192.168.3.200 1cc1-de6f-fa68 dhcp_rfc_proc_discover 1432
2023/07/16 01:22:53.009 [DHCP] Use the Last IP for PXE Client(1c-c1-de-6f-fa-68) in normal mode.
2023/07/16 01:22:53.009 [PXE]  Client 1c-c1-de-6f-fa-68 start PXE install in Legacy BIOS mode.
2023/07/16 01:22:53.009 [DHCP] Recv DHCP Discover from 1cc1-de6f-fa68, response DHCP OFFER with ip 192.168.3.200/255.255.255.0
2023/07/16 01:22:53.009 [DHCP] DHCP boot file is <http://192.168.3.15:16000/ipxe/01-1c-c1-de-6f-fa-68>
2023/07/16 01:22:54.002 [DHCP] Proc DHCP DISCOVER pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:54.002 [DHCP] The client already exist, 192.168.3.200 1cc1-de6f-fa68 dhcp_rfc_proc_discover 1432
2023/07/16 01:22:54.002 [DHCP] Use the Last IP for PXE Client(1c-c1-de-6f-fa-68) in normal mode.
2023/07/16 01:22:54.002 [PXE]  Client 1c-c1-de-6f-fa-68 start PXE install in Legacy BIOS mode.
2023/07/16 01:22:54.002 [DHCP] Recv DHCP Discover from 1cc1-de6f-fa68, response DHCP OFFER with ip 192.168.3.200/255.255.255.0
2023/07/16 01:22:54.002 [DHCP] DHCP boot file is <http://192.168.3.15:16000/ipxe/01-1c-c1-de-6f-fa-68>
2023/07/16 01:22:56.034 [DHCP] Proc DHCP REQUEST pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:56.034 [DHCP] Recv DHCP Offer Request from 1cc1-de6f-fa68, response DHCP ACK
2023/07/16 01:23:56.165 [HTTP] Client 192.168.3.200:34504 (51) timeout

RSOD:
   
Reply
#2
The bootloader used for legacy BIOS mode actually was built with x86_64 acrh.
So maybe the CPU in DL360 G6 doesn't support x86_64 (AMD64) ?
Reply
#3
Good thought! The CPU I have in there now is an Intel Xeon E5506 which according to the spec sheet is a 64-bit CPU (unless I'm missing something)
Reply
#4
There are two different 64bit arch (Intel IA64 and AMD64).
So I don't know which one is it.
Reply
#5
Besides, from the red screen, it print the register EAX/EBX/... which is 32bit arch (for AMD64 it should be RAX/RBX ...)
Reply
#6
Gotcha. I'm actually planning on moving two CPUs (Xeon X5660) from another system to this one so it's possible that may do the trick. Thanks for your help so far with this! I'll let you know how it goes
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)