[FAILED] Failed to start Mender ser…e to grow data partition size

General Discussions
1

I am working on my raspberrypi CM4 with mender.
I try to compile the mender image.
It works. however, when I boot the system.it shows the error log as the title
“[FAILED] Failed to start Mender ser…e to grow data partition size.”

here is my porject information:
poky: git://git.yoctoproject.org/poky branch:dunfell
meta-openembedded: GitHub - openembedded/meta-openembedded branch:dunfell
meta-raspberrypi:git://git.yoctoproject.org/meta-raspberrypi branch:dunfell
meta-mender: GitHub - mendersoftware/meta-mender: Yocto Project meta layer for the Mender client branch: dunfell

detail for build/conf/bblayers.conf:
BBLAYERS ?= "
/home/xiongjian/source_code/yocto_raspberry/poky/meta
/home/xiongjian/source_code/yocto_raspberry/poky/meta-poky
/home/xiongjian/source_code/yocto_raspberry/poky/meta-yocto-bsp
/home/xiongjian/source_code/yocto_raspberry/poky/meta-raspberrypi
/home/xiongjian/source_code/yocto_raspberry/poky/meta-mender/meta-mender-core
/home/xiongjian/source_code/yocto_raspberry/poky/meta-openembedded/meta-python
/home/xiongjian/source_code/yocto_raspberry/poky/meta-openembedded/meta-oe
/home/xiongjian/source_code/yocto_raspberry/poky/meta-openembedded/meta-networking
/home/xiongjian/source_code/yocto_raspberry/poky/meta-openembedded/meta-multimedia
/home/xiongjian/source_code/yocto_raspberry/poky/meta-mender/meta-mender-demo
"
detail for local.conf:
RPI_USE_U_BOOT = “1”
IMAGE_INSTALL_append = " kernel-image kernel-devicetree"
MENDER_FEATURES_DISABLE_append = " mender-image-uefi mender-grub"
IMAGE_FSTYPES_remove += " rpi-sdimg"
#SDIMG_ROOTFS_TYPE = “ext4”
INHERIT += “mender-full”
MENDER_BOOT_PART_SIZE_MB = “64”
#MENDER_PARTITION_ALIGNMENT = “67108864”

MENDER_ARTIFACT_NAME = “release-1”

DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = “systemd”
DISTRO_FEATURES_BACKFILL_CONSIDERED = “sysvinit”
VIRTUAL-RUNTIME_initscripts = “”
MENDER_STORAGE_TOTAL_SIZE_MB = “2048”

I want to know if there is any solution for this problem.

2

Can you use journalctl to get and paste the logs of the failed service to get to the underlying cause.

journalctl -u <NAME OF SERVICE>

example:

journalctl -u wpa_supplicant.service

3

Thank you for your reply.
I finally find out the reason of my problem.
I use the wrong imag file for flashing my device.
I should use the *.sdimg not the *wic.bz2.
Everything works fine after I use the right image file.

1 Like
4

glad you fixed it. :slight_smile: