HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

No boot filename received PXE-E53

 
station2010
Occasional Visitor

No boot filename received PXE-E53

Hi,

 

We have a Proliant DL180G6 server on site running server 2008.  This morning it shows on screen No Boot filename Received PXE-E53 and will not boot up at all.  Can anyone give me any suggestions on how I can correct this ?

1 REPLY
Matti_Kurkela
Honored Contributor

Re: No boot filename received PXE-E53

The message indicates your server is trying to boot from network: the first step of a PXE network boot process is getting an IP address and the name of the bootloader file from the DHCP server. If the information received from the DHCP server does not include the name of the bootloader file, you'll get exactly that error message.

 

  • If your server is supposed to boot from network, it means your DHCP server configuration no longer supports network boot. Fix the DHCP server.
  • If your server should be booting from local disks, it means your local disks are no longer bootable and the server is trying any other boot methods that are allowed in the BIOS configuration. If your system disks were configured with RAID1 or RAID5, this means you have at least 2 failed disks, which is more than those RAID levels can handle: the data is now lost. The simplest way to recover would be to replace the failed disks, recreate the RAID configuration if necessary, and then restore the system from backups. (You *do* have backups, don't you?)
MK