I can't upgrade to 1.3

Support and Troubleshooting
22

in first time, thanks for your time and attention
in my case i use:

  1. Pi 4
  2. usb disk and microSD
  3. umbrel 1.2.2 to 1.3.0

after run sudo fidisk -l this is the answer show the sistem

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Disk /dev/mmcblk0: 59.69 GiB, 64088965120 bytes, 125173760 sectors
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: 0x9d03f99f

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 532479 524288 256M c W95 FAT32 (LBA)
/dev/mmcblk0p2 532480 794623 262144 128M c W95 FAT32 (LBA)
/dev/mmcblk0p3 794624 1056767 262144 128M c W95 FAT32 (LBA)
/dev/mmcblk0p4 1056768 125173759 124116992 59.2G 5 Extended
/dev/mmcblk0p5 1064960 11550719 10485760 5G 83 Linux
/dev/mmcblk0p6 11558912 22044671 10485760 5G 83 Linux
/dev/mmcblk0p7 22052864 125173759 103120896 49.2G 83 Linux

Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Generic
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: gpt
Disk identifier: A1BF549D-2C0B-40C7-938F-76D1829BD3DC

Device Start End Sectors Size Type
/dev/sda1 2048 3907028991 3907026944 1.8T Linux filesystem

many thanks again !!!

23

same problem with a pi 4

is pi 4 still suported? in the SO download section only talks no about pi 5

24
  1. Pi 5 (8 GB Ram)
  2. usb 3.1 SSD (2TB)
  3. umbrel 1.2.2 to 1.3.0

after run sudo fidisk -l this is the answer show the sistem

umbrel@umbrel:~$ sudo fdisk -l
[sudo] password for umbrel:
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/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: XS1000
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: 0xd4719102

Device Boot Start End Sectors Size Id Type
/dev/sda1 8192 532479 524288 256M c W95 FAT32 (LBA)
/dev/sda2 532480 794623 262144 128M c W95 FAT32 (LBA)
/dev/sda3 794624 1056767 262144 128M c W95 FAT32 (LBA)
/dev/sda4 1056768 3907029167 3905972400 1.8T 5 Extended
/dev/sda5 1064960 11550719 10485760 5G 83 Linux
/dev/sda6 11558912 22044671 10485760 5G 83 Linux
/dev/sda7 22052864 3907029167 3884976304 1.8T 83 Linux

many thanks again !!!

25

Thanks everyone. If you are on a Raspberry Pi can you please go to Settings > Advanced settings > Terminal > umbrelOS and run the following command to attempt updating to 1.3.0:

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

Please make sure to copy and paste the entire command exactly.

If you have previously run something like sudo apt update && sudo apt upgrade -y, this ends up breaking the update process.

2 Likes
26

i try it second :smiley:

27

—!!!THANK YOU!!!—

fresh restart, then your command line, i get this.

umbrel@umbrel:~$ sudo mender install https://download.umbrel.com/release/1.3.0/umbrelos-pi.update && sudo rugpi-ctrl system reboot --spare
[sudo] password for umbrel:
INFO[0000] Loaded configuration file: /etc/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
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[0001] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Copying partitions…
INFO[0001] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Found 0,CONFIG kind: 0x0c, start: 8192, size: 524288
INFO[0002] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Found 1,BOOT-A kind: 0x0c, start: 532480, size: 262144
… - 7 %INFO[0005] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Found 2,BOOT-B kind: 0x0c, start: 794624, size: 262144
INFO[0006] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Found 3,system-a kind: 0x83, start: 1064960, size: 7143136
… - 100 %
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/2 (Thu 2024-12-05 11:41:58 UTC):

The system will reboot now!

and after a couple of seconds, it restarts… i thought it woud not restart.

THANK YOU!!! it worked :smiley:

28

Thank you. The command provided by you helped and RPI5 upgraded to Umbrel OS 1.3 successfully.

29

