FROMDEV

Raspberry Pi Network Boot: Requirements and Setup Options

How to Boot a Raspberry Pi Over Ethernet: A Practical Guide

A Raspberry Pi that boots from a network can run without a microSD card in the board, making it easier to manage several devices, replace failed local storage, or keep an installation’s files on a central server. The catch is that “network boot” can mean different things: the Pi may fetch its boot files over Ethernet while still using local storage for its operating system, or it may load both boot files and the operating system from a network share.

For most home and small-lab users, the simplest route is a Pi 4 or Pi 5 using its built-in network boot firmware, a wired connection, and a compatible boot server. This guide explains the requirements, setup options, and common failure points—and how to choose an approach before you start.

What Raspberry Pi network boot does

Network boot is a way for a computer to retrieve the files it needs to start from another device on the local network. On a Raspberry Pi, the boot process begins with firmware in the board’s bootloader. If network boot is enabled and available, the Pi can request boot files from a server instead of reading them from a microSD card or USB drive.

The phrase PXE boot Raspberry Pi is often used to describe this setup, but it is not always technically precise. PXE is a standard commonly associated with PC network booting. Raspberry Pi models use their own boot firmware and network-boot process, even when a server supplies files using familiar network services such as DHCP, TFTP, or NFS.

Choose the right network-boot setup

Network boot with local storage

In this arrangement, the Pi fetches its boot files over Ethernet but uses a microSD card or USB drive for the root filesystem. It is a useful first step because you can test network boot without making the operating system depend entirely on a server.

Full network boot

A fully network-based setup serves both the boot files and the operating system’s root filesystem from another computer or NAS. This can simplify centralized maintenance and reduce the need for storage in each Pi. It also means the server, network, and shared storage must be available whenever the Pi starts and runs.

Network boot from a Raspberry Pi server

A second Raspberry Pi can serve boot files to other Pis, depending on the model, operating system, and server configuration. A dedicated Linux computer or NAS may be a better choice for a larger group of clients, especially if it already provides DHCP or shared storage.

Requirements and compatibility

Before changing boot settings, check the client Pi’s model and firmware. Network-boot support and configuration differ across generations, so follow documentation for your exact board and Raspberry Pi OS release rather than assuming instructions for one model apply to another.

Do not assume your router can serve Raspberry Pi boot files just because it provides DHCP. Many consumer routers cannot host the required boot files or configure the necessary network-boot options. A separate Linux server or a purpose-built setup may be needed.

Step 1: Prepare a boot server

The server’s role depends on whether you want to boot from network only for the initial boot files or run the entire system from network storage. Raspberry Pi Imager offers network-boot server functionality on supported Raspberry Pi OS installations; its availability and workflow can vary by operating-system version. Check the current Raspberry Pi documentation and Imager options before installing separate services.

For a manual server, you may need to configure the appropriate services and prepare boot files for the client. Do not blindly add a second DHCP server to a network that already has one: competing DHCP servers can disrupt connectivity for every device on the LAN. If your router cannot supply the required settings, use a carefully configured network or a documented proxy-DHCP arrangement rather than guessing at router options.

For a full network root filesystem, the server must also export or otherwise provide that filesystem, and the client’s boot configuration must point to it. This is more involved than simply copying files to a TFTP directory. Use current model-specific instructions, and make sure file permissions, paths, and network addresses match your setup.

Step 2: Check EEPROM settings on supported models

The Raspberry Pi 4 and Pi 5 use EEPROM-based boot firmware. Their EEPROM settings determine which devices or methods the board tries during startup. Depending on the firmware version and existing configuration, network boot may already be available or may need to be enabled.

  1. Start the Pi from a working microSD card or USB drive with Raspberry Pi OS.
  2. Update the operating system and bootloader using the supported Raspberry Pi tools, then restart if updates are installed.
  3. Use raspi-config or the current Raspberry Pi bootloader configuration tools to inspect boot-order options. The menu labels can vary by OS version.
  4. Select an order that includes network boot, if needed, and save the configuration.
  5. Shut down, connect Ethernet, and test with the server ready.

On Raspberry Pi OS, raspi-config commonly provides a boot-order menu on supported models. Advanced users can inspect or edit the EEPROM configuration with Raspberry Pi’s bootloader tools, but should avoid copying configuration commands from guides written for a different model or firmware release. Changing boot order does not create a boot server; both ends must be configured.

Step 3: Test the network boot process

Connect the client Pi and server to the same network, then power on the client. Watch the display or server logs if available. A successful attempt should show the Pi obtaining network configuration and retrieving boot files. Once you confirm network boot works, you can remove local boot media if your chosen setup does not need it.

If the Pi falls back to a microSD card, that may mean network boot was not selected, the server did not respond, or the required files were unavailable. Test with local media removed only after you know how to recover the board if the network configuration is incomplete.

Common problems and practical fixes

Keep a tested microSD card or USB drive as a recovery option while experimenting. Network boot shifts some risk from the Pi to the server: if that server is down, clients may not start or may lose access to their root filesystem.

Trade-offs: when is network boot worth it?

Network boot is especially useful for classrooms, device labs, kiosks, and projects where several Pis need a consistent image. A central setup can make updates and replacement easier, and it avoids handling a separate boot card for every device.

For one Pi, a good microSD card or USB SSD is often simpler. Network boot adds server administration, network dependencies, and troubleshooting work. Full network boot also makes uptime dependent on the server and LAN, so it is not automatically more reliable than local storage.

Consider the Pi’s workload, too. A device that processes continuously may need good cooling whether it boots locally or over the network. See these practical tips on how to cool down a Raspberry Pi. If the Pi is part of a display project, this guide to connecting a Raspberry Pi to a projector can help with the output side of the setup. For another always-on use case, review how to set up a Raspberry Pi crypto miner before planning power, cooling, and ongoing operation.

Conclusion

Raspberry Pi network boot can reduce dependence on per-device boot media and make groups of Pis easier to manage. Start by confirming model support, choosing between network boot with local storage and a fully network-based system, and preparing a server that fits your LAN. Then verify the Pi’s EEPROM boot order, test over wired Ethernet, and keep recovery media available.

The most important distinction is that enabling network boot on the Pi is only one part of the job: the network and server must also deliver the right files. For a single board, local storage may be the more practical option. For several devices with a reliable server, a carefully configured network-boot setup can make maintenance much easier.

Exit mobile version