Attended SysUpgrade Error

Installing and Using OpenWrt
1

I tried to use the attended sysupgrade feature today for the first time, which didn't work. The error seems to indicate a lack of disk space? Is there a RootFS size limit on the build server?

Package list missing or not up-to-date, generating it.

Building package index...
Downloading https://downloads.openwrt.org/releases/22.03.5/targets/x86/64/packages/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker1/cache/22.03.5/x86/64/build_dir/target-x86_64_musl/root-x86/../../../../../../../../../../../home/aparcar/asu/worker1/cache/22.03.5/x86/64/dl/openwrt_core
Downloading https://downloads.openwrt.org/releases/22.03.5/targets/x86/64/packages/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/22.03.5/packages/x86_64/base/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker1/cache/22.03.5/x86/64/build_dir/target-x86_64_musl/root-x86/../../../../../../../../../../../home/aparcar/asu/worker1/cache/22.03.5/x86/64/dl/openwrt_base
Downloading https://downloads.openwrt.org/releases/22.03.5/packages/x86_64/base/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/22.03.5/packages/x86_64/luci/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker1/cache/22.03.5/x86/64/build_dir/target-x86_64_musl/root-x86/../../../../../../../../../../../home/aparcar/asu/worker1/cache/22.03.5/x86/64/dl/openwrt_luci
Downloading https://downloads.openwrt.org/releases/22.03.5/packages/x86_64/luci/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/22.03.5/packages/x86_64/packages/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker1/cache/22.03.5/x86/64/build_dir/target-x86_64_musl/root-x86/../../../../../../../../../../../home/aparcar/asu/worker1/cache/22.03.5/x86/64/dl/openwrt_packages
Downloading https://downloads.openwrt.org/releases/22.03.5/packages/x86_64/packages/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/22.03.5/packages/x86_64/routing/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker1/cache/22.03.5/x86/64/build_dir/target-x86_64_musl/root-x86/../../../../../../../../../../../home/aparcar/asu/worker1/cache/22.03.5/x86/64/dl/openwrt_routing
Downloading https://downloads.openwrt.org/releases/22.03.5/packages/x86_64/routing/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/22.03.5/packages/x86_64/telephony/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker1/cache/22.03.5/x86/64/build_dir/target-x86_64_musl/root-x86/../../../../../../../../../../../home/aparcar/asu/worker1/cache/22.03.5/x86/64/dl/openwrt_telephony
Downloading https://downloads.openwrt.org/releases/22.03.5/packages/x86_64/telephony/Packages.sig
Signature check passed.
Downloading file:packages/Packages
Updated list of available packages in /home/aparcar/asu/worker1/cache/22.03.5/x86/64/build_dir/target-x86_64_musl/root-x86/../../../../../../../../../../../home/aparcar/asu/worker1/cache/22.03.5/x86/64/dl/imagebuilder
Downloading file:packages/Packages.sig
Signature check failed.
Remove wrong Signature file.
error: ext4_allocate_best_fit_partial: failed to allocate 1 blocks, out of space?
make[3]: *** [/home/aparcar/asu/worker1/cache/22.03.5/x86/64/include/image.mk:335: /home/aparcar/asu/worker1/cache/22.03.5/x86/64/build_dir/target-x86_64_musl/linux-x86_64/root.ext4] Error 1
make[2]: *** [Makefile:189: build_image] Error 2
make[1]: *** [Makefile:127: _call_image] Error 2
make: *** [Makefile:243: image] Error 2
2

yes, the default is ~100MB.

3

Is there a way to change this? Or is any larger RootFS size completely unsupported?

4

yes, if you use it "offline", and build on your own system.

5

OK, so deploy the ASU server locally? Is there a Wiki/Guide for this?

6

note, there's (or at least was) a bug in the builder, the rootfs size env variable wasn't honored, there's a workaround posted for it though ...

7

Perhaps we are talking cross-purposes. I was specifically asking about the ASU (Attended System Upgrade) server. I've used the image builder locally before but was hoping to automate this process using ASU, however the OpenWRT hosted server seems to have an image size limit.

The instructions for running your own ASU server are pretty sparse (and if followed line for line, don't even work).

8

I see ...

But I also don't see the point of using the ASU, if you're already building your own image?
Simply add the packages you want, during the build process ?

9

I'm at a point now where all the packages I need have finally been merged into the release packages, but there are still some kmods that I need to be installed as part of the image (otherwise networking doesn't work for example) so I can't simply use the release sysupgrade images. So I'm looking for a way to automate the upgrade process so I can do it routinely and keep up with the minor releases.

Unless you can enlighten me, the image builder process is still pretty manual, requiring several steps to pull the existing package list, then parse this into a format that Image Builder can take, manually altering the config file for the RootFS size, building, then uploading back to the running OpenWRT.

10

if you need 100+MB of packages, then you're probably right.

I'm guessing this is an x86, or something similar ?

11

Yes, x86 ext4. I size my image for 1GB but only actually use about 180MB. I suppose I could go on an aggressive package removal hunt to get this down to 100MB but it would be difficult for sure.

12

I use dual installs, since it makes my life easier, and lets me modify the next release
before I actually start using it. Also makes it easy to roll back.

1 Like
13

A great 'half-way' solution would be if the Attended Sys Upgrade UI could output a script to bootstrap the image builder locally, instead of only being able to call the ASU hosted API.

1 Like