[sysupgrade] possible with snapshots or bug?

[anon27813507]

deployed on SSD

{"kernel":"5.4.43","hostname":"OpenWrt","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"OpenWrt","version":"SNAPSHOT","revision":"r13518-c37487a63d","target":"mvebu/cortexa9","description":"OpenWrt SNAPSHOT r13518-c37487a63d"}}

---

The verbose log

Image check failed but --force given - will update anyway!
Saving config files...
etc/config/chrony
etc/config/dhcp
etc/config/dropbear
etc/config/firewall
etc/config/fstab
etc/config/htpdate
etc/config/luci
etc/config/network
etc/config/rpcd
etc/config/system
etc/config/ubootenv
etc/config/ucitrack
etc/config/uhttpd
etc/config/unbound
etc/config/wireless
etc/dropbear/dropbear_rsa_host_key
etc/fw_env.config
etc/group
etc/hosts
etc/inittab
etc/luci-uploads/.placeholder
etc/opkg/keys/0b26f36ae0f4106d
etc/opkg/keys/1035ac73cc4e59e3
etc/opkg/keys/5151f69420c3f508
etc/opkg/keys/72a57f2191b211e0
etc/opkg/keys/792d9d9b39f180dc
etc/opkg/keys/9ef4694208102c43
etc/opkg/keys/b2d571e0880ff617
etc/opkg/keys/b5043e70f9a75cde
etc/opkg/keys/c10b9afab19ee428
etc/opkg/keys/dace9d4df16896bf
etc/opkg/keys/dd6de0d06bbd3d85
etc/opkg/keys/f94b9dd6febac963
etc/passwd
etc/profile
etc/profile.d/sys_bashrc.sh
etc/rc.local
etc/shadow
etc/shells
etc/shinit
etc/sysctl.conf
Commencing upgrade. Closing all shell sessions.

node reboots but then the same package that been on display for upgrade prior to the sysupgrade has not been upgraded and still shows after the reboot

opkg list-upgradable

base-files - 222-r13518-c37487a63d - 222-r13520-68b94f0fb4

Or maybe a misconception on my part that sysupgrade between snapshots does not work and require a fresh install each time?

[anon27813507]

Looks like just a timing matter, although the upgrade image file been populated after the package file it seems that it did not include the updated package yet.

Will give it another go tomorrow

[anon27813507]

No, not a timing matter, the sysupgrade is just not applied/happening. Anyway to debug this?

[anon27813507]

With the valuable input from @jow figured that with the deviation from OpenWrt's setup:

• MBR with two partitions, 1 x vFAT for /boot mount that also carries the boot flag and the other partition ext4 for the root mount

vs.

• PTR with a single partition and no boot flag

sysupgrade fails as the script is looking for /dev -type b and subsequently fails.

Either would have to find a way to patch /lib/upgrade/common.sh or have to forgo sysupgrade and manually upgrade.