mindwave Posted August 11, 2007 Report Share Posted August 11, 2007 Copyright © 2002-2004, Jaco Greeff <jaco@puxedo.org> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. Creating initrd: [ 95.51% 00:00:03/00:00:03]sh: line 1: 7782 Broken pipe /bin/zcat //tmp/initrd.gz 2>/dev/nulltmp/mklivecd.7622/livecd/isolinux/ ... 7783 Segmentation fault | /bin/cpio -t >&/dev/null bootsplash not found in //tmp/initrd.gz [100.00% 00:00:08/00:00:08] running: chkconfig --add harddrake with root / Setting filesystem parameters: [100.00% 00:00:46/00:01:17] Creating compressed image: [100.00% 00:23:05/00:23:23] Creating isolinux boot: [100.00% 00:00:01/00:00:01] Creating final iso: [100.00% 00:00:00/00:00:00] ls: dvd.iso: No such file or directory Argument "" isn't numeric in division (/) at /usr/sbin/mklivecd line 230. Created 'dvd.iso' (0,000 bytes) in 00:26:12 any ideas? Quote Link to comment Share on other sites More sharing options...
chris:b Posted August 11, 2007 Report Share Posted August 11, 2007 (edited) What has virtualbox to do with building an iso? You don't have enough space for building a dvd iso or the size is too big or something like that. I can't help with building these huge images. I always try to build live isos as small as possible. :D If you see error messages, please provide the 'full' build command that you use. Also the output of df. Edited August 11, 2007 by chris:b Quote Link to comment Share on other sites More sharing options...
mindwave Posted August 11, 2007 Author Report Share Posted August 11, 2007 thats interesting because it just started after the vbox install its a 53gb drive, that has been yielding 1.2gb ISO's only 11gb shows used, but that still too big, wonder whats taking all the space. the command line is: mklivecd --verbose dvd.iso Quote Link to comment Share on other sites More sharing options...
mindwave Posted August 11, 2007 Author Report Share Posted August 11, 2007 well SOMEThing has certainly increased my "size" just a properties of the working dirs shows 4.4gb which is MUCH bigger than it used to be Quote Link to comment Share on other sites More sharing options...
mindwave Posted August 11, 2007 Author Report Share Posted August 11, 2007 you know it seems to me that failed builds, used to build up somewhere, but now i'm not finding them in my tmp dirs..... Quote Link to comment Share on other sites More sharing options...
chris:b Posted August 11, 2007 Report Share Posted August 11, 2007 only 11gb shows used, but that still too big, wonder whats taking all the space. 11 GB ? Wow. These can't be installed applications. 11 GB is too much to build a live dvd. The compression rate is 35 - 40 %. Your final iso is just too big. Check your installation, old isos lying around, or video files or music files. Clean the stuff. You should never start a mklivecd build command without performing a df on the target system. Quote Link to comment Share on other sites More sharing options...
chris:b Posted August 11, 2007 Report Share Posted August 11, 2007 Failed builts are in /tmp/mklivecd.XXX Delete them all. And you sure have some old isos, somewhere. When you work as a user they are in your /home/user directory. Unless you opened a terminal in a different directory. Quote Link to comment Share on other sites More sharing options...
chris:b Posted August 11, 2007 Report Share Posted August 11, 2007 And in case you have created a vbox image, a virtual disk image, start Virtual Box, go to: File --> Virtual Disk manager, and delete this big image. You may want to corntrol, where you created the vdisk, most likely in in the invisible /home/user/.VirtualBox --> look at the sub dirs. Quote Link to comment Share on other sites More sharing options...
mindwave Posted August 12, 2007 Author Report Share Posted August 12, 2007 well i did a search for iso' and there arent any. i killed the vbox image before i started, so now i have to look through the temos, strangely enough, even though it starts to say it is, it never does write the final iso Quote Link to comment Share on other sites More sharing options...
Recommended Posts