mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Victor BERTIN <vbertin@witekio.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Fail to register logical partition because it overlaps with the extended partition
Date: Mon, 4 Dec 2023 15:04:37 +0000	[thread overview]
Message-ID: <PAXP192MB12457D6FCCD50380EA71D63FA786A@PAXP192MB1245.EURP192.PROD.OUTLOOK.COM> (raw)

Hello All,

We are using Barebox v2022.12.0 on a MSC SM2S-IMX8MP SoM.

We witness an error happening when registering the first logical partition of our extended partition :
ERROR: New partition mmc2.4 (0x46600400-0xc68003ff) on mmc2 overlaps with partition mmc2.3 (0x46600200-0x466005ff), not creating it
ERROR: mmc2: Failed to register partition 4 on mmc2 (-22)

However, Linux does not complain and all partitions are properly registered :
[root@imx8-evo:~]# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
mmcblk2      179:0    0 14.6G  0 disk
|-mmcblk2p1  179:1    0   66M  0 part
|-mmcblk2p2  179:2    0    1G  0 part /
|-mmcblk2p3  179:3    0   34M  0 part /rwdisk/systemrw
|-mmcblk2p4  179:4    0    1K  0 part
|-mmcblk2p5  179:5    0    2G  0 part /rwdisk/app
|-mmcblk2p6  179:6    0  130M  0 part /var/log
`-mmcblk2p7  179:7    0   32M  0 part /rwdisk/conf
mmcblk2boot0 179:32   0    4M  1 disk
mmcblk2boot1 179:64   0    4M  1 disk

Since 84ea37e4580cabc2a49edc4e2c62b45a752771fc, extended partitions are registered with a size of 2 sectors. Our extended partition still manages to overlap with the first logical partition that it contains.
A simple trick is to reduce the registration size to 1 sector, however we are not sure of the side effects of such change.

Any idea why such issue could happen ?

Thanks in advance for your help,

Victor Bertin

Witekio GmbH is registered in Frankfurt. Registered office: Am Wartfeld 7 - 61169 Friedberg. Registered company number: HRB 95432. VAT number DE287400071
This message contains confidential information and is intended only for the individual(s) addressed in the message. If you aren't the named addressee, you should not disseminate, distribute, or copy this e-mail.

We continuously commit to comply with the applicable data protection laws and ensure fair and transparent processing of your personal data. Please read our privacy statement including an information notice and data protection policy for detailed information on our website.



             reply	other threads:[~2023-12-04 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 15:04 Victor BERTIN [this message]
2023-12-05 10:34 ` Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PAXP192MB12457D6FCCD50380EA71D63FA786A@PAXP192MB1245.EURP192.PROD.OUTLOOK.COM \
    --to=vbertin@witekio.com \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox