# Mender\_grubenv.config has wrong file path to grub files

**URL:** <https://hub.mender.io/t/mender-grubenv-config-has-wrong-file-path-to-grub-files/4579>\
**Category:** General Discussions\
**Tags:** grub, zeus, variscite\
**Created:** [February 7, 2022, 4:52pm UTC](https://hub.mender.io/t/mender-grubenv-config-has-wrong-file-path-to-grub-files/4579 "2022-02-07T16:52:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rlaybourn](https://avatars.discourse-cdn.com/v4/letter/r/43a26b/32.png) [@rlaybourn](https://hub.mender.io/u/rlaybourn)\
**Post date:** [February 7, 2022, 4:52pm UTC](https://hub.mender.io/t/mender-grubenv-config-has-wrong-file-path-to-grub-files/4579/1 "2022-02-07T16:52:28Z")

</div>

I have a problem where rootfs updates are failing due to “No match between boot and root partitions”. I am thinking this may be because fw\_printenv is unable to read the boot environment variables. The problem seems to be caused by an incorrect file path in the file “/etc/mender\_grubenv.config” . The grub file are in “/boot/efi/EFI/BOOT” however this file contains the path “/uboot/EFI/BOOT” which does not exist. Removing the file appears to fix the fw\_printenv problem. Does anyone know where the path in that file comes from? . This did work before and to the best of my knowledge I have not modified anything related to it so am a little stumped as to where to start looking

---

<div class="post-metadata">

**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:** [February 8, 2022, 9:03am UTC](https://hub.mender.io/t/mender-grubenv-config-has-wrong-file-path-to-grub-files/4579/2 "2022-02-08T09:03:20Z")

</div>

Is this using Yocto or mender-convert? It seems to indicate that the configuration is set (partially) to U-Boot integration, but the board is using GRUB integration. It should not happen, so it might be a bug.

---

<div class="post-metadata">

**Author:** ![rlaybourn](https://avatars.discourse-cdn.com/v4/letter/r/43a26b/32.png) [@rlaybourn](https://hub.mender.io/u/rlaybourn)\
**Post date:** [February 8, 2022, 4:45pm UTC](https://hub.mender.io/t/mender-grubenv-config-has-wrong-file-path-to-grub-files/4579/3 "2022-02-08T16:45:43Z")

</div>

This is an image that is being built using yocto for a variscite imx6ul module. I currently have a sticking plaster fix of using a Rootfs post process command to remove the file with the incorrect file path. That works for the time being but I dont see that as any kind of long term fix

---

<div class="post-metadata">

**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:** [February 10, 2022, 7:43am UTC](https://hub.mender.io/t/mender-grubenv-config-has-wrong-file-path-to-grub-files/4579/4 "2022-02-10T07:43:40Z")

</div>

The file comes from the `grub-mender-grubenv` recipe. I don’t really understand how it can change, although it can be altered by setting some special variables, it’s not something we document. What does this say?

```auto
bitbake -e grub-mender-grubenv | grep 'BOOT_DIR='

```