• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

SOLVED Error: Not enough disk space

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

belorsch

Folding Monk
Joined
Nov 1, 2001
Location
Maryland
Linux experience: Dabbler
Linux problem: Seucrity updates for Lubuntu 13.04 no longer supported, must upgrade to Lubuntu 13.10.
Upgrade Error:
Not enough free disk space

The upgrade has aborted. The upgrade needs a total of 55.0M free space on disk ‘/boot’. Please free at least an additional 18.8M of disk space on ‘/boot’. Empty your trash and remove temporary packages of former installations using ‘sudo apt-get clean’.

I'm looking at the files in "/boot' Anyone know what files I can delete? I have 209G free under '/'. As far as I can tell 'sudo apt-get clean' is doing nothing. 'Empty your trash' Sorry I don't see the trashcan to empty.

TIA
 
Do you have a separate /boot partition?

If you type
Code:
df -h

What do you see
Sorry meant to post that in the opener and forgot:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/lubuntu--vg-root 227G 6.7G 209G 4% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 975M 4.0K 975M 1% /dev
tmpfs 197M 776K 197M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 985M 76K 985M 1% /run/shm
none 100M 12K 100M 1% /run/user
/dev/sda1 228M 182M 35M 84% /boot

Course the formatting is hosed but I think its understandable.
 
use
Code:
 tags for formatting..

The answer is right in your post. /boot is basically too full, /boot is separate from / in this case because of the way it is partitioned.

To find what kernel you are currently running you can do

[code]
squid@squid:/boot$ uname -a
Linux squid 3.2.0-39-generic #62-Ubuntu SMP Thu Feb 28 00:28:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

In this case you can see i am running 3.2.0-39. So I go to /boot and take a look:

Code:
squid@squid:/boot$ ls
abi-3.0.0-12-server          memtest86+.bin
abi-3.0.0-13-server          memtest86+_multiboot.bin
abi-3.2.0-39-generic         System.map-3.0.0-12-server
config-3.0.0-12-server       System.map-3.0.0-13-server
config-3.0.0-13-server       System.map-3.2.0-39-generic
config-3.2.0-39-generic      vmcoreinfo-3.0.0-12-server
grub                         vmcoreinfo-3.0.0-13-server
initrd.img-3.0.0-12-server   vmlinuz-3.0.0-12-server
initrd.img-3.0.0-13-server   vmlinuz-3.0.0-13-server
initrd.img-3.2.0-39-generic  vmlinuz-3.2.0-39-generic

In general it is safe to remove all files that do not have your kernel version in the name. After you have removed older kernels, run:

Code:
sudo update-grub

To regenerate your grub.cfg
 
use
Code:
 tags for formatting..

The answer is right in your post. /boot is basically too full, /boot is separate from / in this case because of the way it is partitioned.

To find what kernel you are currently running you can do

[code]
squid@squid:/boot$ uname -a
Linux squid 3.2.0-39-generic #62-Ubuntu SMP Thu Feb 28 00:28:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

In this case you can see i am running 3.2.0-39. So I go to /boot and take a look:

Code:
squid@squid:/boot$ ls
abi-3.0.0-12-server          memtest86+.bin
abi-3.0.0-13-server          memtest86+_multiboot.bin
abi-3.2.0-39-generic         System.map-3.0.0-12-server
config-3.0.0-12-server       System.map-3.0.0-13-server
config-3.0.0-13-server       System.map-3.2.0-39-generic
config-3.2.0-39-generic      vmcoreinfo-3.0.0-12-server
grub                         vmcoreinfo-3.0.0-13-server
initrd.img-3.0.0-12-server   vmlinuz-3.0.0-12-server
initrd.img-3.0.0-13-server   vmlinuz-3.0.0-13-server
initrd.img-3.2.0-39-generic  vmlinuz-3.2.0-39-generic

In general it is safe to remove all files that do not have your kernel version in the name. After you have removed older kernels, run:

Code:
sudo update-grub

To regenerate your grub.cfg
Thanks Strat,
I knew I had to make space in \boot. I just wasn't sure what was safe to delete. Then I found out I couldn't del to get rid of them. Forget what the issue was with that but that led me to search for another way and I found the apt-get purge command. I like it! I'm not sure if I still needed to run the sudo update-grub command but I did just in case.
I'm up to date now... Until next time.
 
Back