No space left on device when building image

[5p0ng3b0b]

Tried
sudo bash croissant.sh chromium.img recovery.bin swtpm.tar
chromium.img was arnoldthebats Camd64OS_R85-13310.B-Special.7z
recovery.bin was chromeos_13421.99.0_eve_recovery_stable-channel_mp-v2.bin
Looked like it was working until.......

Copying ChromeOS system files...
          1.88G  99%    4.61MB/s    0:06:29 (xfr#10230, to-chk=0/13228)
Copying kernel modules...
        385.41M  66%   17.63MB/s    0:00:20 (xfr#1204, ir-chk=1010/2347)
rsync: write failed on "/home/chronos/local/lib/firmware/ql2400_fw.bin": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]
        124.64M  93%  165.27MB/s    0:00:00 (xfr#6, to-chk=0/10)
rsync: write failed on "/home/chronos/local/usr/lib64/dri/kms_swrast_dri.so": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]
Is your wireless card bcm43xx? Answer no if unsure (y/n)
n
Is it ath10k? Answer no if unsure (y/n)
n
Is your computer MacBook/Pro/Air? (y/n)
n

Leave selinux on enforcing? (Won't break SafetyNet without developer mode, but might cause issues with android apps)
Answer no if unsure (y/n)
n
Copying TPM 2 emulator...
cp: error writing '/home/chronos/local/usr/sbin/swtpm_setup.sh': No space left on device
cp: error writing '/home/chronos/local/usr/lib64/libswtpm_libtpms.a': No space left on device
cp: error writing '/home/chronos/local/usr/lib64/libswtpm_libtpms.la': No space left on device
cp: error writing '/home/chronos/local/usr/lib64/libswtpm_libtpms.so.0.0.0': No space left on device
cp: error writing '/home/chronos/local/usr/lib64/libtpm_unseal.so.1.0.0': No space left on device
cp: error writing '/home/chronos/local/usr/lib64/libtpms.a': No space left on device
cp: error writing '/home/chronos/local/usr/lib64/libtpms.la': No space left on device
cp: error writing '/home/chronos/local/usr/lib64/libtpms.so.0.6.0': No space left on device
cat: write error: No space left on device
sed: couldn't write 66 items to /home/chronos/local/usr/sbin/sedQrbR61: No space left on device
sed: couldn't write 66 items to /home/chronos/local/usr/sbin/sedn83A76: No space left on device
sed: couldn't write 37 items to /home/chronos/local/usr/sbin/sedQNLw1o: No space left on device

ChromeOS image created: this is for personal use only, distribute at your own risk

There is 60gb free space on the drive these files are on, Is there something I am doing wrong?

[5p0ng3b0b]

The problem for me was because the ROOT-A partition of the source disk/image needed to be 3GB instead of 2. I dd'd chromium.img to usb then corrected size in gparted and wrote usb back to image file. I was then able to apply the script to both usb and image. The ROOT-A partition reports 2.56GB is used of the 3GB when finished. Whilst this fixed my problem, perhaps the script failed to delete a folder or something causing the partition to run out of space, or perhaps the script could be altered to expand the ROOT-A partition (it might already). Anyhow, the image booted. Thanks for sharing.

[mesbahulalam]

Thanks for the solution

The problem for me was because the ROOT-A partition of the source disk/image needed to be 3GB instead of 2. I dd'd chromium.img to usb then corrected size in gparted and wrote usb back to image file. I was then able to apply the script to both usb and image. The ROOT-A partition reports 2.56GB is used of the 3GB when finished. Whilst this fixed my problem, perhaps the script failed to delete a folder or something causing the partition to run out of space, or perhaps the script could be altered to expand the ROOT-A partition (it might already). Anyhow, the image booted. Thanks for sharing.

Thanks for the solution. At the time of writing this, version 91 is on the stable channel. The few images I tried to chromefy, all of them had this issue. Maybe a partition size check should be added to the script to overcome this. Or we can go bug ArnoldTheBat to increase the partition sizes in his base builds.

[nxvvvv]

@5p0ng3b0b Hey, pls help with your solution. I don't have much experience, so if you could tell me the steps, it would be a great help :).

[goetzerich]

@navaneethkm004 Here's what I did, using a Linux box:

(1) I took the arnoldthebat image and used etcher to write it to a 8GB (or larger) USB.
(2) I then opened the USB in GParted and manually moved the last partition to create more room for the ROOT-A partition, and then increased the size of the ROOT-A partition to at least 4GB
(3) I then used dd to create a new image sudo dd if=/dev/sdX of=new_image.img bs=16M
Note: You may need to decompress the resulting image #file.
(4) Run the script using the new image sudo bash croissant.sh new_image.img recovery.bin swtpm.tar

I'm sure there are more elegant ways of doing this, but this worked for me.