when trying to do an apt-get dist-upgrade i get the following error:
Preconfiguring packages ... (Reading database ... 129755 files and directories currently installed.) Preparing to unpack .../openjdk-7-jre-headless_7u79-2.5.6-1~deb8u1_amd64.deb ... Unpacking openjdk-7-jre-headless:amd64 (7u79-2.5.6-1~deb8u1) over (7u79-2.5.5-1~deb8u1) ... dpkg: error processing archive /var/cache/apt/archives/openjdk-7-jre-headless_7u79-2.5.6-1~deb8u1_amd64.deb (--unpack): cannot copy extracted data for './usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rt.jar' to '/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rt.jar.dpkg-new': failed to write (No space left on device) dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../qemu-system-misc_1%3a2.1+dfsg-12+deb8u1_amd64.deb ... Unpacking qemu-system-misc (1:2.1+dfsg-12+deb8u1) ... dpkg: error processing archive /var/cache/apt/archives/qemu-system-misc_1%3a2.1+dfsg-12+deb8u1_amd64.deb (--unpack): cannot copy extracted data for './usr/bin/qemu-system-cris' to '/usr/bin/qemu-system-cris.dpkg-new': failed to write (No space left on device) dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../qemu-user_1%3a2.1+dfsg-12+deb8u1_amd64.deb ... Unpacking qemu-user (1:2.1+dfsg-12+deb8u1) ... dpkg: error processing archive /var/cache/apt/archives/qemu-user_1%3a2.1+dfsg-12+deb8u1_amd64.deb (--unpack): cannot copy extracted data for './usr/bin/qemu-armeb' to '/usr/bin/qemu-armeb.dpkg-new': failed to write (No space left on device) dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../linux-image-3.16.0-4-amd64_3.16.7-ckt11-1+deb8u2_amd64.deb ... Unpacking linux-image-3.16.0-4-amd64 (3.16.7-ckt11-1+deb8u2) over (3.16.7-ckt11-1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-3.16.0-4-amd64_3.16.7-ckt11-1+deb8u2_amd64.deb (--unpack): cannot copy extracted data for './lib/modules/3.16.0-4-amd64/kernel/sound/firewire/snd-firewire-lib.ko' to '/lib/modules/3.16.0-4-amd64/kernel/sound/firewire/snd-firewire-lib.ko.dpkg-new': failed to write (No space left on device) dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../chromium_44.0.2403.89-1~deb8u1_amd64.deb ... Unpacking chromium (44.0.2403.89-1~deb8u1) over (43.0.2357.65-1~deb8u1) ... dpkg: error processing archive /var/cache/apt/archives/chromium_44.0.2403.89-1~deb8u1_amd64.deb (--unpack): cannot copy extracted data for './usr/lib/chromium/resources.pak' to '/usr/lib/chromium/resources.pak.dpkg-new': failed to write (No space left on device) dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db (220.127.116.11-5) ... /usr/bin/mandb: can't write to /var/cache/man/25396: No space left on device Processing triggers for menu (2.1.47) ... Errors were encountered while processing: /var/cache/apt/archives/openjdk-7-jre-headless_7u79-2.5.6-1~deb8u1_amd64.deb /var/cache/apt/archives/qemu-system-misc_1%3a2.1+dfsg-12+deb8u1_amd64.deb /var/cache/apt/archives/qemu-user_1%3a2.1+dfsg-12+deb8u1_amd64.deb /var/cache/apt/archives/linux-image-3.16.0-4-amd64_3.16.7-ckt11-1+deb8u2_amd64.deb /var/cache/apt/archives/chromium_44.0.2403.89-1~deb8u1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) malvidx@malvidx:~$
but i have plenty of hard drive space.
can someone help?
=== Mod Edit ===
[code] please use code tags from the menu above [/code]
Last edited by Sector11 (2015-07-30 14:11:10)
cannot copy extracted data for './usr/bin/qemu-system-cris' to '/usr/bin/qemu-system-cris.dpkg-new': failed to write (No space left on device)...etc
....but i have plenty of hard drive space....
(NB Please use code tags when posting terminal output. It makes it much easier to read.)
First thing to do is see what is available with
A common solution is to clean your apt cache with
sudo apt-get clean sudo apt-get autoclean
Use the forum search tool (icon top right of page) for "no space left on device", and see what you find
there's also the 5 or sometimes even 10% reserved blocks to be taken into account.
cleaning apt cache should help.
there can also be some other problem, which makes some log file overflow (search home folder or /var/log).
you should play around with du and df and try to find the culprit(s).
do you have everything in one big partition? if not, more info is required.
@OP: often, WM spills lot of messages in file '.xsession-errors' (relevant if you have your OS installation in one big partition). Solution would be:
$ cd $HOME $ ls -lh .xsession-errors # to check size of this file $ rm .xsession-errors
Postpone all your duties; if you die, you won't have to do them ..
--> The very new BL forum! <--
As above - first step to get space is "apt-get autoclean"
"cd /var" then "ncdu" # command gives more information that du about disk usage.
"journalctl --disk-usage" # will show size of your systemd logging If it seems large
read man journalctl with reference to --vacuum-size or --vacuum-time
examples of vacuuming here
Jean Vanier wrote "Being Human" and "A Short History of Progress" by Ronald Wright. Gotta love the Massey Lectures.
You can use baobab to get a visual on your disk space, and see what's causing you to run out of space.
sudo apt-get install baobab
Might be easier to diagnose the problem that way.
Also, during installation, did you install everything on one partition, or seperate it? If the /home directory is separate, then there's probably not enough space allocated for the root directory (where all your programs are installed). Which = repartition time.
df -h output is:
Filesystem Size Used Avail Use% Mounted on /dev/dm-1 6.3G 6.3G 0 100% / udev 10M 0 10M 0% /dev tmpfs 1.6G 8.8M 1.6G 1% /run tmpfs 3.9G 960K 3.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/mapper/malvidx--vg-tmp 360M 2.1M 335M 1% /tmp /dev/mapper/malvidx--vg-var 2.7G 790M 1.8G 31% /var /dev/mapper/malvidx--vg-home 433G 19G 393G 5% /home /dev/sda2 237M 36M 189M 16% /boot /dev/sda1 511M 132K 511M 1% /boot/efi tmpfs 788M 8.0K 788M 1% /run/user/1000
stupid question, but what is /dev/dm-1?
dm is device mapper... dm-1 is your / partition, that is full. you could make another logical volume for /usr, get everything in your /usr direcotry and put it in the /usr partition, and mount it in /usr.
Last edited by pingu (2015-08-03 22:36:52)
"We don't merge kernel code just because user space was written by a retarded monkey on crack."
Linus f****g Trovalds