mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Charles Steinkuehler <>
Subject: [RAUC] RAUC Install issue with disk partitioning
Date: Thu, 10 Mar 2022 16:50:42 -0600	[thread overview]
Message-ID: <> (raw)

I am working through my Buildroot + RAUC example project[1] and after 
modifying the HDD partitioning I can no longer install updates to the 
boot partition however updates to the rootfs partition still work.

My boot filesystem is using boot-mbr-switch and it seems to be getting 
confused by the fact that I have extended partitions but no primary 
partition #4.  The partition layout is:

P1 = Boot loader (with space reserved for boot-mbr-switch)
P2 = Rescue partition
P3 = Extended partition
P4 = <unused>
E5 = Rootfs.0
E6 = Rootfs.1
E7 = Uploads (bulk data, unsafe across reboots)
E8 = Persistent data (fully journaled, safe)

When I attempt to update the bootfs, I get the following.  The exact 
same commands worked before I changed the partition layout (adding the 
rescue & upload partitions, forcing the use of an extended partition table):

$ rauc install /mnt/bootfs.raucb
   0% Installing
   0% Determining slot states
  20% Determining slot states done.
  20% Checking bundle
  20% Verifying signature
  40% Verifying signature done.
  40% Checking bundle done.
  40% Checking manifest contents
  60% Checking manifest contents done.
  60% Determining target install group
  80% Determining target install group done.
  80% Updating slots
  80% Checking slot bootloader.0
  90% Checking slot bootloader.0 done.
  90% Copying image to bootloader.0
100% Copying image to bootloader.0 failed.
100% Updating slots failed.
100% Installing failed.
LastError: Installation error: Failed updating slot bootloader.0: Region 
start address 0x400000 is in area of partition 4 (0x0 - 0xffffffffffffffff)
Installing `/mnt/bootfs.raucb` failed
$ sudo fdisk -ul /dev/mmcblk0
Disk /dev/mmcblk0: 59 GB, 63864569856 bytes, 124735488 sectors
1948992 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device       Boot StartLBA     EndLBA    Sectors  Size Id Type
/dev/mmcblk0p1 *      8192     532479     524288  256M  c Win95 FAT32 (LBA)
/dev/mmcblk0p2     1056768    1581055     524288  256M 83 Linux
/dev/mmcblk0p3     1581056    7372803    5791748 2828M  f Win95 Ext'd (LBA)
/dev/mmcblk0p5     1581057    3424256    1843200  900M 83 Linux
/dev/mmcblk0p6     3424258    5267457    1843200  900M 83 Linux
/dev/mmcblk0p7     5267459    7110658    1843200  900M 83 Linux
/dev/mmcblk0p8     7110660    7372803     262144  128M 83 Linux

Any idea why rauc is complaining that an unused partition overlaps my 
boot partition?

I'll probably just shuffle things around and move the persistent data 
partition to P3 and let the extended partition table take P4, but this 
seems like it's a bug.


Charles Steinkuehler

RAUC mailing list

             reply	other threads:[~2022-03-10 22:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 22:50 Charles Steinkuehler [this message]
2022-03-11  2:33 ` Charles Steinkuehler

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:

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

  git send-email \ \ \ \

* 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