Power & hardware
Power cuts, UPS, boot failures, physical NAS hardware, and recovery after outages.
40 entries — IDs PWR-001 through PWR-040.
PWR-001: Power cut — NAS won't come back on
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: UPS drained, breaker tripped, or PSU fault. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Blackout ended; DXP 8800 Plus dark or fans not spinning. Likely cause: UPS drained, breaker tripped, or PSU fault. Fix: 1. Check wall power and UPS output. 2. Press NAS power button once; wait 2 minutes. 3. If no lights, check breaker panel. 4. Do not yank drives while powered off.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Power Outage Recovery Deep dive: Power outage recovery
PWR-002: Pool degraded after power outage
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Drive didn't remount or failed during outage. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Power returned; TrueNAS shows DEGRADED. Likely cause: Drive didn't remount or failed during outage. Fix: 1. Wait for full boot — all disks ONLINE. 2. If still degraded, follow pool degraded guide. 3. Run SMART on all disks. 4. Replace any drive with new errors.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server When Pool Degraded Deep dive: Power outage recovery
PWR-003: UPS beeping after outage
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: On battery or battery end-of-life. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Unifi or NAS UPS alarming. Likely cause: On battery or battery end-of-life. Fix: 1. Acknowledge alarm per UPS manual. 2. Restore mains power. 3. Replace UPS battery if old. 4. Test UPS self-test monthly.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Power Outage Recovery Deep dive: Power outage recovery
PWR-004: Should NAS be on UPS?
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Clean shutdown needs UPS signaling. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Short outages cause issues. Likely cause: Clean shutdown needs UPS signaling. Fix: 1. NAS and router on UPS recommended. 2. Configure UPS shutdown script if available. 3. Minimum: avoid abrupt power loss during writes.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics Physical Equipment Map Deep dive: Power outage recovery
PWR-005: NAS reboot loop after storm
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: PSU, RAM, or drive preventing boot. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Fans spin, reboot, repeat. Likely cause: PSU, RAM, or drive preventing boot. Fix: 1. Disconnect non-essential USB. 2. Boot with minimum drives only if expert — risky. 3. Otherwise contact support/Ryan. 4. Do not RMA pool disks as first step.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Turn Everything On Deep dive: Power outage recovery
PWR-006: Smell of burning from NAS
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: PSU or backplane failure — fire risk. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Electrical burn smell from DXP 8800 Plus. Likely cause: PSU or backplane failure — fire risk. Fix: 1. Pull power plug immediately. 2. Do not restart until inspected. 3. Photo damage for insurance. 4. Professional hardware inspection before reuse.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover Notify Insurance And Utilities Deep dive: Power outage recovery
PWR-007: Fan noise suddenly loud
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Fan failure, dust, or high CPU from transcodes. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: NAS sounds like jet engine. Likely cause: Fan failure, dust, or high CPU from transcodes. Fix: 1. Check TrueNAS CPU temps. 2. Clean dust filters. 3. Verify all chassis fans spin. 4. Replace failed fan module.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics Physical Equipment Map Deep dive: Power outage recovery
PWR-008: Room too hot for NAS
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Poor ventilation summers. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Closet or rack overheating. Likely cause: Poor ventilation summers. Fix: 1. Move airflow or add room AC/fan. 2. Open closet door. 3. Monitor drive temps in SMART.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics Physical Equipment Map Deep dive: Power outage recovery
PWR-009: Lightning strike — what to check
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Surge damage possible. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Storm nearby; gear acting odd. Likely cause: Surge damage possible. Fix: 1. Inspect UPS absorbed surge indicator. 2. Test NAS SMART all drives. 3. Replace suspicious network gear. 4. Consider whole-home surge protection.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Power Outage Recovery Deep dive: Power outage recovery
PWR-010: Cannot reach NAS after power restore
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Network gear also rebooting; IP conflict. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Power on but 192.168.2.203 dead. Likely cause: Network gear also rebooting; IP conflict. Fix: 1. Wait 5 min for UniFi Dream Machine SE. 2. Power-cycle switch if no link lights. 3. Confirm NAS Ethernet linked. 4. Check DHCP reservation for .203.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Turn Everything On Deep dive: Power outage recovery
PWR-011: Apps didn't start after power return
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Docker service slow start or pool delayed mount. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: TrueNAS up but Jellyfin etc. down. Likely cause: Docker service slow start or pool delayed mount. Fix: 1. Wait 10 minutes post-boot. 2. Start Docker/k3s if stopped. 3. Start apps in order: cloudflared, NPM, media. 4. See Docker FAQ.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Turn Everything On Deep dive: Power outage recovery
PWR-012: Windows A: drive red X after outage
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: NAS was off during Windows boot. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Mapped drive disconnected. Likely cause: NAS was off during Windows boot. Fix: 1. Reconnect A: when NAS online. 2. Enable reconnect at sign-in on map drive. 3. Verify share path.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Windows Pc Basics Deep dive: Power outage recovery
PWR-013: cloudflared down after reboot
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Tunnel app didn't auto-start. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: External sites dead; LAN OK. Likely cause: Tunnel app didn't auto-start. Fix: 1. Start cloudflared in TrueNAS Apps. 2. Set start on boot. 3. Check tunnel logs.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Restart Cloudflared Deep dive: Power outage recovery
PWR-014: Scheduled shutdown before storm
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Manual shutdown done right. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Preemptive shutdown confusion. Likely cause: Manual shutdown done right. Fix: 1. Use TrueNAS Shut Down from UI. 2. Wait for lights off. 3. UPS protects network gear. 4. Power on after storm passes.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Power Outage Recovery Deep dive: Power outage recovery
PWR-015: NAS powered off during resilver
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Pool may resume or show errors. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Accidental unplug during rebuild. Likely cause: Pool may resume or show errors. Fix: 1. Power on and wait — do not touch drives. 2. Check pool status and resilver progress. 3. Run scrub after resilver completes. 4. Avoid repeat — use UPS.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server When Pool Degraded Deep dive: Power outage recovery
PWR-016: BIOS/UEFI settings lost
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: CMOS battery or firmware glitch. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Rare clock or boot order wrong. Likely cause: CMOS battery or firmware glitch. Fix: 1. Set boot to OS drive. 2. Verify all drives detected in BIOS. 3. Contact Ugreen support if drives missing.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Truenas Basics Deep dive: Power outage recovery
PWR-017: Drive bay hot-swap during power on
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: May work on DXP — risky if unsure. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Swapped drive without shutdown. Likely cause: May work on DXP — risky if unsure. Fix: 1. Prefer shutdown for replacement unless documented hot-swap. 2. If pool degraded, follow degraded guide. 3. Never swap two drives at once.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server When Pool Degraded Deep dive: Power outage recovery
PWR-018: Ethernet link light off on NAS
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Bad cable, port, or NIC. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: No network despite power on. Likely cause: Bad cable, port, or NIC. Fix: 1. Try different cable and switch port. 2. Check link on switch side. 3. Reboot NAS once. 4. USB NIC fallback only if documented.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home When Internet Broken Deep dive: Power outage recovery
PWR-019: Whole home power out — priority order
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Unknown restart sequence. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Everything dark. Likely cause: Unknown restart sequence. Fix: 1. Power: modem/ONT → UniFi → NAS → PC. 2. Wait between layers. 3. See turn everything on guide.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Turn Everything On Deep dive: Power outage recovery
PWR-020: Generator power — safe for NAS?
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Dirty power can harm electronics. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Running on generator during extended outage. Likely cause: Dirty power can harm electronics. Fix: 1. Use UPS between generator and NAS. 2. Avoid startup surges. 3. Shutdown NAS if voltage unstable.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Power Outage Recovery Deep dive: Power outage recovery
PWR-021: NAS draws too much at startup
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Inrush current from 7+ spinning disks. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Breaker trips when NAS + PC start. Likely cause: Inrush current from 7+ spinning disks. Fix: 1. Stagger power-on of heavy devices. 2. Dedicated circuit for NAS if possible. 3. Check electrician for panel capacity.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics Physical Equipment Map Deep dive: Power outage recovery
PWR-022: Front panel power button unresponsive
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Button fault or motherboard issue. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Cannot power on via button. Likely cause: Button fault or motherboard issue. Fix: 1. Try rear power switch if present. 2. Check UPS output. 3. Hold button 10s for hard off then on.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Turn Everything On Deep dive: Power outage recovery
PWR-023: LED status unclear on DXP 8800 Plus
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Wait for UI reachable at .203. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Don't know if boot finished. Likely cause: Wait for UI reachable at .203. Fix: 1. Ping 192.168.2.203. 2. Open dsm.saxobroko.com when on LAN. 3. Full boot may take 5–10 minutes.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Truenas Basics Deep dive: Power outage recovery
PWR-024: Hear drives spin up then down repeatedly
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Power supply insufficient or drive fault. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Drives cycling on boot. Likely cause: Power supply insufficient or drive fault. Fix: 1. Stop cycling — pull power. 2. Remove recently added hardware. 3. Test with support — don't guess drive order.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server When Pool Degraded Deep dive: Power outage recovery
PWR-025: UPS software not connected to TrueNAS
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: USB cable not linked or NUT not configured. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: UPS can't auto-shutdown NAS. Likely cause: USB cable not linked or NUT not configured. Fix: 1. Optional improvement: connect UPS USB. 2. Configure NUT in TrueNAS. 3. Until then, manual shutdown on long outages.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Power Outage Recovery Deep dive: Power outage recovery
PWR-026: Battery backup runtime too short
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Undersized UPS or old battery. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: UPS dies in 5 minutes. Likely cause: Undersized UPS or old battery. Fix: 1. Size UPS for NAS + router 15+ min. 2. Replace battery every 3–5 years. 3. Graceful shutdown beats sudden off.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics Physical Equipment Map Deep dive: Power outage recovery
PWR-027: Physical move of NAS to new house
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Shock damage if running. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Relocating DXP 8800 Plus. Likely cause: Shock damage if running. Fix: 1. Full shutdown and unplug. 2. Label drive bays if removing trays. 3. Transport upright secured. 4. Wait 30 min at new location before power on.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics Physical Equipment Map Deep dive: Power outage recovery
PWR-028: Dropped NAS — drives OK?
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Head crash risk even when off. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Unit fell or bumped hard. Likely cause: Head crash risk even when off. Fix: 1. Do not power on immediately. 2. Listen for clicks on boot. 3. Run full SMART on all drives. 4. Replace any with new errors.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Read Smart Disk Errors Deep dive: Power outage recovery
PWR-029: Water leak near NAS
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Electrical hazard and corrosion. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Moisture in rack/closet. Likely cause: Electrical hazard and corrosion. Fix: 1. Power off and unplug immediately. 2. Dry area before restart. 3. Inspect for corrosion. 4. Insurance claim if damaged.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover Notify Insurance And Utilities Deep dive: Power outage recovery
PWR-030: Pets chewed network or power cable
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Physical damage. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Intermittent disconnects. Likely cause: Physical damage. Fix: 1. Replace damaged cables entirely. 2. Route cables protected. 3. Check for short before power on.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics Physical Equipment Map Deep dive: Power outage recovery
PWR-031: NAS in garage — temperature extremes
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Out of spec operation. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Winter cold / summer heat. Likely cause: Out of spec operation. Fix: 1. Move to climate-controlled space. 2. Drives fail faster in extremes. 3. Check SMART temps weekly if must stay.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics Physical Equipment Map Deep dive: Power outage recovery
PWR-032: Power button accidentally pressed
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Bump or kids. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Brief shutdown mid-stream. Likely cause: Bump or kids. Fix: 1. Wait for clean shutdown if graceful. 2. Power on after 30 seconds. 3. Check pool and apps. 4. Use physical lock or rack guard if repeat.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Power Outage Recovery Deep dive: Power outage recovery
PWR-033: Firmware update bricked after power loss
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Power lost during flash. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: NAS won't boot after failed update. Likely cause: Power lost during flash. Fix: 1. Contact TrueNAS/Ugreen support. 2. Do not swap pool drives to another machine blindly. 3. Pool data often intact if drives untouched.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Truenas Basics Deep dive: Power outage recovery
PWR-034: Redundant PSU if one fails?
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Check hardware spec — may be single PSU. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: DXP 8800 Plus PSU question. Likely cause: Check hardware spec — may be single PSU. Fix: 1. Know your model's PSU count. 2. Keep spare PSU part number if dual. 3. Sudden off may be PSU — not always disk.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics Physical Equipment Map Deep dive: Power outage recovery
PWR-035: Ryan — first power outage alone
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: New operator panic. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Inherited NAS; lights flickered. Likely cause: New operator panic. Fix: 1. Wait for power stable. 2. Turn on network then NAS. 3. Check pool HEALTHY before heavy use. 4. Read power outage recovery guide fully.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover Who Gets What Deep dive: Power outage recovery
PWR-036: Status page wrong after outage
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Services still starting. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: status.saxobroko.com shows all red. Likely cause: Services still starting. Fix: 1. Wait 15 minutes. 2. Refresh Homepage/status. 3. Fix NAS and cloudflared first.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Check Status Page Deep dive: Power outage recovery
PWR-037: Clock wrong after long power off
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: CMOS battery or NTP not synced. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: TLS errors on apps. Likely cause: CMOS battery or NTP not synced. Fix: 1. Fix TrueNAS NTP. 2. Reboot router if time wrong network-wide. 3. Retry HTTPS sites.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Truenas Basics Deep dive: Power outage recovery
PWR-038: Multiple brownouts in one day
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Utility grid instability. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Lights dim repeatedly. Likely cause: Utility grid instability. Fix: 1. Minimize writes during brownouts. 2. UPS helps ride through. 3. Consider shutting NAS until stable. 4. Log incidents for utility report.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Power Outage Recovery Deep dive: Power outage recovery
PWR-039: Insurance claim for NAS hardware
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Need documentation. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Lightning destroyed unit. Likely cause: Need documentation. Fix: 1. Photo serial numbers and damage. 2. Note purchase date if known. 3. Pool data separate from hardware claim. 4. Notify insurer per handover guide.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover Notify Insurance And Utilities Deep dive: Power outage recovery
PWR-040: When to call a professional
Stack context: Physical power · UDM · NAS · NBN Integrated runbooks: Outage runbook · PWR recovery order
Why this happens: Beyond home repair safe zone. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Hardware smells, clicks, or pool FAULTED. Likely cause: Beyond home repair safe zone. Fix: 1. Stop using NAS. 2. Do not run filesystem repair tools on ZFS pool. 3. Data recovery labs for FAULTED + critical data. 4. Ryan: use Saxon's contacts or IT pro.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover First 24 Hours Deep dive: Power outage recovery