Dear community,
I got the below update note.
I tried to update now 3 times but after the automatic reboot umbrel is still on Version 1.1.
Which logs can I check or is there a way to update through command line?
Thank you in advance!
Exactly same problem here! Tried 6 times. No error message on GUI, reboot shows old version and ad for 1.2.1 pops up again after seconds!
Umbrel is working smoothly until now on a
ESPRIMO Q556/2 i3 8GB/2TB
umbrelOS 1.1.2
Known bug or feature? 
Tnx for advice!
Greets
I have not tried to update yet. For what I have seen before with other upgrades, there are always issues from one version to the other. I am currently on 1.1, for now.
Hey, you can try SSH into your umbrel and execute
- if you are running it on raspberry pi:
sudo mender install https://download.umbrel.com/release/1.2.1/umbrelos-pi.update && sudo reboot
- if you are running it on x86 system:
sudo mender install https://download.umbrel.com/release/1.2.1/umbrelos-amd64.update && sudo reboot
Wait for the system to update and reboot.
Let me know if this helped.
Thanks but same issue after cli update without errors and reboot.
Are you using raspberry pi or x86 platform?
Are you able to access your apps?
Hello Django,
Thank you, Iām on x86 and the provided command doesnāt help. Apps are accessible.
Attachted the output of āsudo mender install https://download.umbrel.com/release/1.2.1/umbrelos-amd64.update && sudo rebootā
output.txt (1.8 KB)
No idea what is the problem.
Maybe try updating to umbrelOS 1.2 first?
x64, after āupdateā itās working smoothly again on 1.1.2 as before. With all apps. Which logs are containing info about update procedure?
I tried updating with an older version and creating a verbose log file, but neither the update was performed nor a log file created.
This is the command I used for V 1.1.2:
sudo mender install https://download.umbrel.com/release/1.1.2/umbrelos-amd64.update --log-file ā/home/*****/tmp/update.logā --log-level verbose && sudo reboot
Here for 1.2.0:
sudo mender install https://github.com/getumbrel/umbrel/releases/download/1.2.0/umbrelos-amd64.update --log-file '/home/****/tmp/update.logā --log-level verbose
you tried to update from 1.1.2 to 1.1.2?
Mit freundlichen GrĆ¼Ćen
Erhard Ducke
If you check my first post my Umbrel version is 1.1 (screenshot) and I tried updating to 1.1.2, 1.2.0 and 1.2.1
Same issue on my Umbrel-Node (x86) brand new installed and synced 1 Week ago!
Umbrel OS 1.1.2
Update via GUI done 6 times with no effect
Update done console after GUI Update not helpful, see below:
after reboot Node is up and run again, the old Version is still (or again) running
Last login: Mon Jun 24 11:53:03 2024 from 192.168.66.145
umbrel@umbrel:~$ cat ^C
umbrel@umbrel:~$ cat /home/umbrel/umbrel/
app-data/ app-stores/ bin/ db/ secrets/ tor/ umbrel.yaml
umbrel@umbrel:~$ cat /home/umbrel/umbrel/umbrel.yaml
version: 1.1.2
apps:
- bitcoin
- electrs
- lightning
- mempool
appRepositories: - GitHub - getumbrel/umbrel-apps: The official app repository of the Umbrel App Store. Submit apps and updates here. Learn how ā https://github.com/getumbrel/umbrel-apps#readme
torEnabled: false
recentlyOpenedApps: - bitcoin
user:
name: ******************
hashedPassword: **********************************
wallpaper: ā6ā
widgets:
umbrel@umbrel:~$ sudo mender install https://download.umbrel.com/release/1.2.1/umbrelos-amd64.update && sudo reboot
[sudo] password for umbrel:
INFO[0000] Loaded configuration file: /var/lib/mender/mender.conf
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
WARN[0000] No server URL(s) specified in mender configuration.
WARN[0000] Server entry 1 has no associated server URL.
INFO[0000] Mender running on partition: /dev/sda3
INFO[0000] Performing remote update from: [https://download.umbrel.com/release/1.2.1/umbrelos-amd64.update].
Installing Artifact of size 1381239808ā¦
INFO[0001] No public key was provided for authenticating the artifact
INFO[0001] Opening device ā/dev/sda2ā for writing
INFO[0001] Native sector size of block device /dev/sda2 is 512 bytes. Mender will write in chunks of 1048576 bytes
ā¦ - 99 %INFO[0212] All bytes were successfully written to the new partition
INFO[0212] The optimized block-device writer wrote a total of 5201 frames, where 0 frames did need to be rewritten (i.e., skipped)
INFO[0212] Wrote 5453303808/5453303808 bytes to the inactive partition
ā¦ - 100 %
INFO[0212] Enabling partition with new image installed to be a boot candidate: 2
Use ācommitā to update, or ārollbackā to roll back the update.
At least one payload requested a reboot of the device it updated.
Broadcast message from root@umbrel on pts/1 (Mon 2024-06-24 12:26:03 UTC):
The system will reboot now!
----------------up & run again------------------
Last login: Mon Jun 24 12:19:24 2024 from 192.168.66.145
umbrel@umbrel:~$ cat /home/umbrel/umbrel/umbrel.yaml
version: 1.1.2
It seems some others are having the same problem and canāt update!
Any help now would be greatly appreciated!
Would downloading the latest Raspberry Pi 4 image from https://download.umbrel.com/release/latest/umbrelos-pi4.img.zip then re-etching the SD card be feasible, just like we all had to do to get from 0.54 to to 1.0 initially?
Tnx but weāre talking about x64 version.
Any issues with updating raspi also?
yes, my Pi 4 wonāt update
Yes, Iām going to learn about start9. Wonder if I can use my blockchain data without a complete new sync.