Hi Alex,
As regards to a larger RESIN_BOOT_SIZE
, no dice, still the same error, with and without setting the other Size and Maxsize parameters.
Copying files into the device: __populate_fs: Could not allocate block in ext2 filesystem while writing file "Image"
mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system
Deleted: sha256:e25e84397823c824d1823092d9c5b1b32326572d299c32dd4ce7bb2bd130d6c1
Deleted: sha256:b39ac24be79db4c4188f6498a176d79d9e8d37f6c82a0d03e81b801265aa87ae
Deleted: sha256:3c1c6f550ee188271fd448b2ad4830902d60994b86ae25727ebe1db432560670
WARNING: exit code 1 from a shell command.
Further, I’ve broken it in a novel way. I spent some time reviewing the recent livestream that you guys recommended on building BalenaOS, and the most notable piece was that my recipes-core/images/resin-image.bbappend
had previously contained almost nothing based on what I could get out of the docs, just:
IMAGE_FSTYPES_nanopi-neo3 = "resinos-img"
RESIN_IMAGE_BOOTLOADER = "u-boot"
To this I’ve added, based on what I could garner from other repositories and an attempt at removing these size and allocation errors:
IMAGE_ROOTFS_MAXSIZE = "50000000"
RESIN_BOOT_PARTITION_FILES_nanopi-neo3 = " \
${KERNEL_IMAGETYPE}${KERNEL_INITRAMFS}-${MACHINE}.bin:/${KERNEL_IMAGETYPE} \
rk3328-nanopi-r2-rev00.dtb:/dtb/rk3328-nanopi-r2-rev00.dtb \
"
(I recognize that this needs references to at least u-boot in here as well, but some of my previous u-boot issues resulted in this dtb not being built - I’m going to dive back into this and see if I can figure out why in the meantime).
At any rate, the good news is this was perhaps the source of the warning about resin-image-initramfs. I am still failing though, in do_rootfs:
Install resin-boot in the rootfs...
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/rootfs/r>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/Image' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/ro>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/dtb' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/root>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/dtb/rk3328-nanopi-r2-rev00.dtb' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-li>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/splash' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/r>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/splash/balena-logo.png' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resi>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/os-release' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0->
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/device-type.json' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-imag>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/system-connections' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-im>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/system-connections/resin-sample.ignore' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/system-connections/README.ignore' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky->
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/resin-image' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/image-version-info' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-im>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/config.json' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0>
'/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-image/1.0-r0/resin-boot/resinos.fingerprint' -> '/home/ubuntu/development/yocto/balena-nanopineo3/build/tmp/work/nanopi_neo3-poky-linux/resin-i>
NOTE: resin-boot: FAT overhead 1034 sectors, data 66002 sectors, largest file 65814 sectors, boot size 81920 sectors.
ERROR: resin-boot: Not enough space for atomic copy operations.
Any suggestions? Still seems as if this is size related somehow, but hoping that this reference to atomic copy operations is informative in hunting down where. Thanks in advance