How do I rectify a full /boot partition?

Asked by neonlight

 /var/cache/apt/archives/linux-image-2.6.24-19-generic_2.6.24-19.36_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
Architecture: i386
Date: Tue Jul 22 23:52:04 2008
DistroRelease: Ubuntu 8.04
ErrorMessage: fehlgeschlagen in buffer_write(fd) (10, ret=-1)
NonfreeKernelModules: fglrx ath_hal
Package: linux-image-2.6.24-19-generic 2.6.24-19.34 [modified: lib/modules/2.6.24-19-generic/modules.pcimap lib/modules/2.6.24-19-generic/modules.dep lib/modules/2.6.24-19-generic/modules.ieee1394map lib/modules/2.6.24-19-generic/modules.usbmap lib/modules/2.6.24-19-generic/modules.isapnpmap lib/modules/2.6.24-19-generic/modules.seriomap lib/modules/2.6.24-19-generic/modules.alias lib/modules/2.6.24-19-generic/modules.symbols]
PackageArchitecture: i386
SourcePackage: linux
Title: package linux-image-2.6.24-19-generic 2.6.24-19.34 [modified: lib/modules/2.6.24-19-generic/modules.pcimap lib/modules/2.6.24-19-generic/modules.dep lib/modules/2.6.24-19-generic/modules.ieee1394map lib/modules/2.6.24-19-generic/modules.usbmap lib/modules/2.6.24-19-generic/modules.isapnpmap lib/modules/2.6.24-19-generic/modules.seriomap lib/modules/2.6.24-19-generic/modules.alias lib/modules/2.6.24-19-generic/modules.symbols] failed to install/upgrade: fehlgeschlagen in buffer_write(fd) (10, ret=-1)
Uname: Linux 2.6.24-19-generic i686

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu linux Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #250965.

Revision history for this message
neonlight (tomtom) said :
#1
Revision history for this message
Chris Coulson (chrisccoulson) said :
#2

Thank you for taking the time to report this bug and help make Ubuntu better. After having a look through your log file, it looks like you're out of disk space. Could you please confirm this by running the following command in a terminal, and posting the results here:

df -h

If this is the case, I will convert this in to a question in our support tracker, where you'll get some more assistance.

Thanks

Revision history for this message
Chris Coulson (chrisccoulson) said :
#3

From neonlight:

Dateisystem Größe Benut Verf Ben% Eingehängt auf
/dev/mapper/brian-root
                       20G 3.5G 17G 18% /
varrun 5.0G 1.3G 3.8G 25% /var/run
varlock 5.0G 1.3G 3.8G 25% /var/lock
udev 378M 84K 378M 1% /dev
devshm 528M 12K 528M 1% /dev/shm
lrm 378M 39M 340M 11% /lib/modules/2.6.24-19-generic/volatile
/dev/sda1 99M 99M 0 100% /boot
/dev/mapper/brian-home
                      117G 66G 52G 57% /home
/dev/mapper/brian-tmp
                      5.0G 33M 5.0G 1% /tmp
/dev/mapper/brian-var
                      5.0G 1.3G 3.8G 25% /var
none 528M 12K 528M 1% /dev/shm
gvfs-fuse-daemon 20G 3.5G 17G 18% /home/neonlight/.gvfs
/dev/sdb1 3.9G 540M 3.3G 14% /media/NE0NL1GHT

Revision history for this message
Chris Coulson (chrisccoulson) said :
#4

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs .

I have also modified the title to something more appropriate for the support tracker.

Thanks

Revision history for this message
Jonathan Marsden (jmarsden) said :
#5

Basically you need to find out what files are in /boot that are no longer needed, and get rid of them. You could list all big (over 1MByte) files under /boot with

  find /boot -size +1M |xargs ls -l

which might give you (or us here, if you provide the output here!) a clue about what is taking up all that space.

More specifically, it is likely that you have multiple kernel packages installed, some of which are no longer needed. You can use any package manager to look at what packages you have installed, from the command line:

  dpkg-query -l linux-image-* |grep ^ii

should show you the kernel images you have. If you see more than two, it is probably appropriate to remove the oldest one or two such images using your package manager of choice (synaptic, aptitude or dpkg)

  dpkg -r linux-image-2.4.1-99-generic

would remove a (made up example) linux kernel image package.

I would strongly urge you to leave both the linux-image-generic package, and the most recent linux-image-2.<something> package installed... be careful not to uninstall anything you actually need!

For comparison, my /boot here contains 19Mbytes of files, so 99MB is... quite a lot.

If this solves your issue, please come back here to Launchpad and mark this question as solved.

Jonathan

Can you help with this problem?

Provide an answer of your own, or ask neonlight for more information if necessary.

To post a message you must log in.