Strange notice not seen before

[RedRat]

I recently got the notice of upgrades. When I attempted to do the upgrade I got this notice:

Notice.png
When I run sudo apt-get clean, nothing happens, the old files are still there.

Any suggestions as to what I am doing wrong?

[grahammechanical]

The images do not appear in your post.

[coffeecat]

OK, I have a screen shot but for reasons only known to Firefox and the Ubuntu forum, it does not seem to show. basically it says to clear more free space in boot.

You dragged and dropped an image straight into the message editor and triggered a Firefox bug. Vbulletin doesn't work that way. You need to upload an image with the manage attachments button. * I've removed the spurious base64 code.

As far as your problem is concerned we probably don't need an image. It sounds as though you have filled your boot partition. Post the output of these two terminal commands:

df -h
ls -l /boot

One question: did you create a separate boot partition or did you choose an encrypted system when you installed Ubuntu?

* Edit: I see you've edited your post and done that now. You have indeed got an overfull boot partition.

[RedRat]

OK, here goes:
df -h

Filesystem                   Size  Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root  453G  8.8G  421G   3% /
none                         4.0K     0  4.0K   0% /sys/fs/cgroup
udev                         2.9G  4.0K  2.9G   1% /dev
tmpfs                        596M  1.4M  595M   1% /run
none                         5.0M     0  5.0M   0% /run/lock
none                         3.0G  1.4M  3.0G   1% /run/shm
none                         100M   72K  100M   1% /run/user
/dev/sda1                    236M  185M   40M  83% /boot

ls -l /boot

total 179531
-rw-r--r-- 1 root root  1158016 May  2 17:30 abi-3.13.0-24-generic
-rw-r--r-- 1 root root  1161713 May 15 12:07 abi-3.13.0-27-generic
-rw-r--r-- 1 root root  1161764 Jun  4 14:57 abi-3.13.0-29-generic
-rw-r--r-- 1 root root  1162257 Jul  4 15:18 abi-3.13.0-30-generic
-rw-r--r-- 1 root root  1162712 Jul 14 21:29 abi-3.13.0-32-generic
-rw-r--r-- 1 root root  1162712 Jul 29 10:41 abi-3.13.0-33-generic
-rw-r--r-- 1 root root   165510 May  2 17:30 config-3.13.0-24-generic
-rw-r--r-- 1 root root   165521 May 15 12:07 config-3.13.0-27-generic
-rw-r--r-- 1 root root   165544 Jun  4 14:57 config-3.13.0-29-generic
-rw-r--r-- 1 root root   165576 Jul  4 15:18 config-3.13.0-30-generic
-rw-r--r-- 1 root root   165611 Jul 14 21:29 config-3.13.0-32-generic
-rw-r--r-- 1 root root   165611 Jul 29 10:41 config-3.13.0-33-generic
drwxr-xr-x 5 root root     1024 Aug 12 17:12 grub
-rw-r--r-- 1 root root 19891718 May 15 21:09 initrd.img-3.13.0-24-generic
-rw-r--r-- 1 root root 19896611 May 26 18:39 initrd.img-3.13.0-27-generic
-rw-r--r-- 1 root root 19896419 Jun 15 10:23 initrd.img-3.13.0-29-generic
-rw-r--r-- 1 root root 19950046 Jul 14 17:54 initrd.img-3.13.0-30-generic
-rw-r--r-- 1 root root 19952556 Aug  9 11:00 initrd.img-3.13.0-32-generic
-rw-r--r-- 1 root root 19951741 Aug 12 17:12 initrd.img-3.13.0-33-generic
drwx------ 2 root root    12288 May  3 17:52 lost+found
-rw-r--r-- 1 root root   176500 Mar 12 05:31 memtest86+.bin
-rw-r--r-- 1 root root   178176 Mar 12 05:31 memtest86+.elf
-rw-r--r-- 1 root root   178680 Mar 12 05:31 memtest86+_multiboot.bin
-rw------- 1 root root  3372643 May  2 17:30 System.map-3.13.0-24-generic
-rw------- 1 root root  3377429 May 15 12:07 System.map-3.13.0-27-generic
-rw------- 1 root root  3378267 Jun  4 14:57 System.map-3.13.0-29-generic
-rw------- 1 root root  3378641 Jul  4 15:18 System.map-3.13.0-30-generic
-rw------- 1 root root  3381262 Jul 14 21:29 System.map-3.13.0-32-generic
-rw------- 1 root root  3381262 Jul 29 10:41 System.map-3.13.0-33-generic
-rw------- 1 root root  5776416 May  2 17:30 vmlinuz-3.13.0-24-generic
-rw------- 1 root root  5790912 May 15 12:07 vmlinuz-3.13.0-27-generic
-rw------- 1 root root  5792544 Jun  4 14:57 vmlinuz-3.13.0-29-generic
-rw------- 1 root root  5792608 Jul  4 15:18 vmlinuz-3.13.0-30-generic
-rw------- 1 root root  5798112 Jul 14 21:29 vmlinuz-3.1-32-generic
-rw------- 1 root root  5798688 Jul 29 10:41 vmlinuz-3.13.0-33-generic

No the installation was pretty vanilla, no encryption. Basically, just wiped the old 10.04 installation on my Serval Pro laptop.
Did nothing to sizing, if I recall just used the whole disk.

My question is why is sudo apt-get clean not doing its job?

[coffeecat]

No the installation was pretty vanilla, no encryption.

Are you sure?

/dev/mapper/ubuntu--vg-root  453G  8.8G  421G   3% /

Is this familiar:



The installer creates a separate 256MB boot partition when you choose an encrypted install because that has to be unencrypted. A lot of people are being caught by this by not clearing out old kernels occasionally. In my opinion, 256MB is not large enough and the person installing has no way of changing this, but that's another story.

But anyway, the important thing is that you need to uninstall all the kernels except the newest one or two. Don't delete the files manually in /boot. You need to use the package manager to do this properly. Do you need help with this?

By the way, I changed the quote tags in your last post to code tags to preserve formatting. You need code tags for terminal output or config files.

Screenshot from 2014-08-13 15_01_25.png

[ajgreeny]

I'm afraid sudo apt-get clean will not help you in any way. All that does is remove all package files from the cache that is sitting in /var/cache/apt/archives, and that is exactly what the name suggests; a cache, nothing to do with booting or running your system.

If you installed with no encryption and without choosing to use a separate /boot partition you would have ended with just three partitions, root or /, an extended partition, and within that extended partition a swap partition of the exact same size.

You must have chosen to use a separate /boot partition at some point or it would not exist; or did you perhaps choose Something Else at partitioning stage and then reuse all the partitions that you saw in the old 10.04 installation?

[Impavidus]

sudo apt-get --purge autoremove

may help to uninstall old kernels. If that doesn't work (because the update is already partially installed), you'll have to use dpkg directly. Run

dpkg --list linux-image*

to get a list of installed kernels. Make the terminal wide enough, else the output won't fit. It will show the exact names of the packages, of which you'll have to uninstall the oldest versions with

sudo dpkg --purge linux-image-<possibly something>3.2.0-<something>

[RedRat]

Are you sure?



Is this familiar:



The installer creates a separate 256MB boot partition when you choose an encrypted install because that has to be unencrypted. A lot of people are being caught by this by not clearing out old kernels occasionally. In my opinion, 256MB is not large enough and the person installing has no way of changing this, but that's another story.

But anyway, the important thing is that you need to uninstall all the kernels except the newest one or two. Don't delete the files manually in /boot. You need to use the package manager to do this properly. Do you need help with this?

By the way, I changed the quote tags in your last post to code tags to preserve formatting. You need code tags for terminal output or config files.

Screenshot from 2014-08-13 15_01_25.png

No that does not look familiar. basically I told it to use the whole disk for my 14.04 installation. I did not see anything about encryption when I did this. Further, I was never asked for a security key.

Thanks for any clearing up of tags.

[RedRat]

The purge command did not work.

However when I list the images:

||/ Name              Version       Architecture  Description
+++-=================-=============-=============-========================================
un  linux-image       <none>        <none>        (no description available)
un  linux-image-3.0   <none>        <none>        (no description available)
ii  linux-image-3.13. 3.13.0-24.47  amd64         Linux kernel image for version 3.13.0 on
ii  linux-image-3.13. 3.13.0-27.50  amd64         Linux kernel image for version 3.13.0 on
ii  linux-image-3.13. 3.13.0-29.53  amd64         Linux kernel image for version 3.13.0 on
ii  linux-image-3.13. 3.13.0-30.55  amd64         Linux kernel image for version 3.13.0 on
ii  linux-image-3.13. 3.13.0-32.57  amd64         Linux kernel image for version 3.13.0 on
ii  linux-image-3.13. 3.13.0-33.58  amd64         Linux kernel image for version 3.13.0 on
ii  linux-image-extra 3.13.0-24.47  amd64         Linux kernel extra modules for version 3
ii  linux-image-extra 3.13.0-27.50  amd64         Linux kernel extra modules for version 3
ii  linux-image-extra 3.13.0-29.53  amd64         Linux kernel extra modules for version 3
ii  linux-image-extra 3.13.0-30.55  amd64         Linux kernel extra modules for version 3
ii  linux-image-extra 3.13.0-32.57  amd64         Linux kernel extra modules for version 3
ii  linux-image-extra 3.13.0-33.58  amd64         Linux kernel extra modules for version 3
ii  linux-image-gener 3.13.0.33.39  amd64         Generic Linux kernel image

If I run

sudo dpkg --purge linux-image-<possibly something>3.2.0-<something>

That would wipe out my existing kernel since that is in /boot. Naturally I am a bit leery of running that code.

Perhaps, at the end of the day, I should just re-install 14.04LTS from the disk and wipe the disk completely, since I don't have a lot invested in this particular installtion which is only a few months old.

[ajgreeny]

The easiest way to sort this out now is to install synaptic (package manager), open it, reload the packages list with far left icon in toolbar, then search for linux-image by "Name" only, not "Description and Name".

That will list all kernels, show those installed, and allow you to "Mark for Complete Removal" the old ones you don't need any more. This will also show you just how brilliant synaptic is when compared with the software-centre; it is what I almost always use for installing, uninstalling or updating packages on my system as it is so much more flexible, giving you a lot more detail about what is happening than anything except the command line, and in fact you can set synaptic to "Apply Changes in Terminal Window" which shows all that would show from an apt-get command.

There is no real point in re-installing the OS if it otherwise working as you want, so go to synaptic and see what you've been missing.