Attended sysupgrade - allow user to select rootfs size in some way

[numnums]

Hello,

I notice in the 22.03.4 release notes, that we now have:

[38ccc47] imagebuilder: allow to specific ROOTFS_PARTSIZE

Is it at all possible to make this an option within Attended sysupgrade, that a user can adjust?

My use case is using the x86 build of OpenWRT on PC Engines APU2D4. Every time I upgrade, I then have to connect my USB to serial port cable to my router, connect with screen or putty, boot into a Live Linux distribution from USB flash drive, install parted, resize the rootfs partition to use all of the SSD, and then extend the filesystem onto that now larger partition.

It would be nice to reduce the number of steps, work, and time in a upgrade.

Thank you for considering this.

[frollic]

Not if you'd have two parallel installs, install new release from old, resize, and boot into new.
Alternate between them on every new release.

Sysupgrade help for x86_64

So, I was playing with my APU1, and thought I'd try it myself ... The starting point is a SD card with a snapshot image written, and I added an additional 21.02.01 to the same SD card, then rebooted into 21.02.01. This is all done from the already running snapshot version note: with the default size of /dev/sda1, you will only be able to fit three kernels. you'll need: opkg install resize2fs fdisk blkid create new partition for the new openwrt version, I used 250MB. fdisk /dev/sda Comman…

Once you have the partitions in place, there are just three commands + the change in grub (which would be only default boot option, if you use static kernel names, and partitions as root= parameter in grub, instead of PARTUUID).

[numnums]

So make it an advance opt in feature? Only use this if you know exactly what you are doing?

Or, only available for x86 image builds?

Now that this function is available in imagebuilder, and you are telling me this change is not possible because of routers with two parallel installs...

Is your intention of this feature not being made available in Attended sysupgrade to protect users from either bricking their device, or no longer having parallel installs on the flash?

If so, what is to stop a user from using this feature in imagebuilder on a device that has two parallel installs? Does this brick the device, or just make it that it only has one install of OpenWRT on it?

My point being, if any user that knows about this feature can access it through imagebuilder. Then they can potentially screw up their flash layout, parallel installs, or brick the device depending on what happens in this circumstance.

You can't completely protect the user from making potentially fatal mistakes in general, or once a feature like this is made available. Educate and inform them of the dangers of using it. Make it opt in, and maybe not super obvious as an option, or difficult to enable without reading the warning?

What do you think about this?

[popywrt]

Hey guys.
my nanoPI R4S also has more GB sd card.
The default rootfs size is 104 MB which is quite low for such device.
I am also upgrading to the the newest stable with attended sysupgrade.
It would be nice to 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.

[spence]

I think ASU is being replaced by owut, a new upgrade tool, and is available in OpenWrt v24.10. owut has the ability to specify the root filesystem size as well as many other great features.
See this post for a start for information gathering:

Owut: OpenWrt Upgrade Tool

Here's some details on what I think are interesting features: The --init-script option allows you to specify a uci-defaults script, just like Firmware Selector does with its 'Script to run on first boot (uci-defaults)' input field. LuCI Attended Sysupgrade sort of does this by looking for /rom/etc/uci-defaults/99-asu-defaults and relaying that implicitly, but it doesn't allow you to delete or change what's already there. owut makes this explicit, if you want the script included in your new im…

Look through more of that topic etc for more info.
A link to the openwrt doc wiki page for owut is in the first post of that topic/thread.