0.5.0 Update Failing... or is it?

I’m currently running 0.4.18 on my Pi and am unable to complete the update to 0.5.0. The UI says “update failed - unable to perform app migrations”

I’ve tried SSH’ing in to do rm -f ~/umbrel/statuses/update-in-progress && sudo reboot but that didn’t help.

Looking in my debug logs, I see something super confusing… this tells me that the update actually did complete successfully, but for some reason I still boot into 0.4.18.

External storage SD card update service logs
--------------------------------------------
Jun 09 13:00:21 umbrel external storage updater[917]: Creating mempool_web_1     ... done
Jun 09 13:00:22 umbrel external storage updater[917]: Creating btc-rpc-explorer_web_1 ... done
Jun 09 13:00:24 umbrel external storage updater[917]: Creating bluewallet_lndhub_1 ... done
Jun 09 13:00:25 umbrel external storage updater[917]: Creating bitfeed_web_1 ... done
Jun 09 13:00:25 umbrel external storage updater[917]: Umbrel is now accessible at
Jun 09 13:00:25 umbrel external storage updater[917]:   http://umbrel.local
Jun 09 13:00:25 umbrel external storage updater[917]:   http://192.168.50.145
Jun 09 13:00:25 umbrel external storage updater[917]: == End Update Script 01-run.sh ==
Jun 09 13:00:25 umbrel external storage updater[917]: == Begin Update Script 02-run.sh ==
Jun 09 13:00:25 umbrel external storage updater[917]: =======================================
Jun 09 13:00:25 umbrel external storage updater[917]: =============== UPDATE ================
Jun 09 13:00:25 umbrel external storage updater[917]: =======================================
Jun 09 13:00:25 umbrel external storage updater[917]: ========= Stage: Post-update ==========
Jun 09 13:00:25 umbrel external storage updater[917]: =======================================
Jun 09 13:00:25 umbrel external storage updater[917]: == End Update Script 02-run.sh ==
Jun 09 13:00:25 umbrel external storage updater[917]: == Begin Update Script 03-run.sh ==
Jun 09 13:00:26 umbrel external storage updater[917]: =======================================
Jun 09 13:00:26 umbrel external storage updater[917]: =============== UPDATE ================
Jun 09 13:00:26 umbrel external storage updater[917]: =======================================
Jun 09 13:00:26 umbrel external storage updater[917]: =========== Stage: Success ============
Jun 09 13:00:26 umbrel external storage updater[917]: =======================================
Jun 09 13:00:26 umbrel external storage updater[917]: Removing backup
Jun 09 13:00:26 umbrel external storage updater[917]: Successfully installed Umbrel 0.5.0
Jun 09 13:00:26 umbrel external storage updater[917]: == End Update Script 03-run.sh ==
Jun 09 13:00:26 umbrel external storage updater[917]: Deleting cloned repository
Jun 09 13:00:26 umbrel external storage updater[917]: Removing lock
Jun 09 13:00:26 umbrel systemd[1]: Started External Storage SDcard Updater.
Jun 09 13:08:09 umbrel passwd[23722]: pam_unix(passwd:chauthtok): password changed for umbrel
Jun 09 13:12:44 umbrel passwd[31258]: pam_unix(passwd:chauthtok): password changed for umbrel

Any ideas what could be wrong or how to fix?

I’d try reflashing your SD card to 0.5 directly as a first step, seems like it works for some people (I’m actually having the same problem even after reflashing, so I’m seeing what else I can do).

You know what’s really weird?

I just downloaded 0.5.0, flashed it to my SD card, put it back in my Pi and…

0.4.18 still boots. I’m so confused right now!!

edit it gets weirder! I figured why not, let’s try another update via the web UI. It went way quicker than it had any business doing, then without rebooting, my umbrel went straight to the 0.5.0 login page. Now I’m on the latest version.

Strange, but I’ll take it!

Interesting… after re-flashing yesterday and coming back up in 0.4.18 I’m now trying a re-update from the UI…

Let’s see what happens this time…

