# Mender-partuuid and mender-data-growfs incompatible

**URL:** <https://hub.mender.io/t/mender-partuuid-and-mender-data-growfs-incompatible/1274>\
**Category:** General Discussions\
**Created:** [November 22, 2019, 3:26pm UTC](https://hub.mender.io/t/mender-partuuid-and-mender-data-growfs-incompatible/1274 "2019-11-22T15:26:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mdavis777](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mdavis777/32/65_2.png) [@mdavis777](https://hub.mender.io/u/mdavis777)\
**Post date:** [November 22, 2019, 3:26pm UTC](https://hub.mender.io/t/mender-partuuid-and-mender-data-growfs-incompatible/1274/1 "2019-11-22T15:26:06Z")

</div>

Mender-partuuid throws a warning if MENDER\_STORAGE\_DEVICE is defined however mender-data-growfs requires it to be there to work.  
Should there be a warning if both are enabled or automatically disable growfs if partuuid is enabled?  
Another option would be to expand the script to find the data drive by label or UUID if MENDER\_STORAGE\_DEVICE is not defined.

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [November 23, 2019, 3:07am UTC](https://hub.mender.io/t/mender-partuuid-and-mender-data-growfs-incompatible/1274/2 "2019-11-23T03:07:38Z")

</div>

I think it would be best if we can support both option simultaneously. What is the error you are seeing? Is it a build issue or runtime?

---

<div class="post-metadata">

**Author:** ![mdavis777](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mdavis777/32/65_2.png) [@mdavis777](https://hub.mender.io/u/mdavis777)\
**Post date:** [November 23, 2019, 3:34am UTC](https://hub.mender.io/t/mender-partuuid-and-mender-data-growfs-incompatible/1274/3 "2019-11-23T03:34:23Z")

</div>

Somewhat both. Defining MENDER\_STORAGE\_DEVICE triggers  
if bb.utils.contains(‘DISTRO\_FEATURES’, ‘mender-partuuid’, True, False, d) and d.getVar(‘MENDER\_STORAGE\_DEVICE’, True) != “”:  
bb.warn(“MENDER\_STORAGE\_DEVICE is ignored when mender-partuuid is enabled. Clear MENDER\_STORAGE\_DEVICE to remove this warning.”)  
}

However MENDER\_STORAGE\_DEVICE is used to feed the growfs systemd script.  
ExecStart=/usr/sbin/parted -s {MENDER\_STORAGE\_DEVICE} resizepart {MENDER\_DATA\_PART\_NUMBER} 100%

So if you define it you get a bunch of warnings if you don’t growfs doesn’t have a drive and fails.

Just getting rid of the warning will still be an issue because you can’t guarentee MENDER\_STORAGE\_DEVICE will match the correct drive. You would need to use something like the data partition’s uuid or maybe label.

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [November 24, 2019, 1:50pm UTC](https://hub.mender.io/t/mender-partuuid-and-mender-data-growfs-incompatible/1274/4 "2019-11-24T13:50:48Z")

</div>

Yeah, it sounds like the growfs logic needs to dynamically determine which device is used in the case mender-partuuid is enabled.