Raspberry Pi Troubleshooting Hub¶
Choose the guide that matches the symptom. Each section provides checks to help identify the cause before changing the configuration.
Diagnostics & Troubleshooting Guides¶
- Start with your symptom — Choose boot, power, networking, storage, display, or peripheral checks and follow the result.
- Slow boot and systemd timings — Read a real Pi 4 report and measure when SSH is ready.
- NetworkManager wait-online and slow boot — Inspect consumers, connection activation, and readiness before disabling a wait.
- OverlayFS changes lost and update problems — Verify actual mounts and maintain a persistent baseline.
- raspi-config command not found and nonint errors — Inspect the package, terminal, permissions, and exact option before applying settings.
- get_throttled values and undervoltage — Decode current and historical flags and verify power or cooling repairs.
- llama.cpp memory-lock errors — Inspect load modes, process limits, systemd settings, and OOM evidence.
- NetworkManager update errors and APT repair — Identify the package failure stage and preserve remote access.
- USB gadget missing usb0 or not detected — Diagnose the controller, gadget, host, network, and SSH layers.
Common Issues & Solutions
Choose your symptom, interpret the first checks, and follow the matching boot, network, power, storage, or peripheral procedure.
Performance TroubleshootingDiagnose and fix speed bottlenecks, CPU overload, memory pressure, ZRAM configuration, and thermal throttling.
Frequently Asked QuestionsQuick answers to common questions about headless setups, WayVNC remote desktop, security hardening, and password recovery.
Quick Diagnostic Flowchart¶
Start by checking whether you can reach a terminal locally or over SSH:
flowchart TD
accTitle: Choose a Raspberry Pi troubleshooting starting point
accDescr: If a local or SSH terminal is available, check the failed feature or investigate performance. Otherwise start with power, boot messages and network access.
A{Terminal<br/>available?}
A -->|No| B[Check power<br/>boot and access]
A -->|Yes| C{Task<br/>works?}
C -->|No| D[Check the<br/>failed feature]
C -->|Yes, slowly| E[Measure the<br/>slow stage]
Follow the symptom checks, or use performance diagnosis when the task completes slowly.