# Rasberry pi 32-bit OS bullseye fails to boot (image via mender-convert) **URL:** \ **Category:** Debian family\ **Created:** [January 9, 2026, 1:17pm UTC](https://hub.mender.io/t/rasberry-pi-32-bit-os-bullseye-fails-to-boot-image-via-mender-convert/8160 "2026-01-09T13:17:39Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![user706](https://avatars.discourse-cdn.com/v4/letter/u/ba9def/32.png) [@user706](https://hub.mender.io/u/user706)\ **Post date:** [January 9, 2026, 1:17pm UTC](https://hub.mender.io/t/rasberry-pi-32-bit-os-bullseye-fails-to-boot-image-via-mender-convert/8160/1 "2026-01-09T13:17:39Z")
I using this config in mender-convert: ```auto # https://docs.mender.io/operating-system-updates-debian-family/variables source configs/raspberrypi/uboot/include/raspberrypi4_config MENDER_CLIENT_VERSION=5.0.1 # needs tweaking of MENDER_APT_REPO_URL below!!! MENDER_STORAGE_URL="https://downloads.mender.io" MENDER_APT_REPO_URL="${MENDER_STORAGE_URL}/repos/debian" DEPLOY_IMAGE_NAME=roper-rpi-image-raspberrypi4-mender MENDER_COMPRESS_DISK_IMAGE="lzma" MENDER_ARTIFACT_COMPRESSION="lzma" MENDER_STORAGE_TOTAL_SIZE_MB="6500" MENDER_BOOT_PART_SIZE_MB="256" IMAGE_ROOTFS_SIZE="-1" IMAGE_ROOTFS_EXTRA_SPACE="0" IMAGE_OVERHEAD_FACTOR="1.0" MENDER_DATA_PART_SIZE_MB="128" MENDER_DATA_PART_GROWFS="y" MENDER_ENABLE_SYSTEMD="n" ``` I wrote the image to the micro SD-card. The booting fails. It is in an endless loop, trying again and again I see ```auto mount: /boot: can't find in /etc/fstab. EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. sed: can't read /boot/cmdline.txt: No such file or directory sed: can't read /boot/cmdline.txt: No such file or directory grep: /boot/cmdline.txt: No such file or directory mount: /boot: mount point not mounted or bad option. cat: /sys/block/loop0//partition: No such file or directory ``` I’m converting the image with the newest mender-convert (version 5.1.0). Do I need to add this to my config? → `MENDER_BOOT_PART_MOUNT_LOCATION="/boot"` ---
**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:** [January 9, 2026, 1:35pm UTC](https://hub.mender.io/t/rasberry-pi-32-bit-os-bullseye-fails-to-boot-image-via-mender-convert/8160/2 "2026-01-09T13:35:24Z")
Hi @user706, Yes, depending on if you’re using `bullseye` and earlier or `bookworm` and later, different settings are required. This was a breaking change that Raspberry Pi OS `bookworm` introduced. You can see the correlated includes at [mender-convert/configs/raspberrypi/uboot/debian/raspberrypi4\_bullseye\_32bit\_config at master · mendersoftware/mender-convert · GitHub](https://github.com/mendersoftware/mender-convert/blob/master/configs/raspberrypi/uboot/debian/raspberrypi4_bullseye_32bit_config) and [mender-convert/configs/raspberrypi/uboot/debian/raspberrypi4\_bookworm\_32bit\_config at master · mendersoftware/mender-convert · GitHub](https://github.com/mendersoftware/mender-convert/blob/master/configs/raspberrypi/uboot/debian/raspberrypi4_bookworm_32bit_config). Your configuration should therefore either include [mender-convert/configs/raspberrypi/include/pre\_bookworm\_config at master · mendersoftware/mender-convert · GitHub](https://github.com/mendersoftware/mender-convert/blob/master/configs/raspberrypi/include/pre_bookworm_config), or [mender-convert/configs/raspberrypi/uboot/include/bookworm\_config at master · mendersoftware/mender-convert · GitHub](https://github.com/mendersoftware/mender-convert/blob/master/configs/raspberrypi/uboot/include/bookworm_config). This adjusts the `/boot` mount path and if necessary a few other things. Greetz, Josef ---
**Author:** ![user706](https://avatars.discourse-cdn.com/v4/letter/u/ba9def/32.png) [@user706](https://hub.mender.io/u/user706)\ **Post date:** [January 9, 2026, 1:44pm UTC](https://hub.mender.io/t/rasberry-pi-32-bit-os-bullseye-fails-to-boot-image-via-mender-convert/8160/3 "2026-01-09T13:44:40Z")
Thanks!! Yes (I just realized it myself. ) Conversion is running. Keeping my fingers crossed. ---
**Author:** ![user706](https://avatars.discourse-cdn.com/v4/letter/u/ba9def/32.png) [@user706](https://hub.mender.io/u/user706)\ **Post date:** [January 9, 2026, 1:50pm UTC](https://hub.mender.io/t/rasberry-pi-32-bit-os-bullseye-fails-to-boot-image-via-mender-convert/8160/4 "2026-01-09T13:50:30Z")
By the way, above in the config you can see `MENDER_CLIENT_VERSION=5.0.1` When I was using `lastest` and got client 5.0.3, I was running into this issue: mender-update install file.mender resulted in > [@System update fails "Could not open path to sync"](https://hub.mender.io/t/system-update-fails-could-not-open-path-to-sync/8088/12): > > Oh, thanks. So this really is like that, that starting from mender-update 5.0.2 only 64 bit OS is supported?? Because I’m on 32 bit raspberry pi, and running mender-update 5.0.3 and command mender-update install myupdate.mender results in record\_id=1 severity=error time="2026-Jan-08 11:45:33.337012" name="Global" msg="No such file or directory: Could not open path to sync: \x08��\x01\x00\x00\x00\x00/mender/modules/v3/payloads/0000/tree/current\_device\_type" Streaming failed. System not modi… Is it true that for raspberry pi OS bullseye 32-bits, I need `MENDER_CLIENT_VERSION=5.0.1` and that higher versions are only for 64 bit??? ---
**Author:** ![user706](https://avatars.discourse-cdn.com/v4/letter/u/ba9def/32.png) [@user706](https://hub.mender.io/u/user706)\ **Post date:** [January 9, 2026, 1:56pm UTC](https://hub.mender.io/t/rasberry-pi-32-bit-os-bullseye-fails-to-boot-image-via-mender-convert/8160/5 "2026-01-09T13:56:19Z")
I can boot… BUT: `mender-grow-data.service` failed! ```auto ● mender-grow-data.service - Mender service to grow data partition size Loaded: loaded (/etc/systemd/system/mender-grow-data.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2026-01-09 11:03:50 CET; 3h 51min ago Process: 234 ExecStart=/sbin/parted --fix --script /dev/mmcblk0 resizepart 4 100% (code=exited, status=1/FAILURE) Main PID: 234 (code=exited, status=1/FAILURE) CPU: 21ms Jan 09 11:03:50 raspberrypi systemd[1]: Starting Mender service to grow data partition size... Jan 09 11:03:50 raspberrypi parted[234]: /sbin/parted: unrecognized option '--fix' Jan 09 11:03:50 raspberrypi parted[234]: Usage: /sbin/parted [-hlmsv] [-a] [DEVICE [COMMAND [PARAMETERS]]...] Jan 09 11:03:50 raspberrypi systemd[1]: mender-grow-data.service: Main process exited, code=exited, status=1/FAILURE Jan 09 11:03:50 raspberrypi systemd[1]: mender-grow-data.service: Failed with result 'exit-code'. Jan 09 11:03:50 raspberrypi systemd[1]: Failed to start Mender service to grow data partition size. ``` ---
**Author:** ![user706](https://avatars.discourse-cdn.com/v4/letter/u/ba9def/32.png) [@user706](https://hub.mender.io/u/user706)\ **Post date:** [January 9, 2026, 1:59pm UTC](https://hub.mender.io/t/rasberry-pi-32-bit-os-bullseye-fails-to-boot-image-via-mender-convert/8160/6 "2026-01-09T13:59:26Z")
> [@user706](#): > > `/sbin/parted: unrecognized option '--fix'` debian bullseye has an old `parted` that does not yet support the `--fix` flag. Bug is here: [mender-grow-data.service](https://github.com/mendersoftware/mender-convert/blob/460a3c7fe0f60a11da4ee607c7f06e850c646098/configs/systemd_common_config#L19) `--fix` got added in this commit: [fix: systemd\_common\_config: add --fix option to parted call · mendersoftware/mender-convert@ef68160 · GitHub](https://github.com/mendersoftware/mender-convert/commit/ef6816058bfa406ca925928f177e188f838c9645) Perhaps better to have code like this: ```auto ExecStart=/bin/sh -c "/sbin/parted --fix --script $(disk_get_device_base "${MENDER_STORAGE_DEVICE_BASE}") resizepart ${MENDER_DATA_PART_NUMBER} 100% >/dev/null 2>&1 || /sbin/parted --script $(disk_get_device_base "${MENDER_STORAGE_DEVICE_BASE}") resizepart ${MENDER_DATA_PART_NUMBER} 100%" ``` ---
**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:** [January 12, 2026, 10:22am UTC](https://hub.mender.io/t/rasberry-pi-32-bit-os-bullseye-fails-to-boot-image-via-mender-convert/8160/7 "2026-01-12T10:22:52Z")
Hi @user706, We’re looking into variations of this particular implementation currently for other reasons. Yet for the `bullseye` compatibility, the distribution has already moved out of general support last year. There might be more corner cases and breaking points by now, sorry. Greetz, Josef ---
**Author:** ![user706](https://avatars.discourse-cdn.com/v4/letter/u/ba9def/32.png) [@user706](https://hub.mender.io/u/user706)\ **Post date:** [January 12, 2026, 10:35am UTC](https://hub.mender.io/t/rasberry-pi-32-bit-os-bullseye-fails-to-boot-image-via-mender-convert/8160/8 "2026-01-12T10:35:45Z")
ok thanks. This is the only break that I’ve found. But with my workaround in the code (shown above) it works. (I can update old system to this new mender. I can then self-update again to same mender (just to check it works). etc.)