# Invalid variable in U-boot environment

**URL:** <https://hub.mender.io/t/invalid-variable-in-u-boot-environment/5922>\
**Category:** General Discussions\
**Created:** [June 15, 2023, 11:44am UTC](https://hub.mender.io/t/invalid-variable-in-u-boot-environment/5922 "2023-06-15T11:44:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![krisvanrens](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/krisvanrens/32/1454_2.png) [@krisvanrens](https://hub.mender.io/u/krisvanrens)\
**Post date:** [June 15, 2023, 11:44am UTC](https://hub.mender.io/t/invalid-variable-in-u-boot-environment/5922/1 "2023-06-15T11:44:18Z")

</div>

Hi,

I’ve come across a log message from Mender indicating an unsupported variable in the U-boot environment. This is the log message:

```auto
Jun 15 12:19:46 user.info mender[5489]: ...
Jun 15 12:19:46 user.info mender[5489]: time="2023-06-15T12:19:46+02:00" level=info msg="Output (stderr) from command \"fw_printenv\": ERR: no such variable: mender_check_saveenv_canary"
Jun 15 12:19:46 user.info mender[5489]: time="2023-06-15T12:19:46+02:00" level=info msg="Output (stderr) from command \"fw_printenv\": ERR: no such variable: mender_check_saveenv_canary"
Jun 15 12:19:46 user.info mender[5489]: ...

```

I see the message coming up in various other posts as well. But IMHO messages like this are bad, even if they can be ignored, as they obscure other relevant messages or degrade the meaning of relevant log messages.

It seems the variable was introduced in [this patch](https://github.com/mendersoftware/meta-mender/blob/master/meta-mender-core/recipes-bsp/u-boot/patches/0002-Generic-boot-code-for-Mender.patch), which is still the leading implementation for the master branch.

Two questions:

1. Is this a bug on the Mender application side, or a bug in the U-boot environment side? Either way it seems to be harmless for our application, but still.
2. If it’s a bug, I’d happily submit a patch for it and a PR on `meta-mender`. But I do need some help regarding the version to which this should be applied.

Thanks,

Kris