# Adding mender-partuuid causes an error: "/dev/sda1 Does not contain a valid PARTUUID path"

**URL:** <https://hub.mender.io/t/adding-mender-partuuid-causes-an-error-dev-sda1-does-not-contain-a-valid-partuuid-path/992>\
**Category:** General Discussions\
**Tags:** yocto, thud\
**Created:** [September 9, 2019, 12:03pm UTC](https://hub.mender.io/t/adding-mender-partuuid-causes-an-error-dev-sda1-does-not-contain-a-valid-partuuid-path/992 "2019-09-09T12:03:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\
**Post date:** [September 9, 2019, 12:20pm UTC](https://hub.mender.io/t/adding-mender-partuuid-causes-an-error-dev-sda1-does-not-contain-a-valid-partuuid-path/992/2 "2019-09-09T12:20:25Z")

</div>

You are using `thud` branch of meta-mender? Can you also share the configuration options in `local.conf`.

Also please note that `mender-partuuid` will not solve your problem, see my comment here,

> [@Force Grub to select eMMC when Flash Drive plugged in](https://hub.mender.io/t/force-grub-to-select-emmc-when-flash-drive-plugged-in/725/11):
>
> Makes sense now, that partuuid only applies to the mender\_root variable and not to the mender\_grub\_storage\_device. I can not think of an easy way to get around this, because GRUB is not able to scan/probe for a partuuid. But I know of one user who has solved a similar problem using the GRUB [search](https://www.gnu.org/software/grub/manual/grub/grub.html#search) command, which supports looking up filesystem image by label or fs-uuid. But this would require changes to the grub.cfg file + making sure that the partitions are labeled accordingly on each update.

---

_[View the full topic](https://hub.mender.io/t/adding-mender-partuuid-causes-an-error-dev-sda1-does-not-contain-a-valid-partuuid-path/992)._
