# Mender update - preventing rollback

**URL:** <https://hub.mender.io/t/mender-update-preventing-rollback/5776>\
**Category:** General Discussions\
**Tags:** yocto\
**Created:** [April 20, 2023, 6:48am UTC](https://hub.mender.io/t/mender-update-preventing-rollback/5776 "2023-04-20T06:48:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tirank](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tirank/32/1231_2.png) [@Tirank](https://hub.mender.io/u/Tirank)\
**Post date:** [April 20, 2023, 6:48am UTC](https://hub.mender.io/t/mender-update-preventing-rollback/5776/1 "2023-04-20T06:48:21Z")

</div>

Hello,  
I am using mender-client on the Yocto duffel 32.5.1 for Nvidia Jetson NX Xavier.  
I have a version to be deployed, but I need to make sure device will NEVER rollback from this version to older ones.  
If, for example, my version is 2.0 and old version before update was 1.0, installation of 2.0 was completed, device reboots and tries to report to server. If reporting fails, at some point the device will roll back to 1.0.

Also, if boot fails repeatedly even after 2.0 was committed successfully, it will try to go back to 1.0.

Trying to avoid these…

Is there a way I can mark the B partition as not bootable? Maybe write my 2.0 image to both A and B (is this possible)?

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:** [May 13, 2023, 8:38pm UTC](https://hub.mender.io/t/mender-update-preventing-rollback/5776/2 "2023-05-13T20:38:28Z")

</div>

Hi @Tirank,

In case this has not been solved yet, a possible solution is the Update Module provided [here](https://github.com/mendersoftware/mender-update-modules/blob/master/rootfs-version-check/README.md)

Greetz,  
Josef