Umbrel 0.5.1 on PI 4 (formerly a Casa 2 node).
Had been running happily for months, but recently went offline, although the Pi itself seemed to be running. Tried to connect through browser, then ssh, no joy.
Reluctantly, did an unplug/replug. No joy. Was busy, so let it sit for a week or two. Unplugged and moved to office desk, thinking I’d check the SD card. It started up, red steady and green blinky light, blue light on SSD - seemed okay. Huh. Joy?
Node claimed it was ~97% synced, which seemed odd, given that it’d been offline for weeks. Attempted to update from 0.5.1 to 0.5.3 from Settings; downloaded fine so then ran install from the settings page. Didn’t take. Sh*t.
Did a second try, because I was interrupted during the first update and didn’t see what was transpiring in real time. Update failed a second time, system remained at 0.5.1. After 12 minutes, system locked up, and I could not get access through either SSH or browser. Rebooted, lasted about the same amount of time again, then went unresponsive.
Ran Debug (see below).
Next, attempted command line update (see below). Also unsuccessful, but am Pi noob, so perhaps issue is between screen and seat?
Dug out Balena Etcher, downloaded/unziped 0.5.3 image, and reflashed SD. Flash failed to confirm.
Ordered new SD (Sandisk Ultra 32 GB). Flashed and confirmed. Progress?
Inserted new/flashed SSD in Pi. Pi fails to boot. Steady red light (no power problem); but no green lights. This is definitely not progress, actually even more failed than when began troubleshooting.
Reflashed both the new SD (again, successful) and the original (again, failed). New/reflashed SD reinserted (yes, the new 32GB, not old 16GB - double-checked). Red light, no green lights, no joy.
Transparency: While working on this, had also removed a dead/POS Fan Shim fan and replaced with the third Fan Shim I’ve had on this device. Have been running the Pi topless in a closet with one of the mesh devices and it had been steady cool, ever since the Fan Shim #2 went noisy and erratic about 6 months ago.
Have checked against pre-install photo, and 5V jumper is on Pin 2, which I believe is correct - or at least the same as before, when things were running smoothly. Removed the new fan, as that seems like a secondary problem, and wanted to eliminate that part as a source of concern.
At this point, I’m running out of ideas, open to other strategies.
– Debug and command line stuff below –
= Umbrel debug info =
Flashed OS version
Raspberry Pi Model
Revision : c03111
Serial : 100000001d869b22
Model : Raspberry Pi 4 Model B Rev 1.1
Feb 25 2021 12:10:40
Copyright © 2012 Broadcom
version 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean) (release) (start)
total used free shared buff/cache available
Mem: 3.8G 203M 3.0G 6.0M 627M 3.5G
Swap: 4.1G 73M 4.0G
+ Stopped ~/umbrel/scripts/debug
umbrel@umbrel:~/umbrel $ cd ~/umbrel && sudo ./scripts/update/update --repo getumbrel/umbrel#v0.4.8cd ~/umbrel && sudo ./scripts/update/update --repo getumbrel/umbrel#v0.5.3
[sudo] password for umbrel:
Cloning into ‘/tmp/umbrel-update’…
warning: Could not find remote branch v0.4.8cd to clone.
fatal: Remote branch v0.4.8cd not found in upstream origin
fatal: not a git repository: ‘/tmp/umbrel-update//.git’
mv: cannot stat ‘/tmp/umbrel-update//info.json’: No such file or directory
jq: error: Could not open file /tmp/umbrel-update//info.json.orig: No such file or directory
Update path doesn’t seem to be an Umbrel install.
umbrel@umbrel:~/umbrel $ client_loop: send disconnect: Broken pipe