# Mender commit in stand-alone mode

**URL:** <https://hub.mender.io/t/mender-commit-in-stand-alone-mode/2604>\
**Category:** General Discussions\
**Created:** [September 30, 2020, 9:12pm UTC](https://hub.mender.io/t/mender-commit-in-stand-alone-mode/2604 "2020-09-30T21:12:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikhailtchernychev](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mikhailtchernychev/32/1023_2.png) [@mikhailtchernychev](https://hub.mender.io/u/mikhailtchernychev)\
**Post date:** [September 30, 2020, 9:12pm UTC](https://hub.mender.io/t/mender-commit-in-stand-alone-mode/2604/1 "2020-09-30T21:12:56Z")

</div>

Hi,

I am a bit confused about when `mender commit` should be called. I assume first `mender install` is used, then reboot (system reboots from updated partition) and them `mender commit`. But it appeared that reboot itself does not switch the partition. But install,commit,reboot does. Am I right?

Thank you  
Mikhail

---

<div class="post-metadata">

**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\
**Post date:** [September 30, 2020, 9:58pm UTC](https://hub.mender.io/t/mender-commit-in-stand-alone-mode/2604/2 "2020-09-30T21:58:47Z")

</div>

Assuming this is an embedded arm/yocto/uboot project, unless something changed in newer versions of mender client, historically mender -install in standalone mode was enough to do the update and switch the partitions in the bootloader environment. Then reboot which should startup in the newly updated partition, then do a mender -commit if happy with the newly booted partition.

If i recall correctly, use the following bootloader tool:  
`fw_printenv -n mender_boot_part`  
`fw_printenv -n upgrade_available`

before and after doing the mender -install and you should the bootloader env variables change

---

<div class="post-metadata">

**Author:** ![mikhailtchernychev](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mikhailtchernychev/32/1023_2.png) [@mikhailtchernychev](https://hub.mender.io/u/mikhailtchernychev)\
**Post date:** [September 30, 2020, 10:05pm UTC](https://hub.mender.io/t/mender-commit-in-stand-alone-mode/2604/3 "2020-09-30T22:05:57Z")

</div>

This is actually ubuntu x86\_64 20 server, converted with mender-convert tool.

Yes I see that sequence is install - reboot -update.

BTW

```auto
~$ fw_printenv -n mender_boot_part
/usr/bin/fw_printenv: 1: eval: Bad substitution

```

but it works with no arguments.

```auto
~$ fw_printenv 
bootcount=1
mender_boot_part=3
upgrade_available=0
mender_boot_part_hex=3

```

Thank you!

---

<div class="post-metadata">

**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\
**Post date:** [September 30, 2020, 11:02pm UTC](https://hub.mender.io/t/mender-commit-in-stand-alone-mode/2604/4 "2020-09-30T23:02:18Z")

</div>

ok great, yer if i recall with the mender-convert on golden-images like ubuntu, the fw\_printenv installed is not the same tool as the one that comes with uboot as I think it make changes to efi/grub instead on your device