Skip to content

Rootfs size exceeds maximum limit while building OpenBMC for Intel S2600GZ #4041

@tcsk12

Description

@tcsk12

Title of the Issue
Build Error: Rootfs size exceeds maximum limit while building OpenBMC

Problem Description
While attempting to build OpenBMC for the "olympus-nuvoton" as target on a host which is an Intel Server running with Ubuntu 24 OS, I encountered errors related to exceeding the maximum rootfs size during the build process. The build fails when executing the do_image_squashfs_xz and do_image_cpio tasks. Despite rebuilding, the errors persist, and I’m not sure how to proceed. I wanted to bring up the OpenBMC in the QEMU.

Error Statement
ERROR: obmc-phosphor-image-1.0-r0 do_image_squashfs_xz: The rootfs size 112664(K) exceeds IMAGE_ROOTFS MAXSIZE: 32768(K)

ERROR: obmc-phosphor-image-1.0-r0 do_image_cpio: The rootfs size 112664(K) exceeds IMAGE_ROOTFS MAXSIZE: 32768(K)

Warnings:
WARNING: obmc-phosphor-image-1.0-r8 do_rootfs: Group render has never been defined

WARNING: systemd-1_257.1-ro do_install: Using /home/root as root user's home directory is not fully supported by systemd

WARNING: systemd-1_257.1-re do_package: systemd: NOT adding alternative provide /usr/sbin/init: ${rootlibexecdir}/systemd/systemd does not exist

Additional Error after Rebuild:
ERROR: obmc-phosphor-image-1.0-r0 do_generate_static: Image '/home/olympus-nuvoton/openbmc/build/olympus-nuvoton/tmp/work/olympus_nuvoton-openbmc-linux-gnueabi/obmc-phosphor-image/1.0/deploy-obmc-phosphor-image-image-complete/obmc-phosphor-image-olympus-nuvoton.squashfs-xz' is 1953792 bytes too large!

ERROR: Task (/home/olympus-nuvoton/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_generate_static) failed with exit code '1'

What I Tried
-I attempted to rebuild OpenBMC multiple times, but the errors persist.
-I’ve checked the configuration files and verified the IMAGE_ROOTFS_MAXSIZE variable, but increasing it did not resolve the issue.
-I attempted to reduce the size of the root filesystem by removing unused components from the image, but that didn’t help.
-I verified that all required dependencies were installed for the build environment.

Expected Behavior
-I expected the build to complete successfully without the errors related to rootfs size or any other issues.

System Configuration
Hardware: Intel S2600GZ motherboard
OS: Ubuntu 24 (64-bit)
Memory (RAM): 62GB
Disk Space:
Total disk space: 916GB
Used space: 65GB
Available space: 805GB

Build Environment
OpenBMC Version: Latest version
Bitbake Version: BitBake Build Tool Core version 2.9.1

System Information:
RAM:
Total: 62GB
Used: 5.8GB
Free: 44GB
Available: 56GB
Disk Space:
Filesystem Size Used Avail Use% Mounted on
tmpfs 6.3G 2.7M 6.3G 1% /run
/dev/sdb1 916G 65G 805G 8% /
tmpfs 32G 4.0K 32G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sda2 219G 18G 191G 9% /media/Intel_Disk
tmpfs 6.3G 2.6M 6.3G 1% /run/user/1000

Steps to Reproduce
-Clone the OpenBMC repository.
-Run the bitbake obmc-phosphor-image command.
-The build fails during the do_image_squashfs_xz and do_image_cpio tasks, resulting in the rootfs size error.

Request for Assistance
I kindly request your help in identifying the root cause of these errors. Any guidance on how to fix the rootfs size issue, the systemd warnings, or the missing render group would be greatly appreciated. I am looking for any insights or solutions that might help resolve this build failure.

Thank you for your time and support!

Additional Context
The build environment is running Ubuntu 24 with all necessary dependencies installed. Despite rebuilding and adjusting various configurations, I am unable to resolve these issues. I am running this build on a Intel S2600GZ platform.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions