Skip to content

Raspberry Pi 5 Headless Setup: First Boot and SSH Checklist

For Raspberry Pi 5 headless setup, prepare Raspberry Pi OS and SSH in Imager, then boot with suitable power and a simple network path. Use this page for the Pi 5-specific power, storage and boot checks; use the shared headless procedure for account, key and SSH steps. You do not need to install twice.

If you already have a working SSH login, skip first-boot preparation. If a connection attempt failed, use the symptom-based troubleshooter rather than rewriting the card.

Pi 5 first-boot checklist

  • Power: the official 27 W USB-C supply is the recommended baseline. A suitable 5 V / 3 A supply can boot a Pi 5, but USB peripheral power is restricted; it is not the same budget as a detected 5 V / 5 A supply. Leave unnecessary USB drives and other high-draw peripherals disconnected for this first test.
  • Boot media: select Raspberry Pi 5 in Imager and use a supported image. Start with verified microSD if NVMe/USB boot has not already worked. Do not add storage-boot configuration while also diagnosing networking.
  • Network: connect Ethernet to the router before power-up when available, or configure the intended Wi-Fi network in Imager. Ethernet removes Wi-Fi provisioning variables; it does not bypass guest-network isolation.
  • Account and SSH: create your own account and enable SSH in Imager. Keep the account password for administration even when using a public key for SSH.
  • Boot indication: observe the power-button/status LEDs and storage activity. Interpret an actual repeating pattern using the model's documented codes, not colour alone.

The official hardware documentation explains power budgets; the LED behaviour reference explains model-specific signals. A lit power indicator alone does not prove Linux, DHCP or SSH is ready.

Outcome: separate a Pi 5 power/boot problem from a network, name-discovery or SSH-authentication failure, then follow one matching procedure.

Prepare and boot once

  1. Follow Steps 1–2 of the headless procedure on the client computer. Select your Pi 5, image and card; configure the account, network and SSH key. Back up required data and identify the storage carefully: writing erases it.
  2. Allow Imager's verification to finish. Safely remove the card, insert it into the unpowered Pi 5 and attach Ethernet if selected.
  3. Apply the appropriate supply last. If the board is in standby, use the power button according to the official first-boot guidance. Allow initial provisioning to finish; do not repeatedly interrupt power.
  4. Continue to find the Pi and connect. Use the hostname/account you actually configured, or the known router DHCP lease, and verify host identity before accepting a key.

Choosing Lite gives you a terminal, not a graphical desktop. Connect/VNC setup is a later, separate task.

If SSH fails, identify the layer first

No lease and no convincing boot activity

Recheck the supply, intended image, verified card and documented LED pattern. Do not rewrite network files before establishing whether the board booted. If NVMe/USB is involved, return to a known verified microSD baseline before changing several variables together. A missing DHCP lease alone is not proof of a boot failure.

Lease exists but the hostname fails

Use the known lease address with the configured username. If that works, investigate client mDNS/network discovery rather than changing SSH or reinstalling Raspberry Pi OS.

Timeout, refused connection or rejected key

These do not mean the same thing. The headless troubleshooter distinguishes route/filtering, service/listener and account/key failures. Network policy can also cause a rejection; an error message alone is not a complete diagnosis. Keep host-key verification enabled.

For local recovery, inspect the board with a keyboard/display if available. Do not guess a USB fallback address or assume a laptop's USB port provides sufficient power for the Pi 5.

Verify the first login

Follow the shared post-login checks: confirm the intended hostname/OS, active interface, route and SSH startup, then make a second connection.

If you suspect a power problem, run this read-only inspection on the Pi:

1
vcgencmd get_throttled

Use the get_throttled decoder to separate current flags from recorded history. This command is not a measurement of available USB power, and a zero result is not a guarantee for every future workload.

Complete updates and reconnection only after checking recovery and automatic SSH startup. Do not reboot remotely just to test an unresolved power fault.

Continue from here

Verification scope

This checklist uses the primary Raspberry Pi documentation above. It does not claim a new Pi 5 card write, power test, LED observation or first-boot trial for this revision. The site's available test board is a Pi 4B; shell syntax and rendered links do not establish Pi 5 hardware behaviour.

Donate