When I try to upgrade OpenWrt on my One, the newly created image seems not to be installed and the router is not rebooted. Please see the log messages:
root@R-Router:~# owut upgrade
ASU-Server https://sysupgrade.openwrt.org
Upstream https://downloads.openwrt.org
Target mediatek/filogic
Profile openwrt_one
Package-arch aarch64_cortex-a53
Version-from 24.10.1 r28597-0425664679 (kernel 6.6.86)
Version-to 24.10.1 r28597-0425664679 (kernel 6.6.86)
34 packages are out-of-date
Request hash:
ce269469d0ceb74cb3dcc7e944e207c5c5c160a214143781f6aa93a7b0450b80
--
Status: queued - 0 ahead of you
Progress: 0s total = 0s in queue + 0s in build
--
Status: init
Progress: 0s total = 0s in queue + 0s in build
--
Status: container_setup
Progress: 2s total = 0s in queue + 2s in build
--
Status: validate_manifest
Progress: 22s total = 0s in queue + 22s in build
--
Status: building_image
Progress: 50s total = 0s in queue + 50s in build
--
Status: done
Progress: 52s total = 0s in queue + 52s in build
Build succeeded in 52s total = 0s in queue + 52s to build:
Image saved : /tmp/firmware.bin
Installing /tmp/firmware.bin and rebooting...
root@R-Router:~#
Even if I run owut upgrade -v --force there is no hint why the installation (probably) and a reboot(definitely) does not happen. Any ideas?
By the way: Attended Sysupgrade works fine as expected.
Something is broken with sysupgrade, does owut check -v say anything about missing default packages? If so, you probably need to add them...
For example, we just went through a round of figuring out that the fitblk package was somehow missing on some mediatek/filogic boxes like yours, and installing magically fixes everything; in fact, just go ahead and opkg install fitblk to be safe.
fitblk is installed and the current output of the owut check -v is here:
root@R-Router:~# owut check -v
owut - OpenWrt Upgrade Tool 2025.04.08~ef2bfb4d-r1 (/usr/bin/owut)
ASU-Server https://sysupgrade.openwrt.org
Upstream https://downloads.openwrt.org
Target mediatek/filogic
Profile openwrt_one
Package-arch aarch64_cortex-a53
Root-FS-type squashfs
Sys-type sysupgrade
Version-from 24.10.1 r28597-0425664679 (kernel 6.6.86)
Version-to 24.10.1 r28597-0425664679 (kernel 6.6.86)
Build-FS-type squashfs
Build-at 2025-04-13T16:38:32Z (~641 hours ago)
Image-prefix openwrt-24.10.1-mediatek-filogic-openwrt_one
Image-URL https://downloads.openwrt.org/releases/24.10.1/targets/mediatek/filogic
Image-file openwrt-24.10.1-mediatek-filogic-openwrt_one-squashfs-sysupgrade.itb
Installed 282 packages
Top-level 85 packages
Default 39 packages
User-installed 53 packages (top-level only)
Package version changes:
airoha-en8811h-firmware 20241110-r1 20241110-r2
eip197-mini-firmware 20241110-r1 20241110-r2
mt7981-wo-firmware 20241110-r1 20241110-r2
3 packages are out-of-date
Default package analysis:
Default Provided-by
nftables nftables-json
There are currently package build failures for 24.10.1 aarch64_cortex-a53:
Feed: base
bpf-headers Fri May 9 04:37:15 2025 - not installed
bridger Fri May 9 05:51:30 2025 - not installed
qosify Fri May 9 06:22:19 2025 - not installed
unetd Fri May 9 06:22:22 2025 - not installed
xdp-tools Fri May 9 05:58:42 2025 - not installed
Feed: telephony
freetdm Fri May 9 09:20:58 2025 - not installed
Failures don't affect this device, details at
https://downloads.openwrt.org/releases/faillogs-24.10/aarch64_cortex-a53/
It is safe to proceed with an upgrade
I suspect there is a difference between the owut script and the script initiated by 'Attended Sysupgrade' after the creation and verification of the new image that causes the problem.
Both simply exec the sysupgrade script in a separate process...
Early on, I looked at using the ubus call rpc-sys upgrade_start in owut, but when I saw it was simply running sysupgrade, I cut out the middle man and ran it directly.