Oh, wait, I may have misunderstood you. So you have originally flashed the image generated with Image Builder with CONFIG_TARGET_ROOTFS_PARTSIZE=1024 parameter and you're trying to run asu on that?
Can you not use the image builder again to generate the new image?
rootfs_size_mb integer
example: 100
maximum: 100
minimum: 1
Ability to specify a custom CONFIG_TARGET_ROOTFS_PARTSIZE for the resulting image. Attaching this optional parameter will cause ImageBuilder to build a rootfs with that size in MB.
Is there any reason, why the 100mb limit on the asu servers for ext4 builds are not increased at least a bit to 200 or 300mb, just to give some breathing room ? I know it can be used to ddos the build server if using squashfs due to the compression cpu cost. However for ext4 it does not matter much.
Bump!
Please allow the user to select the rootfs size on attended sysupgrade.
It could also pre select the calculated maxium size from the available space as default.