Okay, got a rpi4 that is experiencing the same issue:

  1. I start the update.
  2. I watch the progress bar.
  3. As the progress bar reaches the end, I see a couple of buttons on the screen for a fraction of a second, and then I’m brought back to the login screen before I can even do anything.
  4. I login and find I’m still running 1.2.2, and I’m told there’s an update available.
  5. I reboot and find I’m still running 1.2.2, and I’m told there’s an update available.

Looking through the forum, I found the instructions about how to bring up a terminal and enter the following command:

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

After entering the command, everything seemed to be going okay until the following happened:

INFO[0038] Output (stdout) from command "/usr/share/mender/modules/v3/rugpi-image": Found 3,system-a kind: 0x83, start: 1064960, size: 7143136 
.............................................................  -  99 %ERRO[0497] Download failed: Unable to open /var/lib/mender/modules/v3/payloads/0000/tree/stream-next: open /var/lib/mender/modules/v3/payloads/0000/tree/stream-next: no such file or directory 
INFO[0497] Could not access /var/lib/mender/modules/v3/payloads/0000/tree, assuming cleanup already done: stat /var/lib/mender/modules/v3/payloads/0000/tree: no such file or directory 
ERRO[0497] Unable to open /var/lib/mender/modules/v3/payloads/0000/tree/stream-next: open /var/lib/mender/modules/v3/payloads/0000/tree/stream-next: no such file or directory

I looked into /var/lib/mender/modules/v3/payloads/0000/ and sure enough there’s nothing other than . and .. in there.

I then did an fdisk -l and saw no errors and got the following summary at the end:

Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
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: 0xa2fecfe6

Device         Boot    Start      End  Sectors  Size Id Type
/dev/mmcblk0p1          8192   532479   524288  256M  c W95 FAT32 (LBA)
/dev/mmcblk0p2        532480   794623   262144  128M  c W95 FAT32 (LBA)
/dev/mmcblk0p3        794624  1056767   262144  128M  c W95 FAT32 (LBA)
/dev/mmcblk0p4       1056768 62333951 61277184 29.2G  5 Extended
/dev/mmcblk0p5       1064960 11550719 10485760    5G 83 Linux
/dev/mmcblk0p6      11558912 22044671 10485760    5G 83 Linux
/dev/mmcblk0p7      22052864 62333951 40281088 19.2G 83 Linux


Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: 500SSD1         
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: gpt
Disk identifier: 0EB9FA04-1F84-40C4-81DE-6BDB7B6A8594

Device     Start        End    Sectors  Size Type
/dev/sda1   2048 3907028991 3907026944  1.8T Linux filesystem

I’m open to any suggestions about how to proceed from here…

30

great!!!
updated and working at 100%
excellent solution
thanks for your time, attention and valuable help

31

Hi there,

After having ignored it for months, I just checked in and upgraded to 1.2.1? then 1.2.2 and then tried 1.3, but that kept failing. I found this thread and tried your command above “sudo mender install https://download.umbrel.com/release/1.3.0/umbrelos-pi.update && sudo rugpi-ctrl system reboot --spare” That resulted in what I thought was an upgrade but when it came back up, I am still on 1.2.2

Might you have any thoughts on what I’ve done wrong? This is a RPi4 with a USB SSD. TY, Kelly

32

If you are on a Raspberry Pi can you please go to Settings > Advanced settings > Terminal > umbrelOS

you made this ???

33

Hi there,

in my case I’m on Rasp 5 with 1TB Samsung USB SSD connected.

Since I’ve upgraded to 1.3, I’m not able to start the Apps properly for the first 30 Minutes and then the system is somehow crashed and not reachable anymore also via SSH. I’ve then performed the commands what was recommended here, but it doesn’t seem to help.

The weird thing is, that I can’t see the new feature with Cloudflare on the WebUI Settings anymore, which I once saw. When I then trying to start applications like “Bitcoin Node” or try to update “Lightning Node” it’s just hanging there forever until roughly 30 Minutes after the restart and then the WebUI nor the SSH is reachable anymore. Any ideas what else I could do? I did run a mender update back to 1.2 (downgrade) which also went fine but then I have exactly the same behavior.

