Compiling OPNSense failing due to missing file during vga build step

[Shady Dave]

Hello! I have been working on getting OPNSense to compile as a learning experience and so I can tinker. I managed to figure out solutions to all the issues I had along the way until now.

I've got it compiling all the way to the vga build step, which I presume is packaging. I get the following output:

Code Select Expand

>>> Running build step: vga
>>> Passing arguments: (none)
>>> Removing vga image
>>> Setting up stage in /usr/obj/usr/tools/config/24.1/amd64
>>> Setting up base in /usr/obj/usr/tools/config/24.1/amd64/work
>>> Setting up kernel in /usr/obj/usr/tools/config/24.1/amd64/work
./boot/kernel/wlan.ko : Lzma library error: No progress is possible: No such file or directory
tar: Error exit delayed from previous errors.
*** Error code 1

Stop.
make: stopped in /usr/tools

I checked to make sure usr/obj/usr/tools/config/24.1/amd64/work/boot/kernel/wlan.ko exists, but the error persists. It also happens if I try make dvd.

I am a bit stumped since the file appears to exist at the path it appears to be looking at. I can't seem to find anything similar to this issue with search here or on the web.

Note, this is a fresh FreeBSD 13.2 install without ports or kernel source tree, everything fetched from the tools repository and then via the make update command.

[Shady Dave]

Just going to update this - I guess it was failing because my disk was too small. I thought a 118GB Optane P1600X with a fresh FreeBSD installation would be enough space for this.

The partition reported 80GB free space, but it still failed. I moved to a 500GB SSD and the compile worked without issue.

[john314]

Hmm, I would think your 118GB should be enough.

I created a VM (under proxmox), with a 100GB disk, installed a fresh FreeBSD 13.2-Release, and then built opnsense similar to how you did (I am also a newbie just starting to tinker/learn opnsense).   But, I did "make serial", although I wouldn't expect that to matter much. After some build issues related to a python library ports bug were resolved, I did a build yesterday in this VM successfully.  After the build is done, my VM disk usage is sitting at only 33% of 100GB.  I'm not sure if the disk usage spikes significantly higher during the build or not. 

I will reset my VM and try doing "make vga", to see if I can reproduce your error.

-John

[john314]

My build using "make vga" completed successfully last night.  The 100GB hard disk for my VM is showing only 33% usage after the build.