no space left on /boot

Tommy Trussell tommy.trussell at
Wed Dec 6 17:28:53 UTC 2017

On Wed, Dec 6, 2017 at 2:10 AM, robert <robert at> wrote:

> after many years of dutiful service one of my remote boxes stops to accept
> updates.
> It complains that there is no space on /boot
> But I can not delete any of the old kernels as the following dialogs show
> how can I clean up things?
> robert

I see this happen all the time on older systems. I think it's due to a
missing step in the upgrade process -- Ideally before doing the upgrade you
would CAREFULLY do an

apt autoremove

to purge all the old linux packages, because in the upgrade process (from
Ubuntu 16.04 to 16.10 for instance) the upgrader deletes the kernel
packages but leaves the boot portions and libraries behind. I presume this
is because it's safer to assume it won't hurt anything and it could break
the boot if it picked the wrong things.

I wrote "carefully" because autoremove can occasionally remove things you
don't want it to.

I apologize that I cannot tell you the other places to look for the
libraries that get left behind. If you dig around you'll see them, and you
can free up a lot of space by deleting them. I'm sure other folks can
describe it better and maybe can describe exactly why the upgrade process
doesn't catch these files.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ubuntu-users mailing list