[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

*** This bug is a duplicate of bug 1675079 *** https://bugs.launchpad.net/bugs/1675079 ** This bug has been marked a duplicate of bug 1675079 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist -- You received this bug notification because you are a member

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

@kudalufi If apt-get does not remove the kernels they must have been set o manually installed which prevents u-u and update-manager from removing them, too. Please remove the ones set manually installed manually. -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

This is still broken, at least on my 18.04. apt-get autoremove does not touch old kernels. What is the process for re-reporting this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Many many many thanks :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or

Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

On Mon, Apr 23, 2018 at 5:48 PM, luca moscato wrote: > Sorry guys to bother you, I'm the reporter of > https://bugs.launchpad.net/ubuntu/+bug/1744045 Thank you for reporting bugs! > > Having this bug fixed exactly what does it means on Ubuntu 16.04 and on the > upcoming

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Sorry guys to bother you, I'm the reporter of https://bugs.launchpad.net/ubuntu/+bug/1744045 Having this bug fixed exactly what does it means on Ubuntu 16.04 and on the upcoming 18.04? With a clean installation (on an encrypted disk) the boot partition will be removed automatically? Or do I

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

This is now fixed in bionic and is scheduled for backporting to stable releases. ** No longer affects: unattended-upgrades -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I'm not sure how average users should handle this. I'm a professional software engineer and facing some serious dpkg issues when trying to make my 16.04 LTS work again due to filled up /boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Here is a good one: https://ubuntuforums.org/showthread.php?t=2374043=13697015#post13697015. The OP had, in total, 74 kernels, 65 headers and 93 extras = 232 packages that almost filled /, and gobbled up inodes. Don't know if it is a record, but it's close. -- You received this bug notification

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Recently, I had to remove 42 old kernels that accumulated over about 18 months on an old PC. It only took about 80 minutes. Clearly, old kernels should be auto-purged by default, with an option to keep them available for those that need it. As is, users have to manually run apt-get autoremove,

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

** Tags added: full-boot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ben, I feel your pain and couldn't agree more. I'm under the impression that this attitude is getting more common as Canonical focuses on server and IoT. Where are the days where the 100 Papercuts (https://wiki.ubuntu.com/One%20Hundred%20Papercuts) got a really high priority? IMHO, this bug sure

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

This bug has just hosed a system I installed for my parents. An unattended-upgrader that breaks your system if you don't attend to it IS broken. Having known about this problem for many years, the least you could have done is added a warning to the installer that choosing lvm or encryption will

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

... and 'sudo apt-get autoremove' would work, too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I wonder why fix to Bug #1439769 has not been released as SRU for 14.04 yet. The fix would make unattended-upgrade work better in removing extra kernels in 14.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

As for default settings for unattended-upgrade, it is interesting what Canonical Foundations Team is going to do with Bug #1624644. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Hi David One option is to install 16.04 or later and configure unattended- upgrades as recommended in the document. I am afraid all the related bugs will not be fixed in 14.04. Fixing Bug #1460396 and Bug #291342 would also help users of Software Updater even if unattended-upgrades is not used.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Hi Jarno I would suggest that most desktop users get notified by the updater that there are updates and run the updater accordingly to apply them. As such, I think the unclogging activity needs to run automatically as the users that are using the default boot partition size almost certainly

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

The reason why 'apt-get autoremove' is stated there is that it is a simple working way in 16.04 and later for most users, if your system is not broken already. purge-old-kernels is included in some Ubuntu package; consequently it is supported by Launchpad's bug reporting system. But as said in the

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Just one quick comment that issue for me never got fixed, and i switched to debian. and will finally hopefully find a way to stop getting notified about comments on this thread. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I'm completely with Dave on this one. Regarding jarnos comment #110: > I see many people take time to complain, but I see none who is willing to spend even 1$ to get an easier solution for poor Ubuntu users. Is funding the problem here? Because if it is, please tell us. I'm sure we can at least

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Well said Dave! It's hard for me to understand why smart people don't understand this issue. This required maintenance should not even be required for expert users let alone the average user. In over 30 years in IT and multiple platforms I have never heard of this design flaw/systems

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

jarnos, The reason why I responded first/primarily about "apt-get autoremove" and "purge-old-kernels" is that those are listed at the top of the page and are the things that a regular-ish user could feel confident doing. I do not feel that the idea of running unattended-upgrade from the command

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

alias remove-old-kernels='dpkg -l linux-{image,headers}-* | awk '\''/^ii/{print }'\'' | egrep '\''[0-9]+\.[0-9]+\.[0-9]+'\'' | grep -v 4.4.0-79 | xargs sudo apt-get -y purge' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I'm running Ubuntu 17.04 and whilst I have had the problem for so long I can't be sure, I think I have had this problem since 15.04. I keep my software completely up to date and all updates have been applied to date. I can honestly say that this issue is by no means fixed. The reference to

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

stub, I suppose the upgrading process did not change the settings concerning unattended-upgrade. You should do that manually after upgrading from 14.04 and initially remove extra kernels manually before upgrading. de0u, I tell about the restrictions concerning 'apt-get autoremove' in the wiki

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I tried the advice given on https://help.ubuntu.com/community/RemoveOldKernels, but it mostly doesn't work. For example, "apt-get autoremove --purge" removed zero kernels. To install "purge-old-kernels" would require installing like 60 dependencies of "bikeshed", which seems unreasonable. I

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

It also requires a complete reinstall if your boot partition is too small (ie. you accepted the defaults with an LVM or encrypted disk install pre 16.04 release). Machines upgraded from 14.04 will continue to fail and be directed here. -- You received this bug notification because you are a

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

No. Automatic removing is supposed to work in 16.04 and later by default. But even in 16.04 it works only, if you let unattended-upgrades install all kernel updates. I have not tested later releases, but I guess it is the same thing. I think removing should work in 16.04 and later, if you use the

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Is this bug confirmed resolved for any version of Ubuntu? What release do I need to get my friends migrated to, in order for this to not be a problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

** Description changed: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I had previously recommended (and consequently installed for them) Ubuntu 16.04 LVM to my parents however their"/boot" partition was constantly filling up to 100% and they kept complaining to me about it (as they are computer illiterate) so I had to eventually reinstall windows 10 for them and

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Correction: I meant systemd, not systemv in the previous comment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving,

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Jackalux, oh I see you have found the popular one-liner script for kernel removing. It is too complicated for what it does and too simple for what it should possibly do. I have written a script to ease kernel removal:

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I hate to be that guy that complains without contributing in a constructive manner, but I just need to say that it's completely unreasonable that my mom and friends I recommend Ubuntu to gets this problem. They should never have to be concerned with what a kernel image is or why the boot partition

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I don't have hardware that I imagine will run 16.xx so need this addressed on older LTS versions. My output for... dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' ... was 120 lines long! I had to teach myself

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

running 16.10, I am also running in to the problem that autoremove fails to remove old initrd files. This was greatly exacerbated by bug #798414 (https://bugs.launchpad.net/ubuntu/+source/initramfs- tools/+bug/798414). With an encrypted file system and a small boot partition, I only have space

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Found a DKMS bug report here: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title:

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

This might be aggravated by this DKMS bug which was found in v2.2.0.3, which incidentally is used in Ubuntu 16.04 LTS, and maybe other versions. It doesn't remove old initrd files in /boot *which lead to full /boot issues and subsequent update problems* I manually removed a bunch of old initrd

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Not fixed https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

My elderly parents are on Ubuntu 16.04, with updates set to 'Download and install automatically'. I must manually prune the Kernel images every so often, or the system's underwear gets all in a twist, and "apt-get autoremove' won't even work. Let's be clear: THIS IS NOT FIXED as of 16.04 LTS.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

** Also affects: unattended-upgrades Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Henry, do you use Ubuntu Trusty, and install kernels manually? See comment #79. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ok, I had to manually remove the files as they were added.. after that, it worked as intended. Funny thing is, all solutions provide here say that you need to enable the removal of unused dependencies by setting this: `Unattended-Upgrade::Remove-Unused-Dependencies "true"` Problem is.. I

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I can't even run `apt-get autoremove` because it starts filling up my /boot with old kernels until it runs out of space.. who the hell designed this madness? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

For those still having this issue on Ubuntu 16.04 : please check that you did not disable the automatic installation of updates. It might be the reason why the old kernels were not removed for me (not 100% yet). See discussion in https://ubuntuforums.org/showthread.php?t=2344232 With a GUI, it's

Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Seems to be a design flaw rather than a bug. From: Ian Weisser To: msing...@yahoo.com Sent: Tuesday, November 22, 2016 9:26 PM Subject: [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Happy to discuss and help...in the support forums. This CLOSED bug report is not the appropriate location to help people troubleshoot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ian, could you please give the URLs where to find the "similar-looking apt problems in the support forums" you're mentioning? I think many people here (including me) would be interested in what are the correct settings you mention. -- You received this bug notification because you are a member

Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Another (complimentary) solution for accumulating kernels in an LVM environment: http://blog.surgut.co.uk/2016/11/boot-less-lvm-rootfs-in- zesty.html The fix to this bug prevents kernels from accumulating. That complimentary solution eliminates the tiny /boot partition, eliminating the space

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

The fix is failing in xenial: I have to repeatedly clean up after the installer, when it complains that it cannot do its work due to disk space on the tiny /boot partition. "My disk is full again!" The bug remains: The automatic update is not considered an unattended update, since the user is

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Does anyone have this problem in Linux Mint 18? "Unattended-Upgrade ::Remove-New-Unused-Dependencies" also does not exist for me but the package was last updated a month ago, which leads me to believe the configuration file "50unattended-upgrades" wasn't "replaced" with the new version. Also, the

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

fksdlofioenvdfsdji, How did you "want to update && upgrade your server"? How many kernels can your /boot partition hold? (What is the size of your /boot partition?) Contents of "50unattended-upgrades" is misleading, as there is no mention of the new configuration variable

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

evendough people talk about not adding more comments to this thread. i had the problem, then they/you/here they said solution is upgrade to 16.04 - i solved the problem manually und than upgraded to 16.04 - now some months later i wanted to update && upgrade my server and boot is full again. -

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Bug #1624644 claims U-U does not work well with Software Updater a.k.a. update-manager. Can you confirm? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

This bug is 'Fix Released' because I marked it as such. Maybe too soon as it is irreversible. Ok, if someone writes new bug report about kernels not autoremoving, please link it here. Ian Weisser, you may e.g contact me privately, if you want to tell me about the kernel header packages thing.

Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Jarno Suni, This bug report ran it's course, and 'Fix Released' is another way of saying 'Closed.' You can discuss it, but no developer is likely to read it...to them, it's a closed issue. It's fixed, and won't be unfixed. The patch is released, and won't be reverted. The normal workflow is to

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ian Weisser, the issue is covered by the title of this bug report, anyway. If 'Unattended-Upgrade::Remove-Unused-Dependencies "true";' is used, U-U removes extra kernels, even if new kernels are installed by Software Updater in 16.04. In 14.04 (and in 12.04 I suppose) it does not work due to bug

Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Jarno Suni, That possible cause seems irrelevant to Unattended-Upgrades. Any package installed by any front-end to apt will be upgraded. U-U doesn't know what packages are installed, nor care. U-U simply tells aptdaemon to upgrade packages from the repositories authorized by the user. U-U does

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I guess the reason is I have installed some kernels using Software Updater even if Unattended Upgrades is set to install security updates. I guess I am not the only one using update-notifier and update-manager to install updates. -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Jarno Suni, Okay, I stand corrected on that statement. Please explain how you determined that Unattended Upgrades is the culprit, instead kernel header packages or user changes to apt-marking or other possible causes for the symptom you describe. With the information so far, I cannot duplicate

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ian Weisser, I think in 16.04, in contrary to what you claim, packages are not autoremoved before doing anything else. https://github.com/mvo5/unattended-upgrades tells: "Unattended-Upgrade::Remove-New-Unused-Dependencies - boolean (default:True) Remove any new unused dependencies after the

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Brian Candler, check if you have same repositories enabled in both servers. You should get purge-old-kernels, if you add byobu PPA repository. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I have two Precise (12.04) servers with Unattended-Upgrade::Remove-Unused-Dependencies "true"; in 50unattended-upgrades. One of them cleans up its kernels and only keeps the last two; one of them accumulates kernels over time, and I occasionally get alerts about /boot filling up. On the latter

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

There seems a lot of confusion in this bug report about which pieces of the system work together to cause this problem, and which pieces should be responsible for fixing it. Marking kernels as eligible for autoremoval is done by apt. The apt package provides

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I think this `Unattended-Upgrade::Remove-New-Unused-Dependencies` is not well tested yet. I have not noticed if it has removed any kernel. Also, I think it will not remove a kernel, if you happen to install a new kernel using Software Updater before Unattended Upgrades operates. -- You received

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Unattended upgrades does not remove old kernels that were installed by other means than unattended upgrades even if "Unattended-Upgrade ::Remove-Unused-Dependencies "true";" is set in Trusty (and maybe in Precise) Bug #1492709 -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I don't think backporting the new defaults to Precise and Trusty would be right for an SRU. On Precise and Trusty, you can set Unattended-Upgrade::Remove-Unused- Dependencies "true"; This is false by default. Setting it to true will remove *all* unused dependencies after every unattended

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

This was fixed in Xenial. The default is now to remove newly unused dependencies after every unattended upgrade. --- unattended-upgrades (0.89) unstable; urgency=medium [ Michael Vogt ] * Add `Unattended-Upgrade::Remove-New-Unused-Dependencies` that defaults to "yes". This ensures that

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

** Tags added: precise trusty xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ta, can you upload your 10periodic, 20auto-upgrades and 50unattended- upgrades from /etc/apt/apt.conf.d? and some log file from /var/log /unattended-upgrades that tells about kernel upgrades? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ta, oh, it seems you have tried to apply the workaround earlier. If you removed extra kernels then and setup Unattended Upgrades to install and remove kernels automatically, /boot folder should have some space, so I don't understand why it was full again. -- You received this bug notification

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ta, which version of Ubuntu do you mean? Did you try the workaround mentioned in the bug description? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

sorry guys one day, I updated and during the update it said my boot folder had zero space. Then when i restarted I couldn't boot. I managed to use an older version of the kernel in order to login and backup my files thankfully. I think I will uninstall this version of ubuntu. Hopefully this issue

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Can someone confirm that security updates are installed automatically by default in Xenial? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title:

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Can someone tell if unattended-upgrades has purged any older kernels in Xenial? Provided that security updates are configured to download and install automatically in Software & Updates, and there is line //Unattended-Upgrade::Remove-Unused-Dependencies "true"; or

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Oh, in contrary to previous comment, for some reason, kernel 4.4.0-28 was marked as manually installed. I changed it to be automatically installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

In 16.04, unattended-upgrades installed kernel linux- image-4.4.0-31-generic. Now /etc/apt/apt.conf.d/01autoremove-kernels protects releases 4.4.0-28-generic and 4.4.0-31-generic, but unattended upgrades did not purge two older kernels there are in my system. All of the kernels are automatically

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Anyone else affect Bug #1603620 in Xenial? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

thanks jarno thats was my problem. When i run the command without root it prompts me to install additional packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ta, "sudo apt-get autoremove --purge" only purges automatically installed packages, but in Trusty the linux kernel packages are likely to be marked as being manually installed. If you mean /boot/initrd.img* files by gzip archives, they should be removed automatically when you purge the respective

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Steve Sims, that is why you have to use dpkg first like told in the "Safely removing old kernels" section of the guide. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

sudo purge-old-kernels exists for me (Ubuntu 15.04) but fails because ... /boot is full :p [snip] update-initramfs: Generating /boot/initrd.img-3.19.0-50-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 [snip] This is such a long-standing issue, have to wonder

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Hi also for me sudo purge-old-kernels sudo: purge-old-kernels: command not found purge-old-kernels does not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Well when I attempted the workaround I got this: sudo apt-get autoremove --purge Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. I actually used the above command to clear up space

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

The workaround page says: "Warning: Do NOT use the 'rm' command to delete files that were placed by the package manager, including kernel files. It merely creates a new headache for you to solve when the package manager cannot remove packages due to 'file not found'. Always use the package manager

Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Thanks for the update. On Sat, 11 Jun 2016 at 03:00 Ta wrote: > Ok I managed to resolve this issue: > > opened file explorer as root using gksudo. I navigated to the boot > folder then manually deleted all the gzip archives ( because I expect > they would not be

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

And use dpkg directly only, if apt-get (or purge-old-kernels) fails. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving,

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ta, dpkg tells the header is not installed. If you have separate /boot partition, the existence of headers do not matter because they are not stored in /boot. If the current instructions do not work, please comment at http://askubuntu.com/a/731791/21005 to tell what exactly went wrong. -- You

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Ok I managed to resolve this issue: opened file explorer as root using gksudo. I navigated to the boot folder then manually deleted all the gzip archives ( because I expect they would not be used). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

also I noticed there are gzip archives in the boot folder can I manually remove these? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

also I noticed there are gzip archives in the boot folder can I manually remove these? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

I followed the workaround steps and they didn't work I removed the only unused header and it still says its installed? dpkg: warning: ignoring request to remove linux-headers-4.2.0-30-generic which isn't installed rc linux-image-3.19.0-25-generic rc linux-image-3.19.0-51-generic pi

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

so i still have this bug how am I meant to fix this? Am I meant to follow the work around or do I need to upgrade my system to the latest version of ubuntu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

Except upgrading to newer release by an installation media may leave old kernels that have to be removed manually: Bug #1586303 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

For 16.04: There are no additional steps required that I know. For older releases; See https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

** Description changed: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch

  1   2   >