umbrel@umbrel:~$ sudo fdisk -l
[sudo] password for umbrel:
Sorry, try again.
[sudo] password for umbrel:
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/mmcblk0: 29.81 GiB, 32010928128 bytes, 62521344 sectors
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: 0xe165fb0b

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 532479 524288 256M c W95 FAT32 (LBA)
/dev/mmcblk0p2 532480 794623 262144 128M c W95 FAT32 (LBA)
/dev/mmcblk0p3 794624 1056767 262144 128M c W95 FAT32 (LBA)
/dev/mmcblk0p4 1056768 62521343 61464576 29.3G 5 Extended
/dev/mmcblk0p5 1064960 11550719 10485760 5G 83 Linux
/dev/mmcblk0p6 11558912 22044671 10485760 5G 83 Linux
/dev/mmcblk0p7 22052864 62521343 40468480 19.3G 83 Linux

Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Portable SSD T5
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: F48C7D20-C111-45CA-B5DE-64ADDA68C7AA

Device Start End Sectors Size Type
/dev/sda1 2048 1953523711 1953521664 931.5G Linux filesystem
umbrel@umbrel:~$ sudo mender install https://download.umbrel.com/release/1.3.0/umbrelos-pi.update && sudo rugpi-ctrl system reboot --spare
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[0008] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Hot partition is already the default!
INFO[0008] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Copying partitions…
INFO[0008] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Found 0,CONFIG kind: 0x0c, start: 8192, size: 524288
INFO[0008] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Found 1,BOOT-A kind: 0x0c, start: 532480, size: 262144
… - 7 %INFO[0031] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Found 2,BOOT-B kind: 0x0c, start: 794624, size: 262144
INFO[0031] Output (stdout) from command “/usr/share/mender/modules/v3/rugpi-image”: Found 3,system-a kind: 0x83, start: 1064960, size: 7143136
… - 100 %
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 (Sat 2024-12-07 08:01:35 UTC):

The system will reboot now!

2024-12-07_09-10-24_Umbrel_WebUI
2024-12-07_09-10-24_Umbrel_WebUI1200×902 236 KB

34

Hi there, I’m using a x64 running an Umbrel 1.2.2 amd64 with the same issue at update. Now, the dashboard shows “Failed to update”, Error: “Update failed”.

The Umbrel is installed in my internal 256GB SSD (sda), but I restored and I’m storing data in a nvme 2TB (sdb).

Could be the issue this reason? sudo mender install https://github.com/getumbrel/umbrel/releases/download/1.3.0/umbrelos-amd64.update failed returning the following error:

Payload: can not install Payload: rootfs.img: Active root partition matches neither RootfsPartA nor RootfsPartB.
35

follow the instructions provided by nmfretz. for many of us it was the correct solution (raspi 4 and 5 users). you can check it out in this thread. good luck!!!

36

I posted in this thread earlier:

What are my options at this point? Am I looking at a “pull the SD card and reflash” situation, or is there another way to get myself to 1.3?

37

Did you try the solution proposed in this thread by nmfretz? It solved the problem for me and other users?

Thanks everyone. If you are on a Raspberry Pi can you please go to Settings > Advanced settings > Terminal > umbrelOS and run the following command to attempt updating to 1.3.0:

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

Please make sure to copy and paste the entire command exactly.

If you have previously run something like sudo apt update && sudo apt upgrade -y, this ends up breaking the update process.

38

I did indeed, unfortunately.

I’ve never used apt, so whatever happened, it’s looking like there’ll be a reinstall under my Christmas tree. Thanks for trying to help!

39

What command line would be for a not Pi umbrelOS? Just for an amd64 version? Thank you.

1 Like
40

Having the same problem on amd64 and would also be grateful for any help.

41

our solution was provided by nmfretz Nate Fretz, write him… he is a genius, he provided the solution to us rasp users.