ERROR: Starting LBA overlaps

[maxdruiz]

Im using a Pixelbook Go with the default options and get the error:

Unmounting stateful partition...
Editing partition table...
ERROR: Starting LBA overlaps
ERROR: -i 1 -l STATE -b 17092608 -s 10485760

Output of lsblk:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 315.8M 0 loop
-encstateful 253:1 0 315.8M 0 dm /mnt/stateful_partition/encrypted loop1 7:1 0 486.1M 1 loop /opt/google/containers/android/rootfs/root loop2 7:2 0 4K 1 loop /opt/google/containers/arc-sdcard/mountpoints/container-root loop3 7:3 0 4K 1 loop /opt/google/containers/arc-obb-mounter/mountpoints/container-root loop4 7:4 0 9.2M 1 loop /usr/share/chromeos-assets/quickoffice/_platform_specific loop5 7:5 0 58.6M 1 loop sda 8:0 1 28.7G 0 disk -sda1 8:1 1 28.7G 0 part /media/removable/USB Drive
mmcblk0 179:0 0 58.2G 0 disk
|-mmcblk0p1 179:1 0 1.1G 0 part /mnt/stateful_partition
|-mmcblk0p2 179:2 0 16M 0 part
|-mmcblk0p3 179:3 0 4G 0 part
|-mmcblk0p4 179:4 0 16M 0 part
|-mmcblk0p5 179:5 0 4G 0 part
|-mmcblk0p6 179:6 16M 0 part
|-mmcblk0p8 179:8 16M 0 part /usr/share/oem
|-mmcblk0p9 179:9 512B 0 part
|-mmcblk0p10 179:10 512B 0 part
|-mmcblk0p11 179:11 8M 0 part
`-mmcblk0p12 179:12 32M 0 part
mmcblk0boot0 179:16 0 4M 1 disk
mmcblk0boot1 179:32 0 4M 1 disk
mmcblk0rpmb 179:48 0 16M 0 disk
zram0 252:0 0 11.3G 0 disk [SWAP]

Originally posted by @maxdruiz in #3 (comment)

[ethanmad]

Hi @maxdruiz, I don't have the time to figure this out at this moment. I haven't tried this script on Chromebooks in recent years and I'm not sure if there have been some changes to disk layout or similar. If not, unit conversions (B <--> GiB) and arithmetic should be all that's needed to understand what's going on, if you want to try yourself.

Otherwise, you might try resizing with chrx or parted instead and see if those work without issues.

Feel free to report back and share your findings or what works. :)

[tlh24]

Trip report, for those who may have found this via searching:

I tried this, and while it gave the same error, the script did modify the partition table & successfully made empty space after the stateful partition.

Subsequently booted into a gparted live image, made an ext4 partition (#13) in the free space, rebooted, and allowed ChromeOS to repair itself.

Following this, I booted into a Debian live image and installed Linux on the new partition. After fiddling with edk2 bootloader to properly register the location of grub.efi, I now have a dual boot chromebook! So: it is possible to switch between Linux and ChromeOS with the built-in legacy firmware, which was enabled through Mr.Chromebox's scripts. ChromeOS seems to tolerate the 13th partition just fine.