System update to 2643 from 2310 kills web ui on HC4 Odroid

Platform
1

Hello,
Trying to update from 2310 to 2643 and although the update finishes succesfully and my apps work (grocy, paperless) the web ui eventually breaks and shows system error. Files app also has/had an issue even before the update

Pasting some logs but it looks like backend, API and Authelia services break.

root@syncloud:~# strace /snap/platform/2643/bin/backend 2>&1 | tail -20
execve(“/snap/platform/2643/bin/backend”, [“/snap/platform/2643/bin/backend”], 0xffffe060c670 /* 15 vars */) = -1 EFAULT (Bad address)
+++ killed by SIGSEGV +++
—
root@syncloud:~# ldd /snap/platform/2310/bin/backend
not a dynamic executable

root@syncloud:~# ldd /snap/platform/2643/bin/backend
ldd: exited with unknown exit code (135)
—
root@syncloud:~# snap services platform
Service Startup Current Notes
platform.api enabled inactive -
platform.authelia enabled inactive -
platform.backend enabled inactive -
platform.login enabled active -
platform.nginx-custom-proxy enabled active -
platform.nginx-public enabled active -
platform.openldap enabled active -

root@syncloud:~# snap services nextcloud
Service Startup Current Notes
nextcloud.nats enabled active -
nextcloud.nginx enabled active -
nextcloud.php-fpm enabled active -
nextcloud.postgresql enabled active -
nextcloud.redis enabled active -
nextcloud.signaling enabled active -

root@syncloud:~# snap services paperless
Service Startup Current Notes
paperless.celery enabled active -
paperless.celery-beat enabled active -
paperless.consumer enabled active -
paperless.gunicorn enabled active -
paperless.postgresql enabled active -
paperless.redis enabled active -

Files broken
root@syncloud:~# snap services files
Service Startup Current Notes
files.nginx enabled inactive -
files.uwsgi enabled active -

Current versions (until platform rolls back again)
root@syncloud:~# snap list
Name Version Rev Tracking Publisher Notes
files 170 170 latest/stable syncloud✓ -
grocy 128 128 latest/stable syncloud✓ -
nextcloud 898 898 latest/stable syncloud✓ -
openvpn 256 256 latest/stable syncloud✓ -
paperless 116 116 latest/stable syncloud✓ -
platform 2643 2643 latest/stable syncloud✓ base
users 299 299 latest/stable syncloud✓ -

Initialize device account-key assertion fail

Whats also worth a mention is that i’ve done this update twice before but it seems to rollback by what looks like a “Initialize device” request fail.

root@syncloud:~# snap changes | tail -20
ID Status Spawn Ready Summary
91 Error 2025-06-26 today at 18:59 UTC Initialize device
92 Error today at 19:04 UTC today at 19:04 UTC Initialize device
93 Error today at 19:19 UTC today at 19:19 UTC Initialize device
94 Error today at 19:44 UTC today at 19:44 UTC Initialize device

root@syncloud:~# snap tasks 91
Status Spawn Ready Summary
Done 2025-06-26 today at 18:59 UTC Generate device key
Error 2025-06-26 today at 18:59 UTC Request device serial

…
Request device serial

2026-04-09T18:59:58Z ERROR cannot add “account-key” assertion with primary key clashing with a trusted assertion: [hIedp1AvrWlcDI4uS_qjoFLzjKl5enu4G2FYJpgB3Pj-tUzGlTQBxMBsBmi-tnJR]
—

2

Let me check, I will get back to you.

3

Could you check kernel version please?

uname -a
4

If that is below 5 you need to use the latest image.

5

Hello Boris,
Just did and it’s > 5

root@syncloud:~# uname -a
Linux syncloud 5.11.0-odroid-arm64 #1 SMP PREEMPT Debian 5.11.1-202102250221~buster (2021-02-24) aarch64 GNU/Linux

6

I have the same HC4 with the same kernel (5.11.0-odroid-arm64) and platform 2643, and everything works fine on my box. So this is not a general Go/kernel incompatibility.

Could you run these commands and share the output? It will help narrow down the issue:

  1. Check if the binary file is intact (compare size and checksum):
ls -la /snap/platform/2643/bin/backend
sha256sum /snap/platform/2643/bin/backend
  1. Check disk space:
df -h
  1. Check snap and snapd versions:
snap version
  1. Full snap changes history:
snap changes
  1. Check if the binary runs at all:
/snap/platform/2643/bin/backend -h
  1. Check dmesg for any kernel errors when the backend crashes:
dmesg | tail -30
7

Ran them and here they are:

Binary file

root@syncloud:~# ls -la /snap/platform/2643/bin/backend
sha256sum /snap/platform/2643/bin/backend
-rwxr-xr-x 1 root root 23806828 Apr  6 09:34 /snap/platform/2643/bin/backend
sha256sum: /snap/platform/2643/bin/backend: Input/output error

Disk space