Nothing.

Node comes back firmly in 0.4.18.

What on earth am I doing wrong!

Well, @jonsyu - I reflashed the SD card to v0.5.0 - after finishing that and putting the SD card back in the Pi, it flashed an error about Docker, and gave me 0.4.18 again. (This confuses me. Is the actual OS on the SSD drive? I guess it must be)

I tried updating from the UI, but that’s given me no joy - still 0.4.18.

The troubleshooting logs start:

Umbrel version
--------------
0.4.18

Flashed OS version
-----------------
v0.5.0

…so clearly my flash must have worked.

The startup service logs include this:

Jun 20 12:02:34 umbrel umbrel startup[5744]: Error: “podcasting20-boosts” is not a valid app

…now, that was an early version of Helipad that both @brianoflondon and I had tried.

The logs also say this:

Jun 20 12:02:24 umbrel external storage updater[999]: == Begin Update Script 03-run.sh ==
Jun 20 12:02:24 umbrel external storage updater[999]: =======================================
Jun 20 12:02:24 umbrel external storage updater[999]: =============== UPDATE ================
Jun 20 12:02:24 umbrel external storage updater[999]: =======================================
Jun 20 12:02:24 umbrel external storage updater[999]: =========== Stage: Success ============
Jun 20 12:02:24 umbrel external storage updater[999]: =======================================
Jun 20 12:02:24 umbrel external storage updater[999]: Removing backup
Jun 20 12:02:25 umbrel external storage updater[999]: Successfully installed Umbrel 0.5.0

… they lie.

What can I try now?

I went to the Umbrel troubleshooting guide and followed the instructions for manually updating the node.

Error: “podcasting20-boosts” not found in app repo
App migration failed, reverting update!

That’s the issue, I think.

After looking about for a while, I discovered a mention of podcasting20-boosts in umbrel/db/user.json which I was able to remove (you need to be sudo to do that).

On rerunning the manual upgrade script, things seemed happier; but it still left me running v0.4.18.

But then I tried hitting the “UPDATE” button in the UI, and it worked this time.

1 Like

Thank you James! I also had the feeling this was a ghost of bad app testing past!

I’ll see if I can dig out the same thing.

update…

umbrel@umbrel:~/umbrel/db $ sudo nano user.json 

and remove the reference to podcasting20-boosts.

I went straight back to the UI and started the upgrade from there and it’s all working!

I did all this and even got this in the log:


== Begin Update Script 03-run.sh ==

=======================================
=============== UPDATE ================

=========== Stage: Success ============

Removing backup
Successfully installed Umbrel v0.5.0
== End Update Script 03-run.sh ==

Deleting cloned repository
Removing lock
Got signal: change-password
karen is getting triggered!

But I’m still not upgraded. Disappointing since I’m on the pre-packaged bitcoinmachines hardware.

1 Like

I had this exact same problem. I noticed during a manual attempt that some files could not be updated:

W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Temporary failure resolving ‘deb.debian.org

W: Failed to fetch http://deb.debian.org/debian-security/dists/buster/updates/InRelease Temporary failure resolving ‘deb.debian.org

W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease Temporary failure resolving ‘deb.debian.org

W: Failed to fetch https://download.docker.com/linux/debian/dists/buster/InRelease Temporary failure resolving ‘download.docker.com

W: Failed to fetch http://archive.raspberrypi.org/debian/dists/buster/InRelease Temporary failure resolving ‘archive.raspberrypi.org

W: Some index files failed to download. They have been ignored, or old ones used instead.

  • sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null

  • sh -c mkdir -p /etc/apt/keyrings && chmod -R 0755 /etc/apt/keyrings

  • sh -c curl -fsSL “https://download.docker.com/linux/debian/gpg” | gpg --dearmor --yes -o /etc/apt/keyrings/docker.gpg

curl: (6) Could not resolve host: download.docker.com

I figured the PiHole DNS set up was the problem, redirected my router to DNS server to 1.1.1.1 and the update via UI worked.