Help mender-convert'ing a Mekotronics Armbian image

General Discussions
, ,
1

R58X-4G - Mekotronics
Image

I’m attempting to leverage mender-convert to create a base image for my client devices:

MENDER_ARTIFACT_NAME=release-1 ./docker-mender-convert --disk-image input/Armbian_23.08.0_Meko-r58x-4g_jammy_5.10.160_gnome_v1.3.1.img --overlay input/rootfs_overlay_production/
using log file at: /home/mschmidt/workspace/mender-convert/logs/convert.log.1697640619-282
Running mender-convert --disk-image input/Armbian_23.08.0_Meko-r58x-4g_jammy_5.10.160_gnome_v1.3.1.img --overlay input/rootfs_overlay_production/
Running mender-convert-extract: --config ./work/override_compression_config --disk-image input/Armbian_23.08.0_Meko-r58x-4g_jammy_5.10.160_gnome_v1.3.1.img --overlay input/rootfs_overlay_production/
2023-10-18 14:50:20 [INFO] [mender-convert-extract] Using configuration file: configs/mender_convert_config
2023-10-18 14:50:20 [INFO] [mender-convert-extract] Using configuration file: ./work/override_compression_config
2023-10-18 14:50:20 [INFO] [mender-convert-extract] Validating disk image
2023-10-18 14:50:20 [INFO] [mender-convert-extract] Disk parsed successfully
2023-10-18 14:50:20 [INFO] [mender-convert-extract] NUMBER OF PARTS: 2 TYPE: gpt
2023-10-18 14:50:20 [INFO] [mender-convert-extract] PART 1: SIZE: 256M TYPE: bc13c2ff-59e6-4262-a352-b275fd6f7172
2023-10-18 14:50:20 [INFO] [mender-convert-extract] PART 1: extracting to work/part-1.fs
2023-10-18 14:50:21 [INFO] [mender-convert-extract] PART 2: SIZE: 4.9G TYPE: 0fc63daf-8483-4772-8e79-3d69d8477de4
2023-10-18 14:50:21 [INFO] [mender-convert-extract] PART 2: extracting to work/part-2.fs
2023-10-18 14:50:34 [INFO] [mender-convert-extract] Extracting boot gap to work/boot-gap.bin
mender-convert-extract has finished. Cleaning up...
Running mender-convert-modify: --config ./work/override_compression_config --disk-image input/Armbian_23.08.0_Meko-r58x-4g_jammy_5.10.160_gnome_v1.3.1.img --overlay input/rootfs_overlay_production/
2023-10-18 14:50:34 [INFO] [mender-convert-modify] Using configuration file: configs/mender_convert_config
2023-10-18 14:50:34 [INFO] [mender-convert-modify] Using configuration file: ./work/override_compression_config
mount: /mender-convert/work/rootfs: unknown filesystem type 'crypto_LUKS'.
mender-convert-modify has finished. Cleaning up...
umount: work/rootfs: not mounted.
2023-10-18 14:50:34 [ERROR] [mender-convert] mender-convert failed
2023-10-18 14:50:34 [DEBUG] [mender-convert-extract] When running: (modules/disk.sh:63): run_and_log_cmd():

        dd if=input/Armbian_23.08.0_Meko-r58x-4g_jammy_5.10.160_gnome_v1.3.1.img of=work/boot-gap.bin skip=1b bs=1M count=32767b status=none iflag=count_bytes,skip_bytes
2023-10-18 14:50:34 [INFO] [mender-convert-modify] Using configuration file: configs/mender_convert_config
2023-10-18 14:50:34 [INFO] [mender-convert-modify] Using configuration file: ./work/override_compression_config
2023-10-18 14:50:34 [ERROR] [mender-convert] mender-convert failed
2023-10-18 14:50:34 [ERROR] [mender-convert] mender-convert exit code: 32
Log file available at: /home/mschmidt/workspace/mender-convert/logs/convert.log.1697640619-282

Can anyone help me troubleshoot this/have any ideas? Thanks.

2

Hi @michael.schmidt,

Thanks for getting in touch! Two things immediately hit me:

  1. which mender-convert configuration are you using? As it needs to inject a modified bootloader, it has to know which and where to get it. The board is not one that I have seen before, and generic support probably won’t work on Rockchip based stuff.
  2. The error unknown filesystem type 'crypto_LUKS' sounds like either the partition types are off, or the image uses LUKS at some point. This is probably the prime error why the process falls over, as it is not supported per se.

Greetz,
Josef