I can't believe they haven't taken care of this yet. When I go to delete the older kernels I get denied. I tried some other things I saw mentioned but, probably because I didn't know what I was doing, they didn't work for me either. Now, I make sure all my data is on the other hard drive and just reinstall the system... start over. I am running Lubuntu 15.04 now, we'll see.
On 10/12/2015 02:26 PM, Justin wrote: > I had this problem about a month ago and deleted old kernels and it > worked fine at that point. I had tried a few different flavors before I > settled on Lubuntu so I thought that might be why I had the older kernel > versions floating around. Here I am with the same problem again. > > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/ubuntu--vg-root 228G 14G 204G 7% / > none 4.0K 0 4.0K 0% /sys/fs/cgroup > udev 479M 8.0K 479M 1% /dev > tmpfs 99M 1.5M 98M 2% /run > none 5.0M 0 5.0M 0% /run/lock > none 493M 76K 493M 1% /run/shm > none 100M 24K 100M 1% /run/user > /dev/sda2 237M 232M 0 100% /boot > > sda2 is chock full again so I checked my kernels: > > i linux-image-3.16.0-44-generic - Linux kernel image for version 3.16.0 > on 3 > i linux-image-3.16.0-45-generic - Linux kernel image for version 3.16.0 > on 3 > i linux-image-3.16.0-46-generic - Linux kernel image for version 3.16.0 > on 3 > i linux-image-3.16.0-48-generic - Linux kernel image for version 3.16.0 > on 3 > i linux-image-3.16.0-49-generic - Linux kernel image for version 3.16.0 > on 3 > i linux-image-3.16.0-50-generic - Linux kernel image for version 3.16.0 > on 3 > i linux-image-extra-3.16.0-44-gen - Linux kernel extra modules for version > 3.1 > i linux-image-extra-3.16.0-45-gen - Linux kernel extra modules for version > 3.1 > i linux-image-extra-3.16.0-46-gen - Linux kernel extra modules for version > 3.1 > i linux-image-extra-3.16.0-48-gen - Linux kernel extra modules for version > 3.1 > i linux-image-extra-3.16.0-49-gen - Linux kernel extra modules for version > 3.1 > > I am confident that I had deleted all but 49 and 50 last time but here > they are again. I'll admit that I am a relative noob on linux so the > problem may be with the user! I am posting this information primarily to > try and help. I'm going to delete the extra kernels again and see how it > goes. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp