# Cannot access /data/u-boot in linux on integrating mender?

**URL:** <https://hub.mender.io/t/cannot-access-data-u-boot-in-linux-on-integrating-mender/832>\
**Category:** General Discussions\
**Tags:** beaglebone-black\
**Created:** [July 17, 2019, 2:12pm UTC](https://hub.mender.io/t/cannot-access-data-u-boot-in-linux-on-integrating-mender/832 "2019-07-17T14:12:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![amd](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@amd](https://hub.mender.io/u/amd)\
**Post date:** [July 17, 2019, 2:12pm UTC](https://hub.mender.io/t/cannot-access-data-u-boot-in-linux-on-integrating-mender/832/1 "2019-07-17T14:12:34Z")

</div>

I am working on yocto and integrating mender with it. Currently, my distro has two data parititions one contains **/data/U-boot** and other contains **/data/mender**. The data partition contaning mender overlays the U-boot data partition and I need to unmount the mender data partition to get access to u-boot. How can I merge these two data partitions? I have configured my data partition as **mmcblk0p6** in local.conf file. My **fstab** looks like this:

```auto
# stock fstab - you probably want to override this with a machine specific one

/dev/root / auto defaults 1 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
tmpfs /run tmpfs mode=0755,nodev,nosuid,strictatime 0 0
tmpfs /var/volatile tmpfs defaults 0 0

# uncomment this if your device has a SD/MMC/Transflash slot
#/dev/mmcblk0p1 /media/card auto defaults,sync,noauto 0 0

# Where the U-Boot environment resides; for devices with SD card support ONLY!
/dev/mmcblk0p1 /uboot auto defaults,sync 0 0
/dev/mmcblk0p6 /data auto defaults 0 0

```

---

<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:** [July 17, 2019, 3:48pm UTC](https://hub.mender.io/t/cannot-access-data-u-boot-in-linux-on-integrating-mender/832/2 "2019-07-17T15:48:46Z")

</div>

Hi @amd. Welcome to Mender hub.

From the looks of your fstab, the uboot partition should be mounted at /uboot, assuming it is on /dev/mmcblk0p1. But you also have that partition set to be mounted at /media/card so I’m not sure what specifically we are looking at.

What partition device node is the **/data/U-boot** partition?

Drew

---

<div class="post-metadata">

**Author:** ![amd](https://avatars.discourse-cdn.com/v4/letter/a/46a35a/32.png) [@amd](https://hub.mender.io/u/amd)\
**Post date:** [July 17, 2019, 8:20pm UTC](https://hub.mender.io/t/cannot-access-data-u-boot-in-linux-on-integrating-mender/832/3 "2019-07-17T20:20:07Z")

</div>

Hello Drew,

Thank you for your response. I am sorry, a small mistake the /media/card is actually commented out which I have edited and the /data/uboot and /data/mender are in the same partition mmcblk0p6. That is why I am confused.

Kind Regards,  
Amod

---

<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:** [July 17, 2019, 9:46pm UTC](https://hub.mender.io/t/cannot-access-data-u-boot-in-linux-on-integrating-mender/832/4 "2019-07-17T21:46:25Z")

</div>

I’m still not sure what issue you are seeing. What are your MENDER\_\* variables defined as in local.conf?Is /dev/mmcblk0p6 the data partition that was created by the meta-mender logic or is that a separate partition?

When the system is booted can you show the output of the “mount” command and explain what you want to see instead?