lpxelinux.0 error: no such file or directory
This document describes the logfile "error" messages related to PXE booting that an operator might normally see. This condition does not necessarily indicate any problems with your system.
After TFTPing lpxelinux.0, logs (or network packet traces) may show an error similar to:
This is expected behavior that is standard PXE waterfall searching for a valid filename to boot from. For full reference, please see the syslinux reference documentation, at:
The expected behavior is for a client to attempt to download files in the following order:
- client id (DRP does not use this option, which is what generates the error)
- mac address (in the form of
- ip address in uppercase Hexadecimal format, stepping through IP, subnet, and classful boundaries
- fall back to the default defined file
Due to this behavior, filenames will be specified that do not exist, and the error message related to that probe request is a normal message. This is NOT an indicator that provisioning is broken in your environment.
Additional resources and information related to this Knowledge Base article.
dhcp, pxe, lpxelinux, pxelinux.cfg, syslinux, pxe waterfall, pxe chaining, pxe boot order