How to recover from out of disk space error?

Printable View

2018-01-01
BHReach

How to recover from out of disk space error?

I installed kali in virtualbox. Not knowing how much space I needed, I created a disk size of 25GB. The automatic partitioning mechanism created 8GB of swap and 17GB for kali.

I installed and updated kali. I added a few packages (the Nvidia and CUDA stuff) and followed the instructions for building a custom ISO.

I ran

Code:

./build.sh --distribution kali-rolling --verbose

It finished with errors. Here is the section of the build.log that shows the errors:

Code:

(Reading database ... 100% (Reading database ... 19932 files and directories currently installed.) Preparing to unpack .../0-mariadb-server-10.1_1%3a10.1.29-6_amd64.deb ... ERROR: There's not enough space in /var/lib/mysql/ dpkg: error processing archive /tmp/apt-dpkg-install-fkrfKd/0-mariadb-server-10.1_1%3a10.1.29-6_amd64.deb (--unpack): new mariadb-server-10.1 package pre-installation script subprocess returned error exit status 1 Selecting previously unselected package libjudydebian1. Preparing to unpack .../1-libjudydebian1_1.0.5-5_amd64.deb ... Unpacking libjudydebian1 (1.0.5-5) ... Selecting previously unselected package miredo. Preparing to unpack .../2-miredo_1.2.6-4_amd64.deb ... Unpacking miredo (1.2.6-4) ... Selecting previously unselected package libfuse2:amd64. Preparing to unpack .../3-libfuse2_2.9.7-1_amd64.deb ... Unpacking libfuse2:amd64 (2.9.7-1) ... Selecting previously unselected package fuse. Preparing to unpack .../4-fuse_2.9.7-1_amd64.deb ... Unpacking fuse (2.9.7-1) ... Selecting previously unselected package libntfs-3g88. Preparing to unpack .../5-libntfs-3g88_1%3a2017.3.23-2_amd64.deb ... Unpacking libntfs-3g88 (1:2017.3.23-2) ... Errors were encountered while processing: /tmp/apt-dpkg-install-fkrfKd/0-mariadb-server-10.1_1%3a10.1.29-6_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) P: Begin unmounting filesystems... P: Saving caches... Reading package lists... Building dependency tree... Reading state information...

It took hours for this whole process. If I increase the disk size in virtualbox (by how much?), is there a way to continue building the custom ISO from where it left off or do I have to start from scratch?
2018-01-01
Mister_X

I would recommend using the provided virtual machine images. However, if you insist on using your own, first delete that whole directory and then find out where the 17GB is mounted to then work there. 17Gb should be plenty to build an ISO.
2018-01-02
BHReach

Quote:

Originally Posted by Mister_X

I would recommend using the provided virtual machine images. However, if you insist on using your own, first delete that whole directory and then find out where the 17GB is mounted to then work there. 17Gb should be plenty to build an ISO.

I started over and used kali-linux-2017.3-vbox-amd64 image.

What follows is the error and resulting failure of the creation of the ISO.

It looks like a file on the mirror is corrupted.

How can I recover from this error?

Can I get the file from a different mirror, put it in the correct location and continue the ISO creation process from where it stopped?

Code:

[2018-01-02 13:03:29] lb chroot_archives chroot install P: Configuring file /etc/apt/sources.list Get:1 http://archive.kali.org/kali kali-rolling InRelease [30.5 kB] Get:2 http://archive.kali.org/kali kali-rolling/contrib Sources [64.7 kB] Get:3 http://archive.kali.org/kali kali-rolling/main Sources [11.7 MB] Get:4 http://archive.kali.org/kali kali-rolling/non-free Sources [121 kB] Get:5 http://archive.kali.org/kali kali-rolling/main amd64 Packages [15.7 MB] Err:5 http://archive.kali.org/kali kali-rolling/main amd64 Packages File has unexpected size (15689050 != 15689042). Mirror sync in progress? Hashes of expected file: - Filesize:15689042 [weak] - SHA256:68125eb0dac5029179ce131b06213d6487bb11b0686147475886bfefec6df1aa - SHA1:182ff26033750e7fc0349d9ae8e26df5344de5be [weak] - MD5Sum:7bcc1d8f4c395ef397d0c8ffc4c4ed40 [weak] Release file created at: Tue, 02 Jan 2018 12:06:51 +0000 Fetched 11.9 MB in 1min 53s (105 kB/s) Reading package lists... E: Failed to fetch http://archive.kali.org/kali/dists/kali-rolling/main/binary-amd64/Packages.gz File has unexpected size (15689050 != 15689042). Mirror sync in progress? Hashes of expected file: - Filesize:15689042 [weak] - SHA256:68125eb0dac5029179ce131b06213d6487bb11b0686147475886bfefec6df1aa - SHA1:182ff26033750e7fc0349d9ae8e26df5344de5be [weak] - MD5Sum:7bcc1d8f4c395ef397d0c8ffc4c4ed40 [weak] Release file created at: Tue, 02 Jan 2018 12:06:51 +0000 E: Some index files failed to download. They have been ignored, or old ones used instead. P: Begin unmounting filesystems... P: Saving caches... Reading package lists... Building dependency tree... Del libv4l-0 1.14.1-1 [89.8 kB] Del libvorbisenc2 1.3.5-4.1 [79.1 kB] Del termineter 1.0.1-0kali1 [45.3 kB] Del python3-smoke-zephyr 1.2.0-0kali1 [15.1 kB] Del libgeos-3.6.2 3.6.2-1 [698 kB] Del git-man 1:2.15.1-3 [1514 kB] Del wpasupplicant 2:2.6-15 [1030 kB] Del git 1:2.15.1-3 [4555 kB] Del libsoundtouch1 1.9.2-3 [43.1 kB] Del libvorbis0a 1.3.5-4.1 [93.2 kB] Del libvorbisfile3 1.3.5-4.1 [24.4 kB] Del libv4lconvert0 1.14.1-1 [124 kB] Del libgeos-c1v5 3.6.2-1 [271 kB] Build of kali-rolling/default/amd64 live image failed (see build.log for details)