Chainloading failed, hit 's' for the iPXE shell
-
Afternoon guys, another small glitch. undionly.kpxe, fog 1.5.10.1662.
This is a
System Manufacturer Hewlett-Packard
System Product HP Pro3500 Series
System Version
System Type Type: Desktop
BIOS Vendor AMI
BIOS Version 8.16
BIOS Date 07/17/2013
Motherboard Manufacturer Foxconn
Motherboard Product Name 2ABF
Motherboard Version 3.20
Motherboard Serial Number
Motherboard Asset Tag
CPU Manufacturer Intel Corporation
CPU Version Intel Pentium CPU G2030 @ 3.00GHz
CPU Normal Speed Current Speed: 3000 MHz
CPU Max Speed Max Speed: 3800 MHz
Memory 3.73 GiB
Hard Disk Model SanDisk SSD PLUS 240GB
Hard Disk Firmware UF4004RL
Chassis Manufacturer Hewlett-Packard
Chassis Version
Chassis Serial
Chassis Asset CZC3457Z0Z
GPU-0 Vendor Intel Corporation
GPU-0 Product Xeon E3-1200 v2/3rd Gen Core processor Graphics ControllerI have several of these - about 15 - and all seem ok. This one and 2 others give me the following error upon pxe boot:
GATEWAY IP: 192.168.3.253 Auto-select: Boot to FOG BOOT SERVER IP: 192.168.0.48 PXE->EB: !PXE at 9944:0078, entry point at 9944:0100 UNDI code segment 9944:32CC, data segment 8CFA:C4AG@ (563-626kB) UNDI device is PCI 63:00.6, type DIX+802.3 563KB free base memory after PXE unload iPXE initialising devices... iPXE 1.21.1+ (g5deSd) -- Open Source Network Boot Firmware -- https://ipxe.org Features: DNS FTP HTTP HTTPS iSCSI NFS TFTP VLAN AoE ELF MBOOT PXE bzImage Menu PXEXT Configuring (net0 20:44:fd:14:dd:f6)...... ok Received DHCP answer on interface net0 tftp://192.168.3.253/default.ipxe.... Connection timed out (https://ipxe.org/4c126835) Chainloading failed, hit 's' for the iPXE shell; reboot in 18 seconds_
Hitting ‘s’ and then entering “autoboot” continues with the boot process, into fog, and no more issues. Why would this happen ?
-
@lperoma So I can make the generalization statement that
time
fixes your issue?What I want you to test is this.
PXE boot into the error and then press s to get to the ipxe console.
Wait 20 seconds.
Now key in the following at the console prompt
chain tftp://192.168.3.253/default.ipxe
Does this work and continue into the FOG iPXE menu. In that the only thing different between not working and working is time? (I’m driving to a point here).If time fixes the issue, lets place a dumb switch (unmanaged cheap-o like monoprice) switch between the building network switch and the target computer. Now pxe boot the computer does it boot correctly? If yes then its possibly a spanning tree issue with your building network switch. Make sure your building switch has fastSTP, portfast or whatever your switch mfg calls the fast spanning tree protocol. I might be off base here but it sounds like it might be spanning tree. I know that processor is pretty old, but I don’t think its cpu related.