# No match between boot and root partitions

**URL:** <https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212>\
**Category:** General Discussions\
**Created:** [February 12, 2021, 12:55pm UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212 "2021-02-12T12:55:12Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![abhishek](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@abhishek](https://hub.mender.io/u/abhishek)\
**Post date:** [February 12, 2021, 12:55pm UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/1 "2021-02-12T12:55:12Z")

</div>

Hi all  
My sd card partition for my target board is as follows:  
/dev/mmcbkl0p1 – for kernel  
/dev/mmcbkl0p2 – for uboot  
/dev/mmcbkl0p3 – /  
/dev/mmcbkl0p4-- extra partition for dual boot

What changes need to be done in this partition scheme in order to meet the partition layout requirements of the mender. I understand that an extra partition for persistent data would be required. What else?  
As of now, while running mender daemon, it throws the following Error

ERRO[0000] Failed to read the current active partition: No match between boot and root partitions.: exit status 243

How to resolve this?

---

<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:** [February 12, 2021, 7:18pm UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/2 "2021-02-12T19:18:16Z")

</div>

Hi @abhishek,

The basics are covered [here](https://docs.mender.io/system-updates-debian-family/overview#partition-layout). Will the mechanics for a Yocto build are different, the underlying structures are similar.

Note that we don’t usually leave the kernel in a separate partition but rather stored as a file in the root filesystem. This ensures redundancy and rollback capability.

Without knowing more about your system, I would expect your partition structure to looks something like:

- /dev/mmcblk0p1 - UBoot (maybe not depending on how Uboot works on your device; on many platforms it is actually stored in unpartitioned space)
- /dev/mmcblk0p2 - root filesystem A
- /dev/mmcblk0p3 - root filesystem B
- /dev/mmcblk0p4 - data partition

Is there a reason you are doing this manually rather than using our [mender-convert](https://docs.mender.io/system-updates-debian-family) (for debian style systems) or [Yocto integrations](https://docs.mender.io/system-updates-yocto-project) which will set it up for you?

Drew

---

<div class="post-metadata">

**Author:** ![abhishek](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@abhishek](https://hub.mender.io/u/abhishek)\
**Post date:** [February 15, 2021, 6:18am UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/3 "2021-02-15T06:18:34Z")

</div>

> [@drewmoseley](#):
>
> rollback capability.

I am using U54 target board (RISC-V) where I have 3 partitions by default, bootloader, kernel and rootfs.  
I suspect mender-conver tool would be targeting ARM architecture. Will it recognise all 3 partitions? Can I use it create image for my target from by golden image?

I am currently building mender from source and able to transfer simple files. With filesystem update, it is creating this issue!

Thanks for your response

---

<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:** [February 15, 2021, 4:55pm UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/4 "2021-02-15T16:55:45Z")

</div>

I don’t know if mender-convert will support that board or not but I suspect there will be issues.  
It definitely won’t work with the kernel as a separate partition.  
You may be able to address both issues with a custom integration.

Building from source may get you a working system to transfer simple files. As you noted, doing the robust full image updates requires more effort.

Drew

---

<div class="post-metadata">

**Author:** ![abhishek](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@abhishek](https://hub.mender.io/u/abhishek)\
**Post date:** [February 15, 2021, 5:31pm UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/5 "2021-02-15T17:31:30Z")

</div>

Can you guide me where exactly I should dig further to solve this issue?  
I have managed to transfer simple file but this problem occurs while filesystem update. I have even tested by creating data partition but still got same error!  
Looks like uboot issue!

Thanks

---

<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:** [February 15, 2021, 6:39pm UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/6 "2021-02-15T18:39:22Z")

</div>

You will not be able to do a filesystem update without doing a full integration using either [mender-convert](https://docs.mender.io/system-updates-debian-family) or [Yocto](https://docs.mender.io/system-updates-yocto-project). Those doc links should get you started but it’s hard to say what issues you will face given that this is a new architecture.  
Drew

---

<div class="post-metadata">

**Author:** ![abhishek](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@abhishek](https://hub.mender.io/u/abhishek)\
**Post date:** [February 16, 2021, 1:12pm UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/7 "2021-02-16T13:12:49Z")

</div>

Mender-convert needs config file which is not available for my target board (u54). Can pi4 config file be used as sample to create config file in this command?

```auto
MENDER_ARTIFACT_NAME=release-1 ./docker-mender-convert \
    --disk-image input/golden-image-1.img \
    --config configs/raspberrypi3_config \
    --overlay rootfs_overlay_demo/

```

---

<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:** [February 16, 2021, 2:43pm UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/8 "2021-02-16T14:43:03Z")

</div>

Not likely. That is the config file that customizes mender-convert for your platform. You will need to determine what is needed for your platform and store it in a custom config file. That’s essentially what is needed for a mender-convert integration.

Drew

---

<div class="post-metadata">

**Author:** ![abhishek](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@abhishek](https://hub.mender.io/u/abhishek)\
**Post date:** [August 13, 2021, 11:10am UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/9 "2021-08-13T11:10:59Z")

</div>

Hi

 ![MicrosoftTeams-image (1)](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/1/162a17cfa98575bea748eeea56fa23fcef3d59d8.png)

When I have flashed golden image in pi, I could find kernel sitting within boot partition along with uboot but in documents, it is mentioned that kernel comes along with rootfs and uboot remains separate.  
Can you please clarify?

---

<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:** [August 13, 2021, 11:43am UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/10 "2021-08-13T11:43:41Z")

</div>

In this case, the kernel7.img file is actually a U-Boot binary. The proprietary firmware loads U-Boot which then loads the kernel off of the root filesystem.

Drew

---

<div class="post-metadata">

**Author:** ![abhishek](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@abhishek](https://hub.mender.io/u/abhishek)\
**Post date:** [August 13, 2021, 11:51am UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/11 "2021-08-13T11:51:44Z")

</div>

Can you please point out where exactly the kernel is located in rootfs?

 ![MicrosoftTeams-image (2)](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/f/fc3830787d8982061bb46b2ec495d147f261f253.png)

---

<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:** [August 13, 2021, 2:30pm UTC](https://hub.mender.io/t/no-match-between-boot-and-root-partitions/3212/12 "2021-08-13T14:30:32Z")

</div>

It’s in the boot directory.
