9. Frequently Asked Questions¶
9.1. Why doesn’t the installed system use the whole partition?¶
The filesystem image installed via RAUC was probably created for a size smaller than the partition on the target device.
Especially in cases where the same bundle will be installed on devices which use different partition sizes, tar archives are preferable to filesystem images. When RAUC installs from a tar archive, it will first create a new filesystem on the target partition, allowing use of the full size.
9.2. Is it possible to use RAUC without D-Bus (Client/Server mode)?¶
Yes. If you compile RAUC using the
--disable-service configure option, you
will be able to compile RAUC without service mode and without D-Bus support:
Then every call of the command line tool will be executed directly rather than being forwarded to the RAUC service process running on your machine.
9.3. Why does RAUC not have an ext2 / ext3 file type?¶
ext4 is the successor of ext3. There is no advantage in using ext3 over ext4.
Some people still tend to select ext2 when they want a file system without journaling. This is not necessary, as one can turn off journaling in ext4, either during creation:
mkfs.ext4 -O ^has_journal
or later with:
tune2fs -O ^has_journal
Note that even if there is only an ext4 slot type available, potentially each file system mountable as ext4 should work (with the filename suffix adapted).
9.4. Is the RAUC bundle format forwards/backwards compatible?¶
The basic bundle format has not changed so far (squashfs containing images and the manifest, with a CMS signature), which means that newer versions can install old bundles. Going forward, any issue with installing old bundles would be considered a bug.
Newer RAUC versions have added features and slot types, though (such as casync, eMMC boot partitions, MBR/GPT partition switching). If you use those features, older versions of RAUC that cannot handle them will refuse to install the bundle. As long as you don’t use new features, our intention is that bundles created by newer versions will be installable by older versions.
There are ideas of introducing a new bundle format to allow streaming installation (over the network), but we won’t remove support for the original format.
If there are ever reasons that require an incompatible change, you can use a two step migration: You can use an intermediate update to ship a new RAUC binary in a bundle created by the old (compatible) version. Then use the newly installed RAUC binary for the real update.
9.5. Can I use RAUC with a dm-verity-protected partition?¶
Yes you can, as the offline-generated dm-verity hash tree is simply part of
the image that RAUC writes to the partition.
To ensure RAUC does not corrupt the partition by executing hooks or writing
slot status information, use
type=raw in the respective slot config and
use a global (see slot status file) on a separate
non-redundant partition with setting
9.6. What causes a payload size that is not a multiple of 4kiB?¶
RAUC versions up to 1.4 had an issue in the casync bundle signature generation, which caused two signatures to be appended. While the squashfs payload size is a multiple of 4kiB, the end of the first signature was not aligned. As RAUC uses the second (“outer”) signature during verification, this didn’t cause problems. RAUC 1.5 fixed the casync bundle generation and added stricter checks, which rejected the older bundles. In RAUC 1.5.1, this was reduced to a notification message.
To avoid the message, you can recreate the bundle with RAUC 1.5 and newer.