Switching back to the previous slot when the device fails to boot


I’m testing deployments using Mender in a Jetson TX2 device (using Jetpack 4.6.1, ota tools version R32.6.1) following the tutorial available in Nvidia Jetson L4T Integration - Debian family - Mender Hub. I have already created a working artifact and I was able to deploy it correctly on another device.

Now, I’m testing scenarios where errors are introduced in a controllable way. In one of them, the non-bootable artifact has been created by removing Image and zImage files from the boot folder in the OS snapshot. According to the Nvidia documentation, if the device fails to boot to the updated slot, it switches back to the previous slot, however in this test the device did not boot. Should I introduce any step in the procedure described here to permit a rollback in this kind of situation?

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.

hello mchudzik,

there should be messages reported,
could you please share the bootloader logs for reference,

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.