Same is happening for me. I have a raspberry pi 4 4gb and a raspberry pi 4 8gb. Both running umbrel on 1.1.
Both “update” to 1.2.1 without error and after rebooting are still on 1.1.
This seems to be a serious issue!
1 Like
Following advices I’m trying to update to 1.1.2 first and then to 1.2.1, OK?
It’s running on a x86 device.
I’ve tried that and appears the message as follows:
sudo mender install https://download.umbrel.com/release/1.1.2/umbrelos-amd64.update && sudo reboot
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/nvme0n1p2
INFO[0000] Performing remote update from: [https://download.umbrel.com/release/1.1.2/umbrelos-amd64.update].
Installing Artifact of size 1382419968…
INFO[0001] No public key was provided for authenticating the artifact
WARN[0001] Returning artifact name from /etc/mender/artifact_info file. This is a fallback, in case the information can not be retrieved from the database, and is only expected when an update has never been installed before.
ERRO[0001] could not get the current Artifact name
ERRO[0001] artifact name is empty
I’ve tried to put the name of the update in thefile but didn’t worked:
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/nvme0n1p2
INFO[0000] Performing remote update from: [https://download.umbrel.com/release/1.1.2/umbrelos-amd64.update].
Installing Artifact of size 1382419968…
INFO[0001] No public key was provided for authenticating the artifact
WARN[0001] Returning artifact name from /etc/mender/artifact_info file. This is a fallback, in case the information can not be retrieved from the database, and is only expected when an update has never been installed before.
ERRO[0001] Broken device manifest file: ([umbrelos-amd64.update])
ERRO[0001] could not get the current Artifact name
ERRO[0001] Broken device manifest file: ([umbrelos-amd64.update])
Seems that I need to know what to put in this file to run the update.
Someone can respond with the data and format of this file?
Yes you can. Just putting the data of blockchain in the right folders.
Thanks Sir, you know dir name of blockchain on umbrel?
I did this once and worked for me.
/umbrel/app-data/bitcoin/data/bitcoin has some folders as ‘blocks’ and ‘chainstate’ that has many files. SO, after copy, try to paste everything under /umbrel/app-data/bitcoin/data/bitcoin of the origin in the same place of the destiny. This saves 2 days of download maybe 3. Good luck.
Thank you!
I’ve finally discovered the problem: The script fails in executing this command and creates this problem. Just copy paste this command and execute it in terminal:
echo “artifact_name=umbrelOS” > /etc/mender/artifact_info
then try to update. 
Hiya @atomzenitram thanks for looking into this really appreciate it!
The fix you mention should be automatically applied by umbrelOS during update. The update process runs this script which should create that file with the same contents if it doesn’t already exist: umbrel/scripts/update-script at 570acdabcab13ac237fba992f491d126fff30810 · getumbrel/umbrel · GitHub
Where there any other steps you took? Do you remember which version you initially installed so I can try to recreate the issue?
1 Like
Ah @atomzenitram just reading through your messages above I see you were trying to update with mender cli directly instead of through the umbrelOS OTA update process.
Was there a reason you weren’t updating from the UI? That should automatically apply the fix among other things. It’s not recommended to directly interact with the mender CLI.
1 Like
Hi @lukechilds, first I was in 0.5.4 and updated to 1.1.1 what was really cool and soft.
Then I was trying to install any update from 1.1.1 and wasn’t possible by normal ways.
Initially I didn’t tried all the updates because I’ve thought that some were only for RPi equipments, so 1.1.2 was not updated via normal ways just because didn’t worked. I thought was ok. Then I’ve figured out that the 1.2.1 is needed and to not loose the sequence I’ve tried and couldn’t do it. So I’ve began to look for log messages and forum to understand. Finally I’ve had to touch the file to create it (arctifact_info) then the log stop warning the lack of the file but warned about the content of it. Finally I’ve tried that solution because I’ve seen that in the log of the script and catched that the script tried but couldn’t do it . So I did it manually and then could update. I’ve tried via cli the 1.1.2 and the 1.2.1 updates because couldn’t update at first via OTA and the command saved me the day.NO I’ve just updated from 1.2.1 to 1.2.2beta1 and 1.2.2 via OTA and it’s all fine.
Big thank u! Works for me 
To install the latest update you only need one command
sudo mender install https://download.umbrel.com/release/1.2.2/umbrelos-pi.update && sudo reboot
1 Like
If the update won’t install, check for bad blocks on your MicroSD card. That was the issue for me.
(Discord)
1 Like
1.2.2. Also not working, tried both ui and cli mender
2 Likes
try to post the error message or log messages for us to try understand what is going on.
I tried both too and it didn’t work.
time=“2024-08-09T08:52:21Z” level=info msg=“Loaded configuration file: /var/lib/mender/mender.conf”
time=“2024-08-09T08:52:21Z” level=info msg=“‘UpdateControlMapExpirationTimeSeconds’ is not set in the Mender configuration file. Falling back to the default of 2*UpdatePollIntervalSeconds”
time=“2024-08-09T08:52:21Z” level=info msg=“‘UpdateControlMapBootExpirationTimeSeconds’ is not set in the Mender configuration file. Falling back to the default of 600 seconds”
time=“2024-08-09T08:52:21Z” level=warning msg=“No server URL(s) specified in mender configuration.”
time=“2024-08-09T08:52:21Z” level=warning msg=“Server entry 1 has no associated server URL.”
time=“2024-08-09T08:52:21Z” level=info msg=“Mender running on partition: /dev/nvme0n1p2”
time=“2024-08-09T08:52:21Z” level=info msg=“Performing remote update from: [https://download.umbrel.com/release/1.2.2/umbrelos-amd64.update].”
time=“2024-08-09T08:52:23Z” level=info msg=“No public key was provided for authenticating the artifact”
time=“2024-08-09T08:52:23Z” level=info msg=“Opening device "/dev/nvme0n1p3" for writing”
time=“2024-08-09T08:52:23Z” level=info msg=“Native sector size of block device /dev/nvme0n1p3 is 512 bytes. Mender will write in chunks of 1048576 bytes”
time=“2024-08-09T08:53:59Z” level=info msg=“All bytes were successfully written to the new partition”
time=“2024-08-09T08:53:59Z” level=info msg=“The optimized block-device writer wrote a total of 5211 frames, where 0 frames did need to be rewritten (i.e., skipped)”
time=“2024-08-09T08:53:59Z” level=info msg=“Wrote 5463287808/5463287808 bytes to the inactive partition”
time=“2024-08-09T08:53:59Z” level=info msg=“Enabling partition with new image installed to be a boot candidate: 3”
try Linux’s logs here.
Which logs specifically?
Thanks this worked for me
1 Like