Notes

Boot a Raspberry Pi 4 or 5 from USB storage

Check boot order before reflashing anything, prepare a separate USB system disk and diagnose power or adapter problems independently of the bootloader.

On a Raspberry Pi 4 or 5, USB boot depends on the EEPROM bootloader’s boot order and a bootable operating-system image on the USB device. They are two separate pieces. Writing an operating-system image to an SSD does not update the board’s EEPROM, and updating the EEPROM does not install an operating system on the SSD.

Recent bootloaders support USB mass-storage boot. An early Pi 4 may need a bootloader update first. This procedure is for those EEPROM-based boards; older Pi models have different requirements, including permanent OTP settings on some models. Do not apply those older instructions to a Pi 4 or 5.

Check the current configuration

With Raspberry Pi OS already running on the board, inspect its bootloader and open the configuration tool:

sudo rpi-eeprom-update
sudo raspi-config

Use the boot-order option under the advanced settings to select a policy that includes USB boot. Menu labels can change between tool releases; choose the behavior rather than copying a menu number. Reboot when prompted.

The EEPROM tools are supplied by Raspberry Pi OS. They are not generic commands available on every distribution. If the tool reports that an update is needed, follow its documented update procedure and use stable firmware appropriate to the board rather than an arbitrary downloaded image.

Recover or change the bootloader with Imager

If you cannot boot the installed system, Raspberry Pi Imager can prepare a separate, expendable microSD card with a bootloader utility image. Select the Raspberry Pi model first, then find the utility bootloader image and USB boot option appropriate to it.

Writing the utility image erases the selected card. Confirm its identity before writing. Boot the Pi with that card and follow the utility’s completion indication; then power down and remove it. Do not interrupt the firmware write or assume a fixed delay proves it completed.

This recovery card is a tool for the board’s bootloader. It is not the system disk you are preparing in the next step.

Prepare and test the USB system disk

Use Imager to write a supported operating-system image to the intended USB SSD or flash drive. This also erases that target, so verify the selected device independently of the recovery card. Configure credentials and network access in Imager if you need a headless first boot.

Power down, attach the USB disk and remove the ordinary OS microSD card for the first test. This makes the result unambiguous: if the board starts, it did not silently fall back to the SD installation.

After booting Linux, inspect the mounted root filesystem:

findmnt /
lsblk -o NAME,TRAN,SIZE,FSTYPE,MOUNTPOINTS

If booting fails, check the power supply and the USB bridge as well as the image. An SSD enclosure may need more power than the board can supply. A USB-to-SATA adapter can also work after Linux starts yet fail during boot. Test another supported adapter or a powered enclosure before repeatedly rewriting the firmware.

Raspberry Pi’s USB mass-storage boot documentation covers model differences; its EEPROM documentation explains firmware updates.