You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I attempted to build Maru OS branch 0.7 for Hammerhead following the official developer guide at https://maruos.com/docs/developer/. My host operating system is Void Linux, but I conducted the build within a Docker container using the pdsouza/maruos-devbox:maru-0.6 image, so the host OS should not be a factor.
The build failed at 99%, with an 'out of space' error and error messages related to mk2fs and e2fsdroid. I have confirmed that both my host OS and Docker have sufficient free space, indicating that the issue lies elsewhere.
Before posting this issue, I performed a preliminary Google search and found a user encountering a similar error who suspected a connection to btrfs, which happens to be my Docker storage backend. I remounted my Docker environment with an extfs storage backend and repeated the process, but the error persisted.
Please let me know if any further information is required. Thank you for your assistance.
[ 99% 72391/72392] Target system fs image: /var/ma...obj/PACKAGING/systemimage_intermediates/system.img
FAILED: /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system.img
/bin/bash -c "(mkdir -p /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/ /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates && rm -rf /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system_image_info.txt ) && (echo \"ext_mkuserimg=mkuserimg_mke2fs.sh\" >> /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_
intermediates/system_image_info.txt ) && (echo \"fs_type=ext4\" >> /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system_image_info.txt ) && (echo \"system_size=1073741824\" >> /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system_image_info.txt ) && (echo \"extfs_sparse_flag=-s\" >> /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system_image_info.txt ) && (echo \"squashfs_sparse_flag=-s\" >> /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system_image_info.txt ) && (echo \"selinux_fc=/var/maru/out/target/product/hammerhead/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin\" >> /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system_image_info.txt ) && (echo \"skip_fsck=true\" >> /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system_image_info.txt ) && (PATH=/var/maru/out/host/linux-x86/bin/:\$PATH build/make/tools/releasetools/build_image.py /var/maru/out/target/product/hammerhead/system /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system_image_info.txt /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system.img /var/maru/out/target/product/hammerhead/system /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/generated_system_image_info.txt || ( mkdir -p /var/maru/out/dist; cp /var/maru/out/target/product/hammerhead/installed-files.txt /var/maru/out/dist/installed-files-rescued.txt; exit 1 ) )"
error: failed to build /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system.img from /var/maru/out/target/product/hammerhead/system
Error: '['mkuserimg_mke2fs.sh', '-s', '/var/maru/out/target/product/hammerhead/system', '/var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system.img', 'ext4', 'system', '1073741824', '-j', '0', '-D', '/var/maru/out/target/product/hammerhead/system', '-L', 'system', '-M', '0', '/var/maru/out/target/product/hammerhead/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin']' failed with exit code 4:
MKE2FS_CONFIG=./system/extras/ext4_utils/mke2fs.conf mke2fs -O ^has_journal -L system -m 0 -E android_sparse -t ext4 -b 4096 /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system.img 262144
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 262144 4k blocks and 65536 inodes
Filesystem UUID: 8bc5128a-e93c-45b1-b3a0-bfd336e2283c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
e2fsdroid -p /var/maru/out/target/product/hammerhead/system -S /var/maru/out/target/product/hammerhead/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin -f /var/maru/out/target/product/hammerhead/system -a /system /var/maru/out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system.img
__populate_fs: Could not allocate block in ext2 filesystem while writing file "LatinIME.apk"
e2fsdroid: Could not allocate block in ext2 filesystem while populating file system
Out of space? The tree size of /var/maru/out/target/product/hammerhead/system is 1092419584 bytes (1041 MB), with reserved space of 0 bytes (0 MB).
The max image size for filsystem files is 1073741824 bytes (1024 MB), out of a total partition size of 1073741824 bytes (1024 MB).
ninja: build stopped: subcommand failed.
06:45:55 ninja failed with: exit status 1
#### failed to build some targets (25:17 (mm:ss)) ####
The text was updated successfully, but these errors were encountered:
Description:
I attempted to build Maru OS branch 0.7 for Hammerhead following the official developer guide at https://maruos.com/docs/developer/. My host operating system is Void Linux, but I conducted the build within a Docker container using the
pdsouza/maruos-devbox:maru-0.6
image, so the host OS should not be a factor.The build failed at 99%, with an 'out of space' error and error messages related to mk2fs and e2fsdroid. I have confirmed that both my host OS and Docker have sufficient free space, indicating that the issue lies elsewhere.
Before posting this issue, I performed a preliminary Google search and found a user encountering a similar error who suspected a connection to btrfs, which happens to be my Docker storage backend. I remounted my Docker environment with an extfs storage backend and repeated the process, but the error persisted.
Please let me know if any further information is required. Thank you for your assistance.
The text was updated successfully, but these errors were encountered: