Skip to content

Raspberry Pi Troubleshooting Guide: ACT LED Blink Codes, SSH & Power Diagnostics

Created: 2026-11-08 Last updated: 2026-11-08

Executive Summary: When a Raspberry Pi refuses to boot, drops offline, or rejects SSH connections, newcomers are often left stranded with no monitor output or descriptive error logs. Fortunately, the hardware is equipped with built-in diagnostic systems: the VideoCore firmware and bootloader communicate hardware failures directly through rhythmic flash patterns on the green ACT LED, while the kernel tracks voltage dips and thermal throttling inside firmware registers. This guide serves as your definitive emergency first-aid kit, providing exact diagnostic tables, host-key resolution commands, and a structured recovery decision tree.

  • ACT LED Blink Codes

    Decode pre-boot firmware signals: identify missing start.elf binaries, unsupported board revisions, and defective SDRAM chips.

  • SSH Connection Repairs

    Resolve "Connection Refused", wipe obsolete host fingerprints (ssh-keygen -R), and bypass German/English keyboard layout password traps.

  • Undervoltage Telemetry

    Decode the exact bitmask returned by vcgencmd get_throttled to pinpoint brownouts caused by thin USB phone cables.

  • Flash Storage Rescue

    Understand why microSD cards enter permanent read-only lock, run fsck filesystem repairs, and recover using EEPROM recovery images.

When a Raspberry Pi powers on, its primary processor does not launch immediately. Instead, the small EEPROM bootloader and VideoCore GPU initialize first and read the boot partition of your microSD card or NVMe SSD.

If an error prevents the system from booting, the green ACT LED flashes a repeated Morse-like error code:

%%{init: {'flowchart': {'wrappingWidth': 600, 'subGraphTitleMargin': {'top': 15, 'bottom': 15}}}}%%
flowchart TB
    POWER["Apply USB-C Power"] --> PWR_CHECK{"Is Red PWR LED Solid?"}
    PWR_CHECK -->|"No / Flickers"| BAD_POWER["Undervoltage Failure!<br/>Replace PSU with Official 27W/15W Adapter."]
    PWR_CHECK -->|"Yes (Solid Red)"| ACT_CHECK{"What is Green ACT LED doing?"}

    ACT_CHECK -->|"Rapid Irregular Flickering"| OK_BOOT["Normal Boot Process!<br/>Kernel loaded, initializing system."]
    ACT_CHECK -->|"Repeated Rhythmic Flash Pattern"| BLINK_ERROR["Firmware POST Error!<br/>Count flashes between pauses."]
    ACT_CHECK -->|"Solid ON or Completely Dark"| NO_CARD["Bootloader cannot read card!<br/>Clean slot or re-flash card."]

Count the number of green flashes that occur between longer pauses:

Flash Count Meaning / Failure Stage Root Cause & Immediate Fix
3 Flashes start.elf not found The FAT32 boot partition is unreadable, corrupted, or the start.elf file was accidentally deleted. Fix: Re-flash the microSD card with Raspberry Pi Imager.
4 Flashes start.elf cannot launch The firmware image is incompatible with this board model (e.g. attempting to boot an obsolete 32-bit Buster image on a Raspberry Pi 5). Fix: Use the latest 64-bit Bookworm image.
7 Flashes Kernel image not found start.elf executed, but the Linux kernel binary (kernel8.img) is missing from /boot/firmware/.
8 Flashes SDRAM failure / not recognized The soldered LPDDR memory chip failed power-on self-test (POST). Usually caused by physical board damage or defective hardware.
Continuous Slow Blink Thermal shutdown or board halt SoC temperature exceeded safety threshold, or the system executed an orderly poweroff command.

2. Solving SSH Connection Problems

A freshly flashed Raspberry Pi that appears to boot normally may still refuse remote connections. Here are the three most frequent obstacles:

Problem 1: ssh: connect to host ... port 22: Connection refused

  • Root Cause: The SSH service was not activated during the flashing process in the Imager.
  • The Zero-Reinstallation Fix:
  • Remove the microSD card from the Pi and insert it back into your PC or Mac.
  • Open the visible FAT32 drive (labeled bootfs or boot).
  • Create an empty file named exactly ssh (without any file extension like .txt).
  • Eject the card, insert it into the Pi, and power it up. During boot, the system detects the ssh file, enables the OpenSSH server, and deletes the trigger file.

Problem 2: WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!

If you re-flashed your Raspberry Pi or assigned it an IP address previously used by another computer, your workstation's SSH client warns of a possible security breach:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
Offending key in /home/user/.ssh/known_hosts:42
  • Root Cause: Your workstation saved the old cryptographic host key fingerprint.
  • The Fix: Remove the obsolete key from your workstation's cache with one command:
Purging the Obsolete Fingerprint from your PC
ssh-keygen -R rpi-server.local
# Or by IP address:
ssh-keygen -R 192.168.1.145

Now reconnect with ssh yourusername@rpi-server.local and accept the new fingerprint with yes.

Problem 3: Permission denied (publickey,password)

  • Root Cause: A password typo caused by the German vs. English Keyboard Trap.
  • When defining a password in the Raspberry Pi Imager, if your workstation uses a German layout (QWERTZ) while the Pi default was set to English (QWERTY), the letters Z and Y are reversed, and special symbols (-, _, !, ?) move to entirely different keys!
  • Fix: If your password contains y or z, try typing the alternate letter during the SSH login prompt.

3. Undervoltage Telemetry: Decoding vcgencmd get_throttled

When a Raspberry Pi encounters insufficient voltage, it does not always crash immediately. Instead, the VideoCore PMIC throttles the CPU cores and flags the incident in an internal hardware bitmask register.

Query the register via SSH:

Auditing Hardware Throttling State
vcgencmd get_throttled

Output example: throttled=0x50005

%%{init: {'flowchart': {'wrappingWidth': 600, 'subGraphTitleMargin': {'top': 15, 'bottom': 15}}}}%%
flowchart LR
    VAL["Hex Value: 0x50005"]
    L16["Bit 0 (0x1) + Bit 2 (0x4):<br/>Current Undervoltage & Frequency Capped!"]
    H16["Bit 16 (0x10000) + Bit 18 (0x40000):<br/>Historical Undervoltage occurred since boot!"]

    VAL --> L16
    VAL --> H16

Decoding the Bitmask Hex Values

The returned hex value is a 32-bit field where the lower 16 bits represent Current Conditions and the upper 16 bits represent Historical Events since Boot:

Bit Position Hex Mask Meaning Root Cause & Engineering Solution
Bit 0 0x1 Under-voltage currently detected (< 4.63V) Power supply wire is sagging. Replace with Official 27W/15W PSU.
Bit 1 0x2 ARM frequency currently capped (> 80°C) CPU is overheating. Install an Active Cooler or heatsink.
Bit 2 0x4 Currently throttled Hard throttling active to prevent chip damage.
Bit 16 0x10000 Under-voltage has occurred since boot Voltage dropped temporarily during load spike (e.g. spinning up external drive).
Bit 17 0x20000 ARM frequency capping has occurred System overheated in the past and shed clock speed.
Bit 18 0x40000 Throttling has occurred since boot System was severely throttled historically.

If vcgencmd get_throttled returns anything other than throttled=0x0, your system is compromised by either power sag or excessive heat!

4. MicroSD Card Longevity: The Read-Only Failure Mode

MicroSD cards use flash NAND memory blocks with a finite number of write/erase cycles (~3,000 to 10,000 cycles).

When a cheap card exhausts its pool of spare blocks due to continuous logging or database writes, the memory controller locks the card into permanent Hardware Read-Only Mode to preserve existing data from total loss.

Symptoms of a Failed MicroSD Card:

  1. You can log into the Pi via SSH, create a file (touch test.txt), but upon rebooting, the file has vanished!
  2. Running apt update throws errors like Read-only file system or I/O error.
  3. The green ACT LED blinks rapidly without making progress.

Repairing Filesystem Errors (fsck)

If a card was ungracefully disconnected without sudo poweroff, run a non-destructive filesystem check from another Linux computer or recovery mode:

Checking Root Filesystem Partition
sudo fsck.ext4 -f /dev/mmcblk0p2

5. The Emergency Recovery Checklist

When a Raspberry Pi refuses to boot, follow this systematic elimination hierarchy:

  • Check the Red PWR LED

    Is it solid red? If blinking or dark, throw away the phone charger and connect the Official Raspberry Pi Power Supply.

  • Observe the Green ACT LED

    Is it blinking rhythmically? If you count 3 or 4 flashes, the OS image is corrupt. Re-flash with Raspberry Pi Imager.

  • Verify Network Cables & mDNS

    Check if the Ethernet port LEDs (Amber/Green) are flickering. If yes, check your router DHCP client list for the assigned IP address.

  • Inspect /boot/firmware/config.txt

    Did you edit config.txt recently? A single typo in an overclock or dtoverlay parameter can prevent bootloader execution. Revert changes.

Summary of the Fundamentals Module

You have completed the entire Fundamentals & First Steps curriculum: 1. You understand SBC hardware architecture, power supply demands, and A2 SD cards. 2. You successfully launched a headless system via Raspberry Pi Imager and OpenSSH. 3. You mastered raspi-config, Debian APT package management, and safe shutdown commands. 4. You wired physical breadboard circuits and controlled hardware using Python gpiozero. 5. You possess the diagnostic knowledge to decode hardware blink patterns and fix network/power faults.

Proceed to Module 2 to master advanced hardware architecture, PCIe NVMe SSD integration, and active thermal cooling:

  • Next Module: Hardware Architecture, Power & Storage

    Explore Broadcom SoC internals, the custom RP1 southbridge, PCIe Gen 3 NVMe configuration, and multi-node fleet provisioning.

    Advance to Module 2