root@syncloud:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.5G     0  1.5G   0% /dev
tmpfs           371M  828K  370M   1% /run
/dev/mmcblk0p2   60G  7.7G   50G  14% /
tmpfs           1.9G  2.1M  1.9G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/loop0       96M   96M     0 100% /snap/files/170
/dev/loop1      218M  218M     0 100% /snap/grocy/128
/dev/loop2      586M  586M     0 100% /snap/nextcloud/896
/dev/loop3      586M  586M     0 100% /snap/nextcloud/898
/dev/loop4       71M   71M     0 100% /snap/openvpn/256
/dev/loop5      713M  713M     0 100% /snap/paperless/116
/dev/loop6      424M  424M     0 100% /snap/paperless/99
/dev/loop7      170M  170M     0 100% /snap/platform/2310
/dev/loop9      173M  173M     0 100% /snap/users/299
/dev/sda        112G  106M  112G   1% /opt/disk/external
/dev/loop11     182M  182M     0 100% /snap/platform/2643

Snap version

root@syncloud:~# snap version
snap    639
snapd   639
series  16
debian  12
kernel  5.11.0-odroid-arm64

Snap changes history

root@syncloud:~# snap changes
ID   Status  Spawn                   Ready                   Summary
91   Error   2025-06-26              yesterday at 21:40 UTC  Initialize device
92   Error   yesterday at 21:45 UTC  yesterday at 21:45 UTC  Initialize device
93   Error   yesterday at 21:59 UTC  yesterday at 21:59 UTC  Initialize device
94   Error   yesterday at 22:24 UTC  yesterday at 22:24 UTC  Initialize device
95   Error   yesterday at 23:04 UTC  yesterday at 23:04 UTC  Initialize device
96   Error   yesterday at 23:54 UTC  today at 00:14 UTC      Auto-refresh snaps "grocy", "paperless", "platform"
97   Error   today at 00:24 UTC      today at 00:24 UTC      Initialize device
98   Error   today at 03:09 UTC      today at 03:09 UTC      Initialize device
99   Error   today at 08:29 UTC      today at 08:29 UTC      Initialize device

Binary run check

root@syncloud:~# /snap/platform/2643/bin/backend -h
Segmentation fault

Kernel errors

root@syncloud:~# dmesg | tail -30
[53651.914611] SQUASHFS error: Unable to read data cache entry [1f7ee18]
[53651.916008] SQUASHFS error: Unable to read page, block 1f7ee18, size 11524
[53651.917402] SQUASHFS error: Unable to read data cache entry [1f7ee18]
[53651.918791] SQUASHFS error: Unable to read page, block 1f7ee18, size 11524
[53651.920224] SQUASHFS error: Unable to read data cache entry [1f7ee18]
[53651.921629] SQUASHFS error: Unable to read page, block 1f7ee18, size 11524
[53651.923021] SQUASHFS error: Unable to read data cache entry [1f7ee18]
[53651.924423] SQUASHFS error: Unable to read page, block 1f7ee18, size 11524
[53651.925803] SQUASHFS error: Unable to read data cache entry [1f7ee18]
[53651.927171] SQUASHFS error: Unable to read page, block 1f7ee18, size 11524
[53651.928538] SQUASHFS error: Unable to read data cache entry [1f7ee18]
[53651.929892] SQUASHFS error: Unable to read page, block 1f7ee18, size 11524
[53651.931288] SQUASHFS error: Unable to read data cache entry [1f7ee18]
[53651.932647] SQUASHFS error: Unable to read page, block 1f7ee18, size 11524
[53652.335334] SQUASHFS error: Unable to read fragment cache entry [38bf69c]
[53652.336726] SQUASHFS error: Unable to read page, block 38bf69c, size 376c
[53662.586003] SQUASHFS error: Unable to read fragment cache entry [38bf69c]
[53662.587442] SQUASHFS error: Unable to read page, block 38bf69c, size 376c
[53672.839000] SQUASHFS error: Unable to read fragment cache entry [38bf69c]
[53672.840397] SQUASHFS error: Unable to read page, block 38bf69c, size 376c
[53683.081170] SQUASHFS error: Unable to read fragment cache entry [38bf69c]
[53683.082589] SQUASHFS error: Unable to read page, block 38bf69c, size 376c
[53693.331891] SQUASHFS error: Unable to read fragment cache entry [38bf69c]
[53693.333292] SQUASHFS error: Unable to read page, block 38bf69c, size 376c
[53703.583647] SQUASHFS error: Unable to read fragment cache entry [38bf69c]
[53703.585050] SQUASHFS error: Unable to read page, block 38bf69c, size 376c
[53713.833082] SQUASHFS error: Unable to read fragment cache entry [38bf69c]
[53713.834484] SQUASHFS error: Unable to read page, block 38bf69c, size 376c
[53724.081419] SQUASHFS error: Unable to read fragment cache entry [38bf69c]
[53724.082826] SQUASHFS error: Unable to read page, block 38bf69c, size 376c
8

SQUASHFS error: Unable to read data cache entry [1f7ee18]
This means SD card is dead, can you get a new one and flash a new image from here?

9

Guess I’ll have to. I’ll see if I’ll do with another SD card or maybe another SSD in the other slot since I have to image and flash : ). Thanks!