No, owut is unique among all the ASU clients in supporting that option.
The lantiq/xrx200 devices should be working again within a day or so, two PRs got merged and I'm waiting for the docker images to be generated so I can test them.
The already-built 24.10.1 imagebuilder is never going to be exposed in ASU for the xrx200 target, it is broken for this use and will remain so. Only 24.10.0, 24.10.2, and later, plus the snapshots (both 24.10 and main) will be available.
3 Likes
I made an upgrade to 24.10.1, still not working....
Manual building of image with the requested packages worked (I used for upgrade).
1 Like
@erik-hamburg I think @efahl already said that 24.10.1 wasn't going to "be exposed in ASU". It may be cold comfort to you as it is to me that 24.10.0 now is available.
That said, SNAPSHOT is also not yet working, this after being patient enough to wait for a new build to be published. How can we get this container rebuilt with the right keys?
1 Like
lets hope-wait-and-see 
ATM I'm still running into gpg issue. But nice to see some progress
I'm trying to upgrade an X86-64 build from 24.10.0 to 24.10.1 via attended sysupgrade and get this error towards the bottom.
"Signature check passed.
Pseudo file "dev" exists in source filesystem "/builder/build_dir/target-x86_64_musl/root-x86/dev".
Ignoring, exclude it (-e/-ef) to override.
error: ext4_allocate_best_fit_partial: failed to allocate 10 blocks, out of space?
make[3]: *** [/builder/include/image.mk:399: /builder/build_dir/target-x86_64_musl/linux-x86_64/root.ext4] Error 1
make[2]: *** [Makefile:268: build_image] Error 2
make[1]: *** [Makefile:163: _call_image] Error 2
make: *** [Makefile:337: image] Error 2"
I'm not sure how I could be out of space considering / shows 808 MiB free in Mount Points?
The imagebuilder doesn't know about space on your device, it builds an image with a rootfs that is by default (for the x86 targets) 104MB, so if your packages are such that you exceed that, it can't proceed.
It appears you have resized the rootfs to ~950MB on your device after that initial installation of 24.10.0. Any resizing will be wiped out by LuCI ASU, as it knows nothing about it.
It is likely that your only recourse is to use owut, which has a --rootfs-size ROOTFS_SIZE option, but even that is going to need some extra work on your part the first time you use it (https://openwrt.org/docs/guide-user/installation/sysupgrade.owut#expanding_root_file_system).
The 104MB seemed pretty small so yes I used parted to use the remaining space on the 1GB flash drive that I installed to. I didn't realize that it would still only use 104MB nor did I see anyway to change it when I flashed openwrt-24.10.0-x86-64-generic-ext4-combined-efi.img.gz. Is there some way to increase it now or was there something else I should have done initially before getting it all set up?
Since OpenWrt doesn't have a fancy installer, like desktop Linux, there's no option for specifying partition sizes or the like during installation (and there's really no need for it, since almost all devices have a fixed size flash "hard drive", the partition sizes are literally impossible to change).
But, those of us using SBCs and miniPCs can change it, so we do. The issue with parted is that anything it does is ignored by OpenWrt's sysupgrade, which simply blasts a new img in place overwriting all the partition tables, thus destroying anything you've done using it. Since the default images are all 104MB, that's all you get with defaults, resulting in the situation you're now seeing.
The ASU server can be told to create an image with a larger rootfs partition, but the only ASU client that currently does this is owut, as mentioned above. If you go that route, be sure to read the warnings in the wiki.
So you are saying that I should remove the ASU packages considering it will never work properly and figure out how to use owut from ssh? Would resizing the partition back down and creating a new partition with the extra space & mounting as overlay help?
For whatever reason the partition cannot be shrunken back down to 104MB & gives me a minimum of 140MB. I set it at 256MB. I also decided to try the overlay thing after not hearing back & it did not help.
So I ran the following commands & then tried "owut download" without error but I have a couple more questions. First, the "256" size in the screenshot example would be MiB so it should fit perfectly with the partition size I created or should I change it to a lower value? Second, it mentions adding these commands to the config so you don't always have to repeat them but I see no instructions on where to add them?
Sort of... owut is an ASU client, just the like LuCI ASU app is, they just have different options and internals. So, "Yes, remove LuCI ASU app, install owut instead".
Overlays/other extra partitions on the same disk don't work, as sysupgrade overwrites the partition table upon execution. If you put the data on another drive, then it will work.
But, the easiest thing to do is just install owut, run those commands to set the rootfs to 256 and then do owut upgrade, should work just fine, assuming that your current rootfs size is 256 (but, of course, keep a backup of your config).
You only need to run them once on the command line, they permanently modify the config file and you don't have to use them again unless you want to change the size. You can cat /etc/config/attendedsysupgrade to see where all the options are stored.
1 Like
I got this box upgraded smoothly. Thanks!
2 Likes
This update just failed for my banana pi
{
"url": "https://sysupgrade.openwrt.org",
"branch": "SNAPSHOT",
"revision": "r29347-f09c23fbc9",
"efi": null,
"advanced_mode": "0",
"request_hash": "",
"sha256_unsigned": "",
"client": "luci/25.118.17862~9959134",
"packages": {
"apk-mbedtls": "3.0.0_pre20250208-r2",
"base-files": "1657~f09c23fbc9",
"busybox": "1.37.0-r4",
"ca-bundle": "20241223-r1",
"dnsmasq": "2.91-r1",
"dropbear": "2024.86-r1",
"eip197-mini-firmware": "20250311-r1",
"firewall4": "2025.03.17~b6e51575-r1",
"fitblk": "2",
"fstools": "2024.12.02~49d36ba2-r1",
"fwtool": "2019.11.12~8f7fe925-r1",
"getrandom": "2024.04.26~85f10530-r1",
"hostapd-common": "2025.02.09~c8c7d56a-r1",
"https-dns-proxy": "2025.03.13-r1",
"iwinfo": "2025.02.06~9cec6b4d-r1",
"jansson4": "2.14-r3",
"jshn": "2024.03.29~eb9bcb64-r1",
"jsonfilter": "2025.04.18~8a86fb78-r1",
"kernel": "6.6.87~d1a6137bce5bb1ac19a2c756f358ad0a-r1",
"kmod-crypto-acompress": "6.6.87-r1",
"kmod-crypto-aead": "6.6.87-r1",
"kmod-crypto-authenc": "6.6.87-r1",
"kmod-crypto-crc32c": "6.6.87-r1",
"kmod-crypto-des": "6.6.87-r1",
"kmod-crypto-hash": "6.6.87-r1",
"kmod-crypto-hmac": "6.6.87-r1",
"kmod-crypto-hw-safexcel": "6.6.87-r1",
"kmod-crypto-manager": "6.6.87-r1",
"kmod-crypto-md5": "6.6.87-r1",
"kmod-crypto-null": "6.6.87-r1",
"kmod-crypto-sha1": "6.6.87-r1",
"kmod-crypto-sha256": "6.6.87-r1",
"kmod-crypto-sha512": "6.6.87-r1",
"kmod-gpio-button-hotplug": "6.6.87-r5",
"kmod-hwmon-core": "6.6.87-r1",
"kmod-leds-gpio": "6.6.87-r1",
"kmod-lib-crc-ccitt": "6.6.87-r1",
"kmod-lib-crc32c": "6.6.87-r1",
"kmod-lib-lzo": "6.6.87-r1",
"kmod-libphy": "6.6.87-r1",
"kmod-mt7915e": "6.6.87.2025.04.11~be28ef77-r1",
"kmod-mt7981-firmware": "6.6.87.2025.04.11~be28ef77-r1",
"kmod-nf-conntrack": "6.6.87-r1",
"kmod-nf-conntrack6": "6.6.87-r1",
"kmod-nf-flow": "6.6.87-r1",
"kmod-nf-log": "6.6.87-r1",
"kmod-nf-log6": "6.6.87-r1",
"kmod-nf-nat": "6.6.87-r1",
"kmod-nf-reject": "6.6.87-r1",
"kmod-nf-reject6": "6.6.87-r1",
"kmod-nfnetlink": "6.6.87-r1",
"kmod-nft-core": "6.6.87-r1",
"kmod-nft-fib": "6.6.87-r1",
"kmod-nft-nat": "6.6.87-r1",
"kmod-nft-offload": "6.6.87-r1",
"kmod-phy-airoha-en8811h": "6.6.87-r1",
"kmod-phy-aquantia": "6.6.87-r1",
"kmod-ppp": "6.6.87-r1",
"kmod-pppoe": "6.6.87-r1",
"kmod-pppox": "6.6.87-r1",
"kmod-rtc-pcf8563": "6.6.87-r1",
"kmod-slhc": "6.6.87-r1",
"kmod-usb3": "6.6.87-r1",
"libblobmsg-json20240329": "2024.03.29~eb9bcb64-r1",
"libc": "1.2.5-r4",
"libgcc1": "13.3.0-r4",
"libiwinfo-data": "2025.02.06~9cec6b4d-r1",
"libiwinfo20230701": "2025.02.06~9cec6b4d-r1",
"libjson-c5": "0.18-r1",
"libjson-script20240329": "2024.03.29~eb9bcb64-r1",
"libmbedtls21": "3.6.3-r1",
"libmnl0": "1.0.5-r1",
"libnftnl11": "1.2.8-r1",
"libnl-tiny1": "2025.03.19~c0df580a-r1",
"libubox20240329": "2024.03.29~eb9bcb64-r1",
"libubus20250102": "2025.01.02~afa57cce-r1",
"libuci20250120": "2025.01.20~16ff0bad-r1",
"libuclient20201210": "2024.10.22~88ae8f20-r1",
"libucode20230711": "2025.03.24~b27d70c9-r1",
"libudebug": "2023.12.06~6d3f51f9",
"libustream-mbedtls20201210": "2024.07.28~99bd3d2b-r1",
"logd": "2024.04.26~85f10530-r1",
"luci": "25.118.17862~9959134",
"luci-app-attendedsysupgrade": "25.118.17862~9959134",
"luci-app-https-dns-proxy": "2023.12.26-r4",
"mt7981-wo-firmware": "20250311-r1",
"mtd": "26",
"netifd": "2024.12.17~ea01ed41-r1",
"nftables-json": "1.1.1-r1",
"odhcp6c": "2024.09.25~b6ae9ffa-r1",
"odhcpd-ipv6only": "2024.05.08~a2988231-r1",
"openwrt-keyring": "2024.11.01~fbae29d7-r1",
"ppp": "2.5.2-r1",
"ppp-mod-pppoe": "2.5.2-r1",
"procd": "2025.03.13~891094ae-r1",
"procd-seccomp": "2025.03.13~891094ae-r1",
"procd-ujail": "2025.03.13~891094ae-r1",
"ubi-utils": "2.2.1-r1",
"uboot-envtools": "2025.01-r3",
"ubox": "2024.04.26~85f10530-r1",
"ubus": "2025.01.02~afa57cce-r1",
"ubusd": "2025.01.02~afa57cce-r1",
"uci": "2025.01.20~16ff0bad-r1",
"uclient-fetch": "2024.10.22~88ae8f20-r1",
"ucode": "2025.03.24~b27d70c9-r1",
"ucode-mod-fs": "2025.03.24~b27d70c9-r1",
"ucode-mod-nl80211": "2025.03.24~b27d70c9-r1",
"ucode-mod-rtnl": "2025.03.24~b27d70c9-r1",
"ucode-mod-ubus": "2025.03.24~b27d70c9-r1",
"ucode-mod-uci": "2025.03.24~b27d70c9-r1",
"ucode-mod-uloop": "2025.03.24~b27d70c9-r1",
"urandom-seed": "3",
"urngd": "2023.11.01~44365eb1-r1",
"usign": "2020.05.23~f1f65026-r1",
"wpad-basic-mbedtls": "2025.02.09~c8c7d56a-r1",
"zlib": "1.3.1-r1"
},
"profile": "openwrt,one",
"target": "mediatek/filogic",
"version": "SNAPSHOT",
"diff_packages": true,
"filesystem": "squashfs"
}
STDERR:
Generate local signing keys...
WARNING: can't open config file: /builder/shared-workdir/build/staging_dir/host/etc/ssl/openssl.cnf
WARNING: can't open config file: /builder/shared-workdir/build/staging_dir/host/etc/ssl/openssl.cnf
read EC key
writing EC key
WARNING: opening /builder/packages/packages.adb: No such file or directory
Package list missing or not up-to-date, generating it.
Building package index...
ERROR: unable to select packages:
libblobmsg-json20240329 (no such package):
required by: world[libblobmsg-json20240329]
libjson-script20240329 (no such package):
required by: world[libjson-script20240329]
libubox20240329 (no such package):
required by: world[libubox20240329]
make[2]: *** [Makefile:226: package_install] Error 3
make[1]: *** [Makefile:167: _call_manifest] Error 2
make: *** [Makefile:344: manifest] Error 2
Make sure you have Advanced Mode enabled, and "uninstall" those packages on the New firmware upgrade available page before you submit the build request.
(This is the ABI-versioned package name issue due to incomplete implementation of apk, you will see this again and again in main snapshots, until apk support is completed.)
Well I found another thread where it was mentioned to uninstall those packages, but I uninstalled them from the actual package manager and broke the whole system in the process. Like, can't even log in with SSH broken.
Right now the farthest it gets when it boots is the red LED on the left slow blinks. I'm trying to figure out how to do the recovery from USB.