Good Day Friends!
Due to the choise of hardware I’m forced to write an update module to make system updates. I was not able to integrate Mender with U-Boot. I managed to handle this but some commands in my update module always return non-zero codes even if the operation ended as expected or what I would consider successful.
My update module is receiving and rooftfs.ext4. This will be written to rootfsB with
dd. After that the rootfsB filesystem will be resized with
resize2fs. For this successful to happen,
e2fsck $target_partition -f -y needs to be executed.
In my special case its the
e2fsck $target_partition -f -y || true. This commands somehow return always non-zero code and the stage
How can I deal with this behaviour? How can I suppress such errors or make an exception?
One thing is that the eMMC is randomly switching between
U-Boot env is on the data partition /mnt/uboot.env.
altboot are triggered as expected.