LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 04-06-2014, 10:23 AM   #1
alex100
LQ Newbie
 
Registered: Apr 2014
Posts: 4

Rep: Reputation: Disabled
/boot full


my /boot is 100% full and am trying to clear. I have several old kernels and have tried all of the methods for clearing listed in other posts but none seem to work. I am running Ubuntu Server 13.10. My current kernel is 3.11.0-17 although 3.11.0-19 is listed and but has never installed correctly due to lack of space. Any suggestions as I seem to be going in circles.
 
Old 04-06-2014, 11:49 AM   #2
pingu
Senior Member
 
Registered: Jul 2004
Location: Skuttunge SWEDEN
Distribution: Debian preferably
Posts: 1,350

Rep: Reputation: 127Reputation: 127
Can't you just delete old kernels, together with old initrd & config-files?
 
Old 04-06-2014, 01:49 PM   #3
John VV
LQ Muse
 
Registered: Aug 2005
Location: A2 area Mi.
Posts: 16,818

Rep: Reputation: 2408Reputation: 2408Reputation: 2408Reputation: 2408Reputation: 2408Reputation: 2408Reputation: 2408Reputation: 2408Reputation: 2408Reputation: 2408Reputation: 2408
normally there will be 3 kernels
the current one being used
the one before that as a BACK UP
and the one before the ( now back up) as an emergency BACK UP

if there are more than that then you changed some setting to allow more
or to not remove old kernels

just how small is this boot partition ?

i have had NO problems with boot partitions as small as 100 meg
but some distros like BIG boot partitions
so 500 meg is a good size
 
Old 04-06-2014, 02:12 PM   #4
alex100
LQ Newbie
 
Registered: Apr 2014
Posts: 4

Original Poster
Rep: Reputation: Disabled
I have tried Sudo apt-get purge (+ names of old kernel's), sudo apt-get remove, sudo apt-get clean etc etc but none of them seem to remove the old kernels. As an example when I run remove linux-image-3.8.0-31-generic I get:

Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies.
linux-image-extra-3.11.0-19-generic : Depends: linux-image-3.11.0-19-generic but it is not going to be installed
linux-image-extra-3.8.0-31-generic : Depends: linux-image-3.8.0-31-generic but it is not going to be installed
linux-image-generic : Depends: linux-image-3.11.0-19-generic but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

if I then run apt-get -f install I get:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
attr bind9 bind9utils libhdb9-heimdal libkdc2-heimdal libndr-standard0
libndr0 libsamba-credentials0 libsamba-hostconfig0 libsamba-util0 libsamdb0
linux-headers-3.8.0-19 linux-headers-3.8.0-19-generic linux-headers-3.8.0-31
linux-headers-3.8.0-31-generic linux-headers-3.8.0-32
linux-headers-3.8.0-32-generic linux-headers-3.8.0-33
linux-headers-3.8.0-33-generic linux-headers-3.8.0-34
linux-headers-3.8.0-34-generic linux-image-3.8.0-19-generic
linux-image-3.8.0-31-generic linux-image-3.8.0-32-generic
linux-image-3.8.0-33-generic linux-image-3.8.0-34-generic
linux-image-extra-3.8.0-19-generic linux-image-extra-3.8.0-31-generic
linux-image-extra-3.8.0-32-generic linux-image-extra-3.8.0-33-generic
linux-image-extra-3.8.0-34-generic python-dnspython python-ldb python-talloc
python-tdb
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
linux-image-3.11.0-19-generic
Suggested packages:
fdutils linux-doc-3.11.0 linux-source-3.11.0 linux-tools
The following NEW packages will be installed
linux-image-3.11.0-19-generic
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
10 not fully installed or removed.
Need to get 0 B/14.5 MB of archives.
After this operation, 39.8 MB of additional disk space will be used.
Do you want to continue [Y/n]?

if I click Y I get:

(Reading database ... 343703 files and directories currently installed.)
Unpacking linux-image-3.11.0-19-generic (from .../linux-image-3.11.0-19-generic_3.11.0-19.33_amd64.deb) ...
Done.
dpkg: error processing /var/cache/apt/archives/linux-image-3.11.0-19-generic_3.11.0-19.33_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-3.11.0-19-generic' to '/boot/vmlinuz-3.11.0-19-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.11.0-19-generic /boot/vmlinuz-3.11.0-19-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.11.0-19-generic /boot/vmlinuz-3.11.0-19-generic
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-3.11.0-19-generic_3.11.0-19.33_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

So am getting nowhere!
 
Old 04-06-2014, 02:16 PM   #5
alex100
LQ Newbie
 
Registered: Apr 2014
Posts: 4

Original Poster
Rep: Reputation: Disabled
also for info the partition with /boot is 257MB
 
Old 04-06-2014, 02:25 PM   #6
pingu
Senior Member
 
Registered: Jul 2004
Location: Skuttunge SWEDEN
Distribution: Debian preferably
Posts: 1,350

Rep: Reputation: 127Reputation: 127
How about
# rm /boot/vmlinuz-3.8.0-31-generic
# rm /boot/initrd.img-3.8.0-31-generic
?
Or, like the message says:
# apt-get autoremove

Last edited by pingu; 04-06-2014 at 02:27 PM.
 
Old 04-06-2014, 02:48 PM   #7
alex100
LQ Newbie
 
Registered: Apr 2014
Posts: 4

Original Poster
Rep: Reputation: Disabled
sudo apt-get autoremove does nothing! (have tried several times and everything is still there!) When I run I get:

Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run ‚apt-get -f install‚ to correct these.
The following packages have unmet dependencies.
linux-image-extra-3.11.0-19-generic : Depends: linux-image-3.11.0-19-generic but it is not installed
linux-image-generic : Depends: linux-image-3.11.0-19-generic but it is not installed
E: Unmet dependencies. Try using -f.
 
Old 04-06-2014, 03:32 PM   #8
pingu
Senior Member
 
Registered: Jul 2004
Location: Skuttunge SWEDEN
Distribution: Debian preferably
Posts: 1,350

Rep: Reputation: 127Reputation: 127
So just delete the old kernels & initrd. Then there should be space enough to install the newest kernel.

Now sometimes, when apt gets screwed up completely - like when you run out of space - you'll have to repeat commands several times before everything is back to normal. It has happened to me, I don't remember exactly what I did but trying to recall.
So you run "apt-get remove linux-image-extra-3.11.0-19-generic" "apt-get -f install" over and over. Also pay attention to messages you get, maybe apt gets stuck on some other package then try to remove it. Again, " apt-get remove <whatever_package_name>".

But my first choice would still be to delete very old stuff from /boot/ and try with "apt-get -f install".

Another way to do it is to unmount /boot, remount it somewhere else like /mnt/myboot, copy everything to /boot which now resides on same partition as / meaning there's lots of space.
Then try to install new kernel again. As there is space enough this should work.
 
Old 04-06-2014, 06:53 PM   #9
JeremyBoden
Member
 
Registered: Nov 2011
Posts: 938

Rep: Reputation: 174Reputation: 174
Cool

Solution (for the future)
Put /boot in the same partition as /usr
 
Old 04-07-2014, 06:51 PM   #10
jefro
Moderator
 
Registered: Mar 2008
Posts: 15,374

Rep: Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198
The OP created a /boot partition. It is a common task.
/boot may need to be a separate partition in systems than can't boot to high partitions. Other reasons too exist for this choice.

The solution would be to create larger /boot partitions upon install. It's a stinker to make it larger later. Kernels are getting larger and larger. An update or two and your default 100m partition is full.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Using qemu to boot a full hardware installed Windows partion on dual boot system dwmolyneux Linux - General 8 05-13-2012 01:11 PM
[SOLVED] /boot partition full bluforce Linux - General 2 04-16-2012 01:57 PM
Boot partition is full ngiamol Linux - General 9 05-10-2009 09:55 AM
Boot partition nearly full Yig Linux - Newbie 10 10-26-2007 10:34 PM
boot partition full spiri Debian 3 09-13-2005 07:05 PM


All times are GMT -5. The time now is 04:17 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration