I can't upgrade to 1.3

Support and Troubleshooting
42

Yes, for Rpi4/RPi5 could be working. But on amd64 version returns a Payload error:

umbrel@umbrel:~$ sudo mender install https://download.umbrel.com/release/1.3.0/umbrelos-amd64.update && sudo system reboot --spare
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/sdb2       
INFO[0000] Performing remote update from: [https://download.umbrel.com/release/1.3.0/umbrelos-amd64.update]. 
Installing Artifact of size 1391746560...
INFO[0002] No public key was provided for authenticating the artifact 
WARN[0002] 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[0002] Download failed: Payload: can not install Payload: rootfs.img: Active root partition matches neither RootfsPartA nor RootfsPartB. 
ERRO[0002] Payload: can not install Payload: rootfs.img: Active root partition matches neither RootfsPartA nor RootfsPartB.

Any idea @nmfretz ?

43

Having trouble updating my 2022 Raspberry Pi “Bitcoin Machine” to Umbrel 1.0 or a later version. I think I have a Pi 4, but I’m not sure; it’s a 2T SSD machine. I followed the instructions to download the latest software (umbrelos-pi4.img.zip), used balanaEtcher to flash the zip file onto the Umbrel’s microSD card, re-inserted the card, and plugged all the cables back in. After 30 minutes, the Umbrel display screen remains blank (light gray), and I can’t access it by using umbrel.local or the IP address that’s associated with the Umbrel on my home network although the Umbrel is listed as a device on that network. I was updating from the OS that came with the machine, which I think was 0.5. I I don’t know what to do. Have read a lot of postings here but still stuck as I am not that experienced. I ran sudo fdisk -1 in Terminal on my iMac and got this:
[192-168-68-52:~] DDN% sudo fdisk -1
Password:
fdisk: illegal option – 1
usage: fdisk [-ieu] [-f mbrboot] [-c cyl -h head -s sect] [-S size] [-r] [-a style] disk
-i: initialize disk with new MBR
-u: update MBR code, preserve partition table
-e: edit MBRs on disk interactively
-f: specify non-standard MBR template
-chs: specify disk geometry
-S: specify disk size
-r: read partition specs from stdin (implies -i)
-a: auto-partition with the given style
-d: dump partition table
-y: don’t ask any questions
-t: test if disk is partitioned
`disk’ is of the form /dev/rdisk0.
auto-partition styles:
boothfs 8Mb boot plus HFS+ root partition (default)
hfs Entire disk as one HFS+ partition
dos Entire disk as one DOS partition
raid Entire disk as one 0xAC partition
[192-168-68-52:~] DDN%

I will much appreciate any help you can provide!

44

I installed umbrel 1.3.0 few days ago on my RPi 5 with 8GB and a 2TB SSD NVme, No SD
Blockchain in fully synced and now electrs tries to sync too.
But since day one I have several freezes over the day. The web UI is not reachable nor SSH, but I can ping the pi.
When I repower the pi I checked the journal and saw this.

Dec 20 00:14:13 umbrel mender[344]: time="2024-12-19T23:14:13Z" level=error msg="Failed to authorize with \"\": failed to build authorization request: failed to obtain authorization message data: failed to obtain identity data: failed to call /usr/share/mender/identity/mender-device-identity: fork/exec /usr/share/mender/identity/mender-device-identity: no such file or directory"
Dec 20 00:14:13 umbrel mender[344]: time="2024-12-19T23:14:13Z" level=warning msg="Reauthorization failed with error: transient error: authorization request failed"
Dec 20 00:14:13 umbrel mender[344]: time="2024-12-19T23:14:13Z" level=error msg="Failed to submit inventory data: transient error: authorization request failed"
Dec 20 00:14:13 umbrel mender[344]: time="2024-12-19T23:14:13Z" level=error msg="inventory submit failed: transient error: authorization request failed"
Dec 20 00:14:13 umbrel mender[344]: time="2024-12-19T23:14:13Z" level=warning msg="Failed to refresh inventory: failed to submit inventory data: inventory submit failed: transient error: authorization request failed"
Dec 20 00:14:13 umbrel mender[344]: time="2024-12-19T23:14:13Z" level=error msg="Failed to authorize with \"\": failed to build authorization request: failed to obtain authorization message data: failed to obtain identity data: failed to call /usr/share/mender/identity/mender-device-identity: fork/exec /usr/share/mender/identity/mender-device-identity: no such file or directory"
Dec 20 00:14:13 umbrel mender[344]: time="2024-12-19T23:14:13Z" level=warning msg="Reauthorization failed with error: transient error: authorization request failed"
Dec 20 00:14:13 umbrel mender[344]: time="2024-12-19T23:14:13Z" level=error msg="Failed to submit inventory data: transient error: authorization request failed"
Dec 20 00:14:13 umbrel mender[344]: time="2024-12-19T23:14:13Z" level=error msg="inventory submit failed: transient error: authorization request failed"
Dec 20 00:14:13 umbrel mender[344]: time="2024-12-19T23:14:13Z" level=warning msg="Failed to refresh inventory: failed to submit inventory data: inventory submit failed: transient error: authorization request failed"

So I tried this command
sudo mender install https://download.umbrel.com/release/1.3.0/umbrelos-pi.update && sudo rugpi-ctrl system reboot --spare
as recommended here and saw this:

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         
INFO[0000] Performing remote update from: [https://download.umbrel.com/release/1.3.0/umbrelos-pi.update]. 
Installing Artifact of size 1122937856...
INFO[0001] No public key was provided for authenticating the artifact 
INFO[0001] Output (stdout) from command "/usr/share/mender/modules/v3/rugpi-image": Hot partition is already the default! 
INFO[0002] Output (stdout) from command "/usr/share/mender/modules/v3/rugpi-image": Copying partitions... 
INFO[0002] Output (stdout) from command "/usr/share/mender/modules/v3/rugpi-image": Found 0,CONFIG kind: 0x0c, start: 8192, size: 524288 
INFO[0003] Output (stdout) from command "/usr/share/mender/modules/v3/rugpi-image": Found 1,BOOT-A kind: 0x0c, start: 532480, size: 262144

And here some investigations:

fdisk 
umbrel@umbrel:~$ sudo fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: CT2000P3PSSD8
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xaa887561

Device         Boot    Start        End    Sectors  Size Id Type
/dev/nvme0n1p1          8192     532479     524288  256M  c W95 FAT32 (LBA)
/dev/nvme0n1p2        532480     794623     262144  128M  c W95 FAT32 (LBA)
/dev/nvme0n1p3        794624    1056767     262144  128M  c W95 FAT32 (LBA)
/dev/nvme0n1p4       1056768 3907029167 3905972400  1.8T  5 Extended
/dev/nvme0n1p5       1064960   11550719   10485760    5G 83 Linux
/dev/nvme0n1p6      11558912   22044671   10485760    5G 83 Linux
/dev/nvme0n1p7      22052864 3907029167 3884976304  1.8T 83 Linux
df- h 
Filesystem      Size  Used Avail Use% Mounted on
overlay         1.8T  768G  963G  45% /
tmp             4.0G  9.0M  4.0G   1% /run
/dev/nvme0n1p7  1.8T  768G  963G  45% /run/rugpi/mounts/data
/dev/nvme0n1p5  3.3G  2.9G  230M  93% /run/rugpi/mounts/system
/dev/nvme0n1p1  256M   12K  256M   1% /run/rugpi/mounts/config
/dev/nvme0n1p2  128M   89M   40M  70% /boot
devtmpfs        4.0M     0  4.0M   0% /dev
tmpfs           4.0G     0  4.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           806M     0  806M   0% /run/user/1000
sudo du -h /run/rugpi/mounts/system | sort -rh | head -20 
2.9G    /run/rugpi/mounts/system
2.1G    /run/rugpi/mounts/system/usr
845M    /run/rugpi/mounts/system/usr/lib
659M    /run/rugpi/mounts/system/images
536M    /run/rugpi/mounts/system/usr/share
498M    /run/rugpi/mounts/system/usr/lib/aarch64-linux-gnu
395M    /run/rugpi/mounts/system/usr/bin
147M    /run/rugpi/mounts/system/usr/share/nodejs
140M    /run/rugpi/mounts/system/usr/libexec
137M    /run/rugpi/mounts/system/usr/libexec/docker
136M    /run/rugpi/mounts/system/usr/share/locale
136M    /run/rugpi/mounts/system/usr/libexec/docker/cli-plugins
102M    /run/rugpi/mounts/system/usr/lib/gcc/aarch64-linux-gnu/12
102M    /run/rugpi/mounts/system/usr/lib/gcc/aarch64-linux-gnu
102M    /run/rugpi/mounts/system/usr/lib/gcc
94M     /run/rugpi/mounts/system/usr/local/lib/node_modules/umbreld
94M     /run/rugpi/mounts/system/usr/local/lib/node_modules
94M     /run/rugpi/mounts/system/usr/local/lib
94M     /run/rugpi/mounts/system/usr/local
86M     /run/rugpi/mounts/system/usr/share/doc
45

Hello all,
I just wanted to let you know that I was able to solve the issues I saw with updating to 1.3. The root cause was my USB cable which led to transfer-speeds between my USB-Harddrive and the Raspberry Pi 5 of ~ 23 MB/sec. After replacing it with a distinct short USB cable the speed went up to > 200MB/sec, everything started to sync (reindex) properly again and now after 2 weeks, my umbrel node is synced 100% and every app in umbrel is running very fast and I’m on 1.3.

Kind Regards
Paddy