Hi Drew and crew :slight_smile: I think I am almost there with the mender integration in our custom hardware. The last step is still to go, though, as my rootfs update via mender keeps on failing. Here is the situation in detail: I managed to build my ubimg with the five volumes as intended (root…

I don’t have any ideas at the moment. Perhaps @kacf can spot something. Drew

After the mender install step, but before rebooting, are you able to mount the volume manually?

Thanks for answering @kacf . After updating and before booting, the effect is the same: [ubi_mount]

Can you give me some more information on how I can investigate the problem further? Overall there are several places where the problem could be. Is there a possibility to test the update process manually? Say perhaps untar the *.mender file and exchange the ubi0_1 volume on my own? Another question …

You can try to untar and dd it to the device manually, but I suspect that it won’t work because ubi devices are not regular block devices. But you can try some other things: Before running an update, can you do md5sum /dev/ubi0_1 sha256sum /dev/ubi0_1. Compare this to the checksum reported by doin…

Hi Kristian, thanks for your reply. Regarding the sha256 checksum I found out, that the ubi0_1 checksum and the *.mender checksum do not match. However, this is the case for the working version on my device vs. the mender artifact before installing the update. AFTER doing mender install, they do …

[image] buffo: So according to the checksum comparison, writing to the UBI volume works as intended, the not-matching checksum is strange. Yes, this is indeed strange. If we look at the code which builds the ubimg, we can see that it uses the raw filesystem blob as input . It’s not rebuilding …

Okay, I found out some more things. When flashing my NAND via u-boot I have two different possibilities: either I use the nand write or the nand write.trimffs function (which is also handled here: clicky , more infos: clicky ). The first one will lead to a successful boot, but I cannot reboot then due…

This is a very interesting finding, @buffo . I don’t think the client takes this into account. But it may not need to take it into account if the filesystem size is an exact multiple of the MENDER_UBI_LEB_SIZE (which it should be). Can you check what it is with: bitbake -e core-image-minimal | grep …

Thanks for the information! Currently I am building with my own image, nevertheless I also checked the minimal-image: [rootfs_size] As a result, the IMAGE_ROOTFS_SIZE must be a multiple of MENDER_UBI_LEB_SIZE (126976 in my case)?

Problem with rootfs update with *.mender

General Discussions

buffo August 9, 2021, 12:06pm 18

Okay, so I cannot use the rootfs-image-v2 update module to update my pre-made ubifs? As suggested, the ubiupdatevol method works with no problem, but the update via the mender client still fails.

Topic		Replies	Views
Mender update with initramfs General Discussions mender-client , imx6ull , kirkstone	17	698	April 2, 2024
Issues with UBIFS, rebooting and dashboard General Discussions nxp , buildroot , ubifs	25	1830	October 8, 2020
Mender update fails at 99% General Discussions yocto , warrior , tx2	11	1043	August 27, 2020
How to say mender client that artifact contains ubi image? OpenWrt	1	557	January 3, 2022
Deploy squashfs on ubiblock partitions General Discussions	13	3360	April 30, 2020

Problem with rootfs update with *.mender

Related topics