# Mender upate flag not set **URL:** https://hub.mender.io/t/mender-upate-flag-not-set/5540 **Category:** General Discussions **Created:** [January 13, 2023, 4:49am UTC](https://hub.mender.io/t/mender-upate-flag-not-set/5540 "2023-01-13T04:49:21Z") **Posts on this page:** 1 **Showing post:** 9
### Author: ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf) #### Post date: [January 16, 2023, 7:35am UTC](https://hub.mender.io/t/mender-upate-flag-not-set/5540/9 "2023-01-16T07:35:32Z")
The second reboot is weird, it looks like it’s going back in time. But it also sounds like the boot loader tools are not working correctly on the second partition. Can you add a state script, `ArtifactReboot_Enter_00_Debug` and `ArtifactReboot_Leave_00_Debug` where you execute `grub-mender-grubenv-print`, so that we can see what the environment is before and after the reboot? Apart from that debugging, here are a few other things to try: 1. In general using an old server with a new client is not supported, only the opposite is (new server and old client). Try upgrading the server to the latest version. 2. Can you try installing a [file update](https://hub.mender.io/t/single-file/486/1) before you install a full rootfs-image update? Just install a dummy file in `/tmp` for example. --- _[View the full topic](https://hub.mender.io/t/mender-upate-flag-not-set/5540)._