# Mender-convert **URL:** \ **Category:** General Discussions\ **Created:** [August 19, 2025, 7:27pm UTC](https://hub.mender.io/t/mender-convert/7966 "2025-08-19T19:27:18Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![hackenstein](https://avatars.discourse-cdn.com/v4/letter/h/c37758/32.png) [@hackenstein](https://hub.mender.io/u/hackenstein)\ **Post date:** [August 19, 2025, 7:27pm UTC](https://hub.mender.io/t/mender-convert/7966/1 "2025-08-19T19:27:18Z")
Finally got mender-convert to run against the full image I captured. It produced .cfg, .ext4, .img and .mender. Can’t apply .mender because device is not mender converted. Don’t know what .cfg and .ext4 are for and when I apply the .img it runs out of space and fails. Why does it produce an image that takes up more space than the drive it’s converting contains? I don’t understand why mender-convert outputs an artifact file when it applies to an image of a device that can’t install an artifact. Any assistance anyone can provide would be greatly appreciated. Regards, Keith ---
**Author:** ![hackenstein](https://avatars.discourse-cdn.com/v4/letter/h/c37758/32.png) [@hackenstein](https://hub.mender.io/u/hackenstein)\ **Post date:** [August 20, 2025, 12:17pm UTC](https://hub.mender.io/t/mender-convert/7966/2 "2025-08-20T12:17:37Z")
Update: MENDER\_STORAGE\_TOTAL\_SIZE\_MB=250000 for 250gb drive. changed to 230000. Fits now but when booting Gave up waiting for suspend/resume device Gave up wating for root file system device. Common Problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough)? - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/nvme0n12 does not exist. Dropping to a shell! It seems mender-convert has not laid out the drive partitions correctly. BusyBox v1.35.0 (Debian 1:1.35.0-4+b4) build-in shell (ash) Enter ‘help’ for a list of build-in commands. (initramfs) & flashing cursor. ---
**Author:** ![hackenstein](https://avatars.discourse-cdn.com/v4/letter/h/c37758/32.png) [@hackenstein](https://hub.mender.io/u/hackenstein)\ **Post date:** [August 20, 2025, 2:40pm UTC](https://hub.mender.io/t/mender-convert/7966/3 "2025-08-20T14:40:17Z")
Did some digging with AI and found settings to try in config file and rebuilt. BOOT\_DEVICE=“/dev/nvme0n1p1” ROOTFS\_PART\_A=“/dev/nvme0n1p2” ROOTFS\_PART\_B=“/dev/nvme0n1p3” DATA\_PART=“/dev/nvme0n1p4” Hopeful but no luck so took them back out and also removed: MENDER\_STORAGE\_DEVICE\_BASE=/dev/nvme0n1 Now error is: /dev/mmcblk0p2 does not exist. ---
**Author:** ![hackenstein](https://avatars.discourse-cdn.com/v4/letter/h/c37758/32.png) [@hackenstein](https://hub.mender.io/u/hackenstein)\ **Post date:** [August 20, 2025, 3:32pm UTC](https://hub.mender.io/t/mender-convert/7966/4 "2025-08-20T15:32:30Z")
Latest: Removed config file completely 2025-08-20 14:47:43 [WARN] [mender-convert-package] The calculated rootfs partition size 3760 MiB is too small. 2025-08-20 14:47:43 [WARN] [mender-convert-package] The actual rootfs image size is 9232 MiB 2025-08-20 14:47:43 [FATAL] [mender-convert-package] You can try adjusting the MENDER\_STORAGE\_TOTAL\_SIZE\_MB variable to increase available space, or modify one of the variables IMAGE\_ROOTFS\_SIZE, IMAGE\_ROOTFS\_EXTRA\_SPACE or IMAGE\_OVERHEAD\_FACTOR to reduce the size of the root filesystem. So… added config file with only IMAGE\_ROOTFS\_EXTRA\_SPACE=20480 sudo No luck so, replaced extra var with total\_size var. Built, applied and /dev/mmcblk0p2 does not exist. Next add config file back and change storage base var appending p ie. nvme0n1p ---
**Author:** ![hackenstein](https://avatars.discourse-cdn.com/v4/letter/h/c37758/32.png) [@hackenstein](https://hub.mender.io/u/hackenstein)\ **Post date:** [August 20, 2025, 4:00pm UTC](https://hub.mender.io/t/mender-convert/7966/5 "2025-08-20T16:00:19Z")
Appending the “p” seems to have fixed that issue. Now, checksums failing on blocks 1,2 and 7. Can’t execute /bin/init & /bin/sh. ---
**Author:** ![hackenstein](https://avatars.discourse-cdn.com/v4/letter/h/c37758/32.png) [@hackenstein](https://hub.mender.io/u/hackenstein)\ **Post date:** [August 20, 2025, 7:16pm UTC](https://hub.mender.io/t/mender-convert/7966/6 "2025-08-20T19:16:54Z")
Fixed finally. Had to reinstall debian on the client then capture that image, convert that then everything fell into place as expected. With all the install client links in the main docs page for mender and a little misguided assistance from AI, somehow I got the idea that the client needed to be installed before the base image capture and that just reeked havoc! With the clean base and the few config tweaks, everything just fell into place! ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [August 22, 2025, 10:59am UTC](https://hub.mender.io/t/mender-convert/7966/7 "2025-08-22T10:59:09Z")
Hi @hackenstein, Just now found time to follow up on this. Interesting, really the first time Mender Hub essentially served as rubberducking and an AI tool solved it 🙂 On a side note, if the resulting configuration does not yield any confidential information and relates to a publicly obtainable board, it would be helpful for others if you could share it here - possibly sanitized, of course. Greetz, Josef ---
**Author:** ![hackenstein](https://avatars.discourse-cdn.com/v4/letter/h/c37758/32.png) [@hackenstein](https://hub.mender.io/u/hackenstein)\ **Post date:** [August 22, 2025, 12:22pm UTC](https://hub.mender.io/t/mender-convert/7966/8 "2025-08-22T12:22:59Z")
Think you may have misread my post. AI caused my grief!