Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[raspberrypi,4-model-b] | Error building the firmware image #790

Open
mrinmaydhar opened this issue Apr 9, 2024 · 3 comments
Open

[raspberrypi,4-model-b] | Error building the firmware image #790

mrinmaydhar opened this issue Apr 9, 2024 · 3 comments

Comments

@mrinmaydhar
Copy link

Server response: Error: Selected packages exceed device storage

Request Data:
Request Data.json

STDOUT:
STDOUT.txt

STDERR:
STDERR.txt

error: ext4_allocate_best_fit_partial: failed to allocate 2246 blocks, out of space?
make[3]: *** [/builder/include/image.mk:350: /builder/build_dir/target-aarch64_cortex-a72_musl/linux-bcm27xx_bcm2711/root.ext4] Error 1
make[2]: *** [Makefile:208: build_image] Error 2
make[1]: *** [Makefile:146: _call_image] Error 2
make: *** [Makefile:262: image] Error 2

@mrinmaydhar
Copy link
Author

#784 similar error. If required, can close this as duplicate (however the error is different in this case)

Moreover, current squashfs usage is 94.13MiB / 1.68GiB (5%). If this is cause for issue, please do let me know. Thank you

@RicardoJCMarques
Copy link

I've got the same error trying to upgrade Snapshot on a RP5.. I'm just getting used to openwrt but I expanded the default partition size on my sd-card. Guessing that might have something to do with this? Does it need a bigger boot partition too?

@mrinmaydhar
Copy link
Author

As mentioned by @aparcar here, the default root allocation is for 100MB, and any expand operations that are performed are after the fact (after initial boot, etc.). So, expanding the boot partition would not be of help (90% sure).

If an attended sysupgrade is something of a priority, then you could remove some packages that you don't need.

I, however, have a custom build environment setup to deal with this limitation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants