Description This module performs a full root filesystem updates on the device. The module was originally developed for testing purposes and it is published as a non-official alternative way of doing rootfs updates on devices with dual partition layout (A/B). It supports rollback in the same way as …

hmm, this is confusing: what is the difference from using mender-artifact write rootfs-image? mender-artifact write module-image -h says that “This command is not meant to be used directly, but should rather be wrapped by an update module build command”

The former command creates a normal rootfs update, the latter creates an update meant for an update module. Since update modules are generic plugins, there is no one command that can be recommended. Instead the update module should come with its own artifact build command which uses the module-image …

Hello @lluiscampos . I followed this document to get the full system update and I came to the end. But when I run the last command, I get an answer like this: root@ubuntu:/home/robust2# ARTIFACT_NAME=“full-update-1.0” root@ubuntu:/home/robust2# DEVICE_TYPE=“imx6ul-var-dart” root@ubuntu:/home/ro…

Hello again @mEK , This Update Module requires a full filesystem image. If you have full Mender integration in your device (namely A/B filesystems), you can generate update images for your device the same way you created the first image: using Yocto project or mender-convert . Then, once you have …

Thank you for your quick and clear answer. First of all, what are the steps I need to follow for full mender integration? Where do you think I should start? Is meta-mender not enough to create an A / B root file system?

But how have you installed Mender in your device? Your logs hint that you are using an NXP imx6 based board, so maybe you have followed a Board integration tutorial here on Mender Hub? If so, you have already yocto environment ready to create new images :slight_smile:

@lluiscampos @kacf I think there is an issue here with the current version of the U-boot utils on the Dunfell branch. Passing the variables into fw_setenv -s - seems to require the syntax var=value rather than var value. Interestingly the var value syntax seems to work directly from the command li…

Yes, but I believe the client already does this. Check out this commit , and then this later followup . The command line is a bit different, because var and value are parsed by the shell, not by the command, and I believe it accepts this. Grub has always used the = variant. What problem are you seei…

Oh, never mind, I missed the context, this is about rootfs-image-v2. And I’ve seen your pull request . Then you’re right, this needs fixing. We are testing the rootfs-image-v2 module, but only using Grub, which seems to support both.

Is is possible to construct the artifact such that it updates the rootfs-image.version value? Right now, it’s setting rootfs-image.rootfs-image-v2.version. I’ve monkeyed around with different combinations of --software-filesystem and --software-name to no avail.

Root Filesystem Image v2

Update Modules

Topic		Replies	Views
Rootfs with explicit version check Update Modules	2	1932	May 19, 2024
Using update module as a rootfs-image General Discussions	5	1187	March 9, 2021
Robust delta update rootfs Update Modules	13	10218	December 11, 2025
Problem with rootfs update with *.mender General Discussions	18	1732	August 10, 2021
Mender-artifact creation to update some files General Discussions	15	1521	April 11, 2019

Root Filesystem Image v2

Related topics