# File system update after mender install on Yocto. It still boots with old file system

**URL:** <https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900>\
**Category:** General Discussions\
**Tags:** yocto, imx8, qt, toradex, apalis\
**Created:** [June 7, 2023, 8:23am UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900 "2023-06-07T08:23:55Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![agunel](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@agunel](https://hub.mender.io/u/agunel)\
**Post date:** [June 7, 2023, 8:23am UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/1 "2023-06-07T08:23:55Z")

</div>

Hi  
I am using Apalis imx 8 board.  
We have added mender layers to our custom Yocto Build. Layers have been added and local.conf file changed accordingly.  
We use QT boot to Qt 6.4.3 layer.  
Integrating mender layer have worked and we created tezii image for our board. Loaded this image using Toradex easy installer. IT worked as expected. Partitions has created A/B and data partitions are present.  
We tested manual update using “mender install file.mender”. This worked too.

> root@b2qt-apalis-imx8:~# mender install /media/sda1/b2qt-embedded-qt6-image-apalis-imx8-20230531134214.mender  
> INFO[0000] Loaded configuration file: /var/lib/mender/mender.conf  
> INFO[0000] Loaded configuration file: /etc/mender/mender.conf  
> INFO[0002] Mender running on partition: /dev/mmcblk0p3  
> INFO[0003] Mender running on partition: /dev/mmcblk0p3  
> INFO[0003] Start updating from local image file: [/media/sda1/b2qt-embedded-qt6-image-apalis-imx8-20230531134214.mender]  
> Installing Artifact of size 852783616…  
> INFO[0003] No public key was provided for authenticating the artifact  
> INFO[0003] Opening device “/dev/mmcblk0p2” for writing  
> INFO[0003] Native sector size of block device /dev/mmcblk0p2 is 512 bytes. Mender will write in chunks of 1048576 bytes  
> … - 99 %INFO[0119] All bytes were successfully written to the new partition  
> INFO[0119] The optimized block-device writer wrote a total of 6049 frames, where 97 frames did need to be rewritten (i.e., skipped)  
> INFO[0120] Wrote 6341787648/6341787648 bytes to the inactive partition  
> … - 100 %  
> INFO[0120] Enabling partition with new image installed to be a boot candidate: 2  
> Use ‘commit’ to update, or ‘rollback’ to roll back the update.  
> At least one payload requested a reboot of the device it updated.  
> root@b2qt-apalis-imx8:~#

It was booted from /dev/mmcblk0p3 and as seen from the log it updated /dev/mmcblk0p2 partition.  
I have used mender commit on next power up.

The problem is kernel and boot settings (device tree file) have changed with the update. But file system partition has not been updated to correct one. It still boots to /dev/mmcblk0p3.

I have checked /dev/mmcblk0p2 and looks like it is updated with correct image, files are there. But it is not an active partition after the update.

I have started to experiment local.conf file settings and added e a few attributes for mender.

#MENDER\_BOOT\_PART:apalis-imx8 = “${MENDER\_STORAGE\_DEVICE\_BASE}p1”  
#MENDER\_ROOTFS\_PART\_A:apalis-imx8 = “${MENDER\_STORAGE\_DEVICE\_BASE}p2”  
MENDER\_ROOTFS\_PART\_A:apalis-imx8 = “/dev/mmcblk0p3”  
#MENDER\_ROOTFS\_PART\_B:apalis-imx8 = “${MENDER\_STORAGE\_DEVICE\_BASE}p3”  
MENDER\_ROOTFS\_PART\_B:apalis-imx8 = “/dev/mmcblk0p2”  
#MENDER\_DATA\_PART:apalis-imx8 = “${MENDER\_STORAGE\_DEVICE\_BASE}p4”

But no luck with the image created and written to board with this settings it stuck on boot after kernel load.

> Waiting for root device /dev/mmcblk02…  
> These are the partitions in previous test:  
> b2qt-apalis-imx8:~:\>ls /dev/mmcblk0  
> mmcblk0 mmcblk0boot0 mmcblk0boot1 mmcblk0p1 mmcblk0p2 mmcblk0p3 mmcblk0p4 mmcblk0rpmb

Any help on the topic appreciated. We feel like missed it so close.

Thanks

---

<div class="post-metadata">

**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:** [June 7, 2023, 8:19pm UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/2 "2023-06-07T20:19:01Z")

</div>

@drewmoseley any pointers?

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [June 7, 2023, 8:55pm UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/3 "2023-06-07T20:55:43Z")

</div>

Nothing immediately comes to mind. My best guess is something is not right in the uboot environment itself. Can you post the output of “printenv” from the U-Boot prompt?  
Drew

---

<div class="post-metadata">

**Author:** ![agunel](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@agunel](https://hub.mender.io/u/agunel)\
**Post date:** [June 8, 2023, 8:29am UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/4 "2023-06-08T08:29:39Z")

</div>

Here is my boot env:

> b2qt-apalis-imx8:~24\>fw\_printenv  
> altbootcmd=run mender\_altbootcmd; run bootcmd  
> apply\_overlays=for overlay\_file in ${fdt\_overlays}; do echo Applying Overlay: ${overlay\_file} && load ${mender\_uboot\_root} ${loadaddr} ${overlays\_prefix}${overlay\_file} && fdt apply ${loadaddr}; env set overlay\_file; done; true  
> arch=arm  
> baudrate=115200  
> board=apalis-imx8  
> board\_name=Apalis iMX8QM  
> board\_rev=v1.0  
> boot\_a\_script=load ${devtype} ${devnum}:${distro\_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}  
> boot\_extlinux=sysboot ${devtype} ${devnum}:${distro\_bootpart} any ${scriptaddr} ${prefix}${boot\_syslinux\_conf}  
> boot\_file=Image  
> boot\_prefixes=/ /boot/  
> boot\_script\_dhcp=boot.scr  
> boot\_scripts=boot.scr.uimg boot.scr  
> boot\_syslinux\_conf=extlinux/extlinux.conf  
> boot\_targets=mmc1 mmc2 mmc0 dhcp  
> bootcmd=run distro\_bootcmd  
> bootcmd\_args=run rootfsargs\_set && env set bootargs ${defargs} ${rootfsargs} ${setupargs} ${vidargs} ${tdxargs}  
> bootcmd\_boot=echo “Bootargs: ${bootargs}” && booti ${kernel\_addr\_r} - ${fdt\_addr\_r}  
> bootcmd\_dhcp=devtype=dhcp; if dhcp ${scriptaddr} ${boot\_script\_dhcp}; then source ${scriptaddr}; fi;  
> bootcmd\_dtb=echo Loading DeviceTree: ${fdtfile}; load ${mender\_uboot\_root} ${fdt\_addr\_r} ${load\_prefix}${fdtfile}  
> bootcmd\_kernel=load ${mender\_uboot\_root} ${kernel\_addr\_load} ${load\_prefix}${kernel\_image}  
> bootcmd\_mmc0=devnum=0; run mmc\_boot  
> bootcmd\_mmc1=devnum=1; run mmc\_boot  
> bootcmd\_mmc2=devnum=2; run mmc\_boot  
> bootcmd\_overlays=run load\_overlays\_file && run fdt\_resize && run apply\_overlays  
> bootcmd\_prepare=run set\_bootcmd\_kernel; run set\_bootcmd\_dtb; run set\_load\_overlays\_file; run set\_apply\_overlays  
> bootcmd\_run=run m4boot; run bootcmd\_dtb && run bootcmd\_overlays && run bootcmd\_args && run bootcmd\_kernel && run bootcmd\_unzip && run bootcmd\_boot; echo “Booting from ${devtype} failed!”  
> bootcmd\_unzip=;  
> bootcount=1  
> bootdelay=1  
> bootfstype=fat  
> bootlimit=1  
> commit\_atf=3c1583b  
> commit\_mkimage=3bfcfccb  
> commit\_scfw=f5623878  
> commit\_secofw=c9de51c0  
> console=ttyLP1  
> cpu=armv8  
> devplist=1  
> distro\_bootcmd=for target in ${boot\_targets}; do run bootcmd\_${target}; done  
> ethaddr=00:14:2d:6c:74:10  
> fdt\_addr\_r=0x9d400000  
> fdt\_board=eval  
> fdt\_resize=fdt addr ${fdt\_addr\_r} && fdt resize 0x20000  
> fdtcontroladdr=fd6a0150  
> fdtfile=imx8qm-apalis-v1.1-ixora-v1.2.dtb  
> fileaddr=9d480000  
> filesize=c93  
> initrd\_addr=0x83800000  
> initrd\_high=0xffffffffffffffff  
> ipaddr=192.168.10.2  
> kernel\_addr\_load=0x95400000  
> kernel\_addr\_r=0x95400000  
> kernel\_comp\_addr\_r=0xf0000000  
> kernel\_comp\_size=0x08000000  
> kernel\_image=Image.gz  
> load\_cmd=load ${mender\_uboot\_root}  
> load\_cmd\_boot=load ${mender\_uboot\_root}  
> load\_overlays\_file=load ${mender\_uboot\_root} ${loadaddr} ${overlays\_file}; env import -t ${loadaddr} ${filesize}  
> load\_prefix=boot/  
> loadaddr=0x95400000  
> m4boot=;  
> mender\_altbootcmd=if test ${mender\_boot\_part} = 2; then setenv mender\_boot\_part 3; setenv mender\_boot\_part\_hex 3; else setenv mender\_boot\_part 2; setenv mender\_boot\_part\_hex 2; fi; setenv upgrade\_available 0; saveenv; run mender\_setup  
> mender\_boot\_kernel\_type=booti  
> mender\_boot\_part=2  
> mender\_boot\_part\_hex=2  
> mender\_check\_saveenv\_canary=1  
> mender\_dtb\_name=imx8qm-apalis-v1.1-ixora-v1.2.dtb  
> mender\_kernel\_name=Image.gz  
> mender\_post\_setup\_commands= ; setenv tdxargs ${tdxargs} ${bootargs}; ; setenv overlays\_file /boot/overlays.txt;setenv overlays\_prefix boot/overlays/  
> mender\_saveenv\_canary=1  
> mender\_setup=if test “${mender\_saveenv\_canary}” != “1”; then setenv mender\_saveenv\_canary 1; saveenv; fi; if test “${mender\_pre\_setup\_commands}” != “”; then run mender\_pre\_setup\_commands; fi; if test “${mender\_systemd\_machine\_id}” != “”; then setenv bootargs “systemd.machine\_id=${mender\_systemd\_machine\_id} ${bootargs}”; fi; setenv mender\_kernel\_root /dev/mmcblk0p${mender\_boot\_part}; if test ${mender\_boot\_part} = 2; then setenv mender\_boot\_part\_name /dev/mmcblk0p2; else setenv mender\_boot\_part\_name /dev/mmcblk0p3; fi; setenv mender\_kernel\_root\_name ${mender\_boot\_part\_name}; setenv mender\_uboot\_root mmc 0:${mender\_boot\_part\_hex}; setenv mender\_uboot\_root\_name ${mender\_boot\_part\_name}; setenv expand\_bootargs “setenv bootargs \”${bootargs}\“”; run expand\_bootargs; setenv expand\_bootargs; if test “${mender\_post\_setup\_commands}” != “”; then run mender\_post\_setup\_commands; fi  
> mender\_try\_to\_recover=if test ${upgrade\_available} = 1; then reset; fi  
> mender\_uboot\_boot=mmc 0:1  
> mender\_uboot\_dev=0  
> mender\_uboot\_if=mmc  
> mmc\_boot=if mmc dev ${devnum}; then devtype=mmc; run scan\_dev\_for\_boot\_part; fi  
> netmask=255.255.255.0  
> overlays\_file=overlays.txt  
> overlays\_prefix=overlays/  
> preboot=setenv fdtfile ${mender\_dtb\_name}  
> ramdisk\_addr\_r=0x9d500000  
> rootfsargs\_set=env set rootfsargs root=${mender\_kernel\_root} ro rootwait  
> scan\_dev\_for\_boot=echo Scanning ${devtype} ${devnum}:${distro\_bootpart}…; for prefix in ${boot\_prefixes}; do run scan\_dev\_for\_extlinux; run scan\_dev\_for\_scripts; done;  
> scan\_dev\_for\_boot\_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro\_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro\_bootpart} bootfstype; then run scan\_dev\_for\_boot; fi; done; setenv devplist  
> scan\_dev\_for\_extlinux=if test -e ${devtype} ${devnum}:${distro\_bootpart} ${prefix}${boot\_syslinux\_conf}; then echo Found ${prefix}${boot\_syslinux\_conf}; run boot\_extlinux; echo SCRIPT FAILED: continuing…; fi  
> scan\_dev\_for\_scripts=for script in ${boot\_scripts}; do if test -e ${devtype} ${devnum}:${distro\_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot\_a\_script; echo SCRIPT FAILED: continuing…; fi; done  
> scriptaddr=0x9d480000  
> serial#=07107600  
> serverip=192.168.10.1  
> set\_apply\_overlays=env set apply\_overlays “for overlay\_file in \${fdt\_overlays}; do echo Applying Overlay: \${overlay\_file} && ${load\_cmd\_boot} \${loadaddr} \${overlays\_prefix}\${overlay\_file} && fdt apply \${loadaddr}; env set overlay\_file; done; true”  
> set\_bootcmd\_dtb=env set bootcmd\_dtb “echo Loading DeviceTree: \${fdtfile}; ${load\_cmd} \${fdt\_addr\_r} \${load\_prefix}\${fdtfile}”  
> set\_bootcmd\_kernel=env set bootcmd\_kernel “${load\_cmd} \${kernel\_addr\_load} \${load\_prefix}\${kernel\_image}”  
> set\_load\_overlays\_file=env set load\_overlays\_file “${load\_cmd\_boot} \${loadaddr} \${overlays\_file}; env import -t \${loadaddr} \${filesize}”  
> setup=setenv setupargs console=tty1 console=${console},${baudrate} consoleblank=0 earlycon  
> setupargs=console=tty1 console=ttyLP1,115200 consoleblank=0 earlycon  
> soc=imx8qm  
> stderr=serial@5a070000  
> stdin=serial@5a070000  
> stdout=serial@5a070000  
> update\_uboot=askenv confirm Did you load flash.bin resp. u-boot-dtb.imx (y/N)?; if test “$confirm” = “y”; then setexpr blkcnt ${filesize} + 0x1ff && setexpr blkcnt ${blkcnt} / 0x200; mmc dev 0 1; mmc write ${loadaddr} 0x0 ${blkcnt}; fi  
> upgrade\_available=0  
> variant=-v1.1  
> vendor=toradex  
> ver=U-Boot 2022.04-0+git.1c83b1aaad86 (Jan 05 2023 - 08:25:45 +0000)

---

<div class="post-metadata">

**Author:** ![dhiry2k](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@dhiry2k](https://hub.mender.io/u/dhiry2k)\
**Post date:** [June 8, 2023, 1:24pm UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/5 "2023-06-08T13:24:36Z")

</div>

any help would be appreciated. we are this close to integrating it with the system now !! maybe something in our uboot environment that we are missing out !!

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [June 8, 2023, 1:41pm UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/6 "2023-06-08T13:41:27Z")

</div>

Well it uses [distro\_bootcmd](https://developer.toradex.com/linux-bsp/os-development/boot/distro-boot/) which is expected. Since you are using boot2qt I’m assuming you didn’t use the same steps as [documented here](https://hub.mender.io/t/toradex-apalis-i-mx8/4103) to get your sources right? Can you share the details of how you got the full set of sources?

Drew

---

<div class="post-metadata">

**Author:** ![dhiry2k](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@dhiry2k](https://hub.mender.io/u/dhiry2k)\
**Post date:** [June 8, 2023, 1:58pm UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/7 "2023-06-08T13:58:34Z")

</div>

> repo init -u git://code.qt.io/yocto/boot2qt-manifest -m v6.4.3.xml
> 
> repo sync

Thats how we got the boot2qt sources.

after that we downloaded mender using git clone to kirkstone branch.

> git clone [GitHub - mendersoftware/meta-mender-community: Community supported Yocto Project layers (Board integrations) for Mender for different boards](https://github.com/mendersoftware/meta-mender-community.git) -b kirkstone
> 
> git clone [GitHub - mendersoftware/meta-mender: Yocto Project meta layer for the Mender client](https://github.com/mendersoftware/meta-mender.git) -b kirkstone

updated the local.conf baed on lessons from this post.

[https://hub.mender.io/t/toradex-apalis-imx8-yocto-with-mender/3759](https://hub.mender.io/t/toradex-apalis-imx8-yocto-with-mender/3759)

here are local.conf variables:

MENDER\_ARTIFACT\_NAME = “release-1”

# 

INHERIT += “mender-full”

# 

DISTRO\_FEATURES:append = " systemd"  
VIRTUAL-RUNTIME\_init\_manager = “systemd”  
DISTRO\_FEATURES\_BACKFILL\_CONSIDERED = “sysvinit”  
VIRTUAL-RUNTIME\_initscripts = “”

# 

# 

INHERIT += “mender-toradex”

# 

MENDER\_FEATURES\_ENABLE:append = " mender-uboot mender-image-sd"  
MENDER\_FEATURES\_DISABLE:append = " mender-grub mender-image-uefi"

# 

IMAGE\_CLASSES += “image\_type\_mender\_tezi”  
IMAGE\_FSTYPES:append = " mender\_tezi"  
IMAGE\_FSTYPES:remove = " teziimg"

# 

# Default is Image.gz, which is not compatible with GRUB

KERNEL\_IMAGETYPE:aarch64\_mender-grub = “Image”

# 

# boot.scr conflicts when using GRUB

IMAGE\_BOOT\_FILES:remove:mender-grub = “boot.scr-verdin-imx8mm;boot.scr”

# 

# Remove files from boot partition that are loaded by Mender

# from the root partitions; this allows the files to be updated OTA

IMAGE\_BOOT\_FILES:remove:mender-uboot = “zImage ${KERNEL\_DEVICETREE} overlays.txt overlays/\*;overlays/”

# 

# 

MENDER\_IMAGE\_BOOTLOADER\_BOOTSECTOR\_OFFSET:apalis-imx8 = “0”  
MENDER\_BOOT\_PART\_SIZE\_MB:apalis-imx8 = “32”  
OFFSET\_SPL\_PAYLOAD:apalis-imx8 = “”  
MENDER\_STORAGE\_DEVICE:apalis-imx8 = “/dev/mmcblk0”  
MENDER\_STORAGE\_TOTAL\_SIZE\_MB:apalis-imx8 = “12288”

MENDER\_UBOOT\_POST\_SETUP\_COMMANDS:append = " ; setenv tdxargs ${tdxargs} ${bootargs}; "

MENDER\_UBOOT\_POST\_SETUP\_COMMANDS:append = " ; setenv overlays\_file /boot/overlays.txt;setenv overlays\_prefix boot/overlays/ "

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [June 8, 2023, 4:53pm UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/8 "2023-06-08T16:53:54Z")

</div>

I’ve never tried to get it working using the Boot2QT repo manifests. I’ve only ever used the Toradex manifests. I suspect something is not getting applied properly related to the Distro Boot stuff. Specifically I would suggest investigating [this patch](https://github.com/mendersoftware/meta-mender-community/blob/kirkstone/meta-mender-toradex-nxp/recipes-bsp/u-boot-distro-boot/files/toradex-bsp-6.0.0/0001-Adapt-boot.cmd.in-to-Mender.patch).

I’ll try to build with TORADEX\_BSP\_VERSION=6.2.0 and will probably need to make a few mods to the layer to support that but I suspect in your case you will need even more changes.

Drew

---

<div class="post-metadata">

**Author:** ![dhiry2k](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@dhiry2k](https://hub.mender.io/u/dhiry2k)\
**Post date:** [June 8, 2023, 9:16pm UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/10 "2023-06-08T21:16:55Z")

</div>

yes , i remember i applied this patch as it was failing in patching. I manually created this patch and applied.

so seems like i applied.

> +env set bootcmd\_run 'run m4boot; run bootcmd\_dtb && run bootcmd\_overlays && run bootcmd\_args && run bootcmd\_kernel && run bootcmd\_unzip && run bootcmd\_boot; echo “Booting from ${devtype} failed!” && false’env set bootcmd\_run ‘run m4boot; run bootcmd\_dtb && run bootcmd\_overlays && run bootcmd\_args && run bootcmd\_kernel && run bootcmd\_unzip && run bootcmd\_boot; echo “Booting from ${devtype} failed!”’

instead of

> +env set bootcmd\_run ‘run m4boot; run bootcmd\_dtb && run bootcmd\_overlays && run bootcmd\_args && run bootcmd\_kernel && run bootcmd\_unzip && run bootcmd\_boot; echo “Booting from ${devtype} failed!”’

Let us try that again and see if that works !!

---

<div class="post-metadata">

**Author:** ![dhiry2k](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@dhiry2k](https://hub.mender.io/u/dhiry2k)\
**Post date:** [June 9, 2023, 11:03am UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/11 "2023-06-09T11:03:31Z")

</div>

Thanks [drewmoseley](https://hub.mender.io/u/drewmoseley) , things are working fine now !!

you are a saviour 🙂 we may mark this thread as solved. i can list down few steps for boot2qt on imxapalis8 if you are okay with that.

---

<div class="post-metadata">

**Author:** ![agunel](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@agunel](https://hub.mender.io/u/agunel)\
**Post date:** [June 9, 2023, 11:06am UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/12 "2023-06-09T11:06:38Z")

</div>

Thanks All!  
It is working with b2qt now.

---

<div class="post-metadata">

**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:** [June 10, 2023, 1:09pm UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/13 "2023-06-10T13:09:41Z")

</div>

Noting down a kind of summary would be very much appreciated @dhiry2k, es far as I know the board also does not have a known good integration at the moment.

Greets  
Josef

---

<div class="post-metadata">

**Author:** ![dhiry2k](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@dhiry2k](https://hub.mender.io/u/dhiry2k)\
**Post date:** [June 15, 2023, 9:35am UTC](https://hub.mender.io/t/file-system-update-after-mender-install-on-yocto-it-still-boots-with-old-file-system/5900/15 "2023-06-15T09:35:25Z")

</div>

sure, i added [here](https://hub.mender.io/t/how-to-manage-your-qt-based-embedded-linux-device-with-mender-apalis-imx8/5921), please update if you feel changes are needed.