I can't upgrade to 1.3

Support and Troubleshooting
1

i try 3 times and don’t upgrade to 1.3, after uploading screen, log… and stay 1.2.2
i have a raspberry pi 4

Captura
Captura1278×458 16.5 KB

Captura1
Captura11059×306 27.7 KB

2

Have you tried via SSH?

3

no… only via web…
this night when i come back to home… i try…
any place to read intructions about ssh instalation ?
thank for relply !!!

4

The command for the Raspberry Pi is:

sudo mender install https://download.umbrel.com/release/1.3.0/umbrelos-pi.update && sudo reboot

And for amd64 architectures like the Umbrel Home:

sudo mender install https://download.umbrel.com/release/1.3.0/umbrelos-amd64.update && sudo reboot

1 Like
5

Good d… nothing works

6

after upgrade ??

7

No the update to 1.3
4-5 hours troubleshoting🤯
Im not good with linux but
Something is wrong with the program: mender

Im stuck on 1.2.2 (i think hardstuck):face_with_spiral_eyes:

8

Hey denny, kennst du dich mit linux aus?
Kann ich dir später bitte ein paar Fehlermeldungen zukommen lassen?

9

The error indicates that the ~/umbrel/scripts/version script or directory does not exist. This might have been caused by incomplete extraction or an improper update.

Ich konnte das script (thing/ ding) wieder herstellen

Dann error error error

Ich konnte alles fixen

Nur das es dann wieder von vorne losging

8 mal😵‍💫

10

This error also appears when I use:
sudo apt full-upgrade
and packages remain unupgraded

11

I fixed this so many times but something bring this back

12

Any place where I can read to fix the error when updating with “sudo apt full-upgrade”
I’m not very good with Linux

13

i use the command… and stay on 1.2.2

2024-11-27-21-23-15-589
2024-11-27-21-23-15-5891920×1208 235 KB

14

I have exactly the same issues described above. I tried to run the “sudo mender install https://download.umbrel.com/release/1.3.0/umbrelos-pi.update” command only without the reboot and then I ran command “sudo mender show-artifact” and this was the result:

umbrel@umbrel:~/umbrel$ sudo mender show-artifact
WARN[0000] No server URL(s) specified in mender configuration.
WARN[0000] Server entry 1 has no associated server URL.
768fa82-1732537058

Then I tried command “sudo mender commit” but it did not work as well. Here is the result:

INFO[0000] 'UpdateControlMapExpirationTimeSeconds' is not set in the Mender configuration file. Falling back to the default of 2*UpdatePollIntervalSeconds
INFO[0000] 'UpdateControlMapBootExpirationTimeSeconds' is not set in the Mender configuration file. Falling back to the default of 600 seconds
INFO[0000] No configuration files present. Using defaults
WARN[0000] No server URL(s) specified in mender configuration.
WARN[0000] Server entry 1 has no associated server URL.
INFO[0000] No dual rootfs configuration present
Committing Artifact...
INFO[0000] Output (stdout) from command "/usr/share/mender/modules/v3/rugpi-image": Hot partition is already the default!

So, I wonder how this can work for somebody?

15

Same issue here. I’ve tried the command:

sudo mender install https://download.umbrel.com/release/1.3.0/umbrelos-pi.update && sudo reboot

it downloads the file. Runs through mender ops but on the reboot still 1.2.2. Also tried through the UI obviously and it failed. Trying to not have to do a full install. It should upgrade right? Is there anything that would fail the mender command?

16

I think the only thing left for us to do is wait for the Umbrel team to offer a solution to this problem.

17

Agreed. Thanks. :crossed_fingers:

18

your are welcome !!! :hugs:

20

Hey All, sorry for the frustration. From the commands posted here it looks like you are all on Raspberry Pi’s. Unfortunately we aren’t able to recreate this issue on our Pi’s, and the issue does not look to be widespread so it is difficult to ascertain what the problem is.

Can anyone that makes their way here with this issue please let us know:

  1. The device you are using (Pi 4, Pi 5)

  2. Your configuration:
    i. Storage device: USB hard-drive or NVMe
    ii. OS install/boot method: are you booting from a microSD card or directly from your USB/NVMe

  3. The umbrelOS version you are on and what version you are attempting to update to
    (e.g., 1.2.2 → 1.3.0)

  4. The output of the following command:

    sudo fdisk -l

    You can run this in Settings > Advanced Settings > Terminal > umbrelOS. If you are prompted for a password, use the password for your umbrelOS dashboard. The password won’t show up as you type it in for security reasons. Just type it in and press ‘Enter’.

  5. Before updating, did you at any point run any Linux system/package upgrade commands like
    sudo apt update && sudo apt upgrade -y. These could potentially put umbrelOS in a state that it cannot update.

Thanks!

21

Also, just a couple clarifications for users that make their way here, since manual troubleshooting is a confusing business.

^ The mender logs mention this, but there is no need to run sudo mender commit. umbrelOS automatically commits on boot.

^ Upgrading linux packages could have unintended consequences where you put umbrelOS in a state where it cannot perform the upgrade successfully since you will be updating packages away from specific versions that the update process might rely on.

What happens here is that umbrelOS has an A/B partitioning system for software updates where if any issue is detected when it tries to boot into the new OS version (e.g. 1.3.0) it can safely abort and reboot into the pre-update version (e.g., 1.2.2), which is what is happening here for some reason. The idea is that a failed update will not brick your umbrel and instead you’ll just stay on your pre-update umbrelOS version. The tricky bit now is to figure out why a small number of Pi updates are failing.