I’ve been working on converting a customized Raspberry Pi OS 12 (bookworm, 32-bit) image using this “Convert your own image” procedure. I’ve been largely successful, but I’m encountering an issue when I try to deploy rootfs-image artifacts.
In short, I can convert an image, write the converted image to a microSD card, and boot a Raspberry Pi 4B exactly as expected. I then create rootfs-image update artifacts with small but obvious changes using mender-artifact following the “Create a Mender Artifact using the snapshot feature” procedure from the docs. I can then upload the artifact to hosted Mender, which appears to create a release as expected. For reference, I am using the following versions in this workflow:
mender-convertversion 4.2.2mender-artifactversion 3.11.2mender-updateversion 4.0.2
When I then try to deploy those images back to the same device (or another device using the same converted image), the deployment always fails with the error:
info: Update Module output (stderr): Input/output error: Reached size of the destination volume, source too big.
I’ve done a bit of experimentation, and I am able to achieve successful deployments if and only if I configure mender-convert to use MENDER_STORAGE_TOTAL_SIZE_MB with a value that is less than or equal to the default value (8192). Unfortunately that’s not a feasible solution for me; to the best of my knowledge, my current “golden image” requires MENDER_STORAGE_TOTAL_SIZE_MB to be greater than 8192.
Has anyone else tried a similar workflow with and have successfully deployed updates when using MENDER_STORAGE_TOTAL_SIZE_MB greater than 8192?