appcenter icon indicating copy to clipboard operation
appcenter copied to clipboard

/boot filled up with kernel updates, simple solution required

Open elementaryBot opened this issue 8 years ago • 7 comments

I ran the update manager as normal and it siad /boot had run out of space and gave a command to fix it which did nothing "sudo apt-cache clean" or similar.

I may have fubared my system trying to manually remove old kernel packages, but even that didnt free up enough space, then removing the kernel updates manually form the update manager etc.. but still,

This was a default eOS install and the boot partition can fill up, there needs to be a non-tech way to the user to move past this.

I'd suggest just removing the old kernels automaticly and moving them onto the new ones.

Yeah, there's not space in my /boot to compile the new kernels.

ProblemType: Bug DistroRelease: elementary OS 0.3 Package: elementary-desktop 1.350+394~ubuntu0.3.1 [origin: LP-PPA-elementary-os-daily] ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CrashDB: elementary_meta CurrentDesktop: Pantheon Date: Mon Nov 3 17:10:24 2014 InstallationDate: Installed on 2014-08-18 (77 days ago) InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20140810) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: elementary-meta SuspiciousXErrors:

ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install)

Launchpad Details: #LP1388699 Ezra Sharp - 2014-11-03 04:21:19 +0000


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

elementaryBot avatar Mar 16 '17 21:03 elementaryBot

Same happen on default ubuntu install. If manually setting boot partition to a small value, after some kernel update apt fails until you clean up it manually. I think that keeping last 3 update should be enough

Launchpad Details: #LPC Nicolò Balzarotti - 2014-11-03 09:36:14 +0000

elementaryBot avatar Mar 16 '17 21:03 elementaryBot

To get rid of these you need to do this at the command line:

sudo apt-get purge linux-image-3.16.0.46-generic (where the last bit matches an old file in /boot) DON'T remove the most recent, though!

but yeah I agree that it should ideally be automatically done by the updater. this is one of the few things I have to regularly go into the command line for in elementary os

Launchpad Details: #LPC dankcushions - 2015-10-19 19:02:45 +0000

elementaryBot avatar Mar 16 '17 21:03 elementaryBot

Assigning this to appcenter. Appcenter should probably automatically know about automatically removing old kernels.

Launchpad Details: #LPC Daniel Fore - 2016-05-07 02:28:22 +0000

elementaryBot avatar Mar 16 '17 21:03 elementaryBot

https://www.bountysource.com/issues/5850207-boot-filled-up-with-kernel-updates-simple-solution-required

Launchpad Details: #LPC Maxim Taranov - 2016-12-15 01:44:33 +0000

elementaryBot avatar Mar 16 '17 21:03 elementaryBot

This issue still exists. However, I found an easy solution that involves typing 1 line on terminal. $ sudo apt autoremove And it's clear! Possibly injecting one line at the end of update command on AppCenter would do this, but in the mean time this is a solution that I am sticking with.

wilsonehusin avatar Jun 08 '17 03:06 wilsonehusin

It seems that sudo apt autoremove does not clean up like before. I use Mainline to manually remove old Kernels. By the way, Mainline does not know how to identify which Kernel is used. Automatic cleaning would be a plus for the distribution. I've been using eOS for a while and this is the only thing that stops me from installing it on newbies' computers.

Arnwaltur avatar Dec 16 '21 09:12 Arnwaltur

This is also being tracked in https://github.com/elementary/triage/issues/91

ChildishGiant avatar Jan 19 '22 23:01 ChildishGiant