© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
That's a good use/reason for customizing your own Ubuntu ISO.
The question is, how to solve the issue you are having?...
If your ISO is 26Gb, I'm sure the final install would be much larger when the compressed Linux file system is extracted during installation. However, your logs show that you are only using 43.70GB out of 100.00GB available in your virtual machine.
So the, "No space left on device" error must be caused by something else:
(1)
One possible cause is that you are running out of inodes, as this URL explains:
https:/
If you have more than 45,000 files, this could be the culprit.
I'm not sure if there is something I can change in Cubic to help with this problem. (It may have something to do with your host machine or how your *.vdi is formatted). Nevertheless, I'll research the block size when Cubic generates the ISO file. I ~think~ having a larger block size may use less inodes, but the image size becomes greater. I'll investigate this further.
(2)
Another possibility is that you are running out of RAM in your virtual machine.
Researching VirutalBox and Live ISOs, I've come across threads implying that, while you are running a Live environment, the actual disk is not used. Instead, RAM is used to simulate disk space. I think you've set the virtual machine to use 2.6GB. That's a lot, but it may not be enough during the installation process.
Would it be possible to allocate more RAM to your VM and do a test? (I think your host computer has about 6GB. May be you can try allocating up to 4.5GB or 5GB to the VM as an experiment?
Please let me know if you try that test, and I'll continue to do more research on item 1.