/boot No space left on device

ned

Renowned Member
Jan 26, 2015
113
2
83
I just tried to install the new kernel and I git this error

No space left on device

Code:
df -h /boot/
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       488M  471M     0 100% /boot

If I list content no boot partition I get this

Code:
ls /boot
config-4.13.13-1-pve  config-4.4.40-1-pve  config-4.4.67-1-pve      initrd.img-4.13.8-2-pve  initrd.img-4.4.49-1-pve  initrd.img-4.4.83-1-pve   System.map-4.13.8-3-pve  System.map-4.4.59-1-pve  vmlinuz-4.13.13-1-pve  vmlinuz-4.4.40-1-pve  vmlinuz-4.4.67-1-pve
config-4.13.8-1-pve   config-4.4.44-1-pve  config-4.4.76-1-pve      initrd.img-4.13.8-3-pve  initrd.img-4.4.59-1-pve  lost+found                System.map-4.4.35-2-pve  System.map-4.4.62-1-pve  vmlinuz-4.13.8-1-pve   vmlinuz-4.4.44-1-pve  vmlinuz-4.4.76-1-pve
config-4.13.8-2-pve   config-4.4.49-1-pve  config-4.4.83-1-pve      initrd.img-4.4.35-2-pve  initrd.img-4.4.62-1-pve  System.map-4.13.13-1-pve  System.map-4.4.40-1-pve  System.map-4.4.67-1-pve  vmlinuz-4.13.8-2-pve   vmlinuz-4.4.49-1-pve  vmlinuz-4.4.83-1-pve
config-4.13.8-3-pve   config-4.4.59-1-pve  grub                     initrd.img-4.4.40-1-pve  initrd.img-4.4.67-1-pve  System.map-4.13.8-1-pve   System.map-4.4.44-1-pve  System.map-4.4.76-1-pve  vmlinuz-4.13.8-3-pve   vmlinuz-4.4.59-1-pve
config-4.4.35-2-pve   config-4.4.62-1-pve  initrd.img-4.13.8-1-pve  initrd.img-4.4.44-1-pve  initrd.img-4.4.76-1-pve  System.map-4.13.8-2-pve   System.map-4.4.49-1-pve  System.map-4.4.83-1-pve  vmlinuz-4.4.35-2-pve   vmlinuz-4.4.62-1-pve


I thought that old kernels were removed once the new one is installed...

List of installed kernels

Code:
dpkg --list | grep pve-kernel
ii  pve-firmware                         2.0-3                          all          Binary firmware code for the pve-kernel
iF  pve-kernel-4.13.13-1-pve             4.13.13-31                     amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.13.8-1-pve              4.13.8-27                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.13.8-2-pve              4.13.8-28                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.13.8-3-pve              4.13.8-30                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.35-2-pve              4.4.35-79                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.40-1-pve              4.4.40-82                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.44-1-pve              4.4.44-84                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.49-1-pve              4.4.49-86                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.59-1-pve              4.4.59-87                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.62-1-pve              4.4.62-88                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.67-1-pve              4.4.67-92                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.76-1-pve              4.4.76-94                      amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.83-1-pve              4.4.83-96                      amd64        The Proxmox PVE Kernel Image
 
I removed 2 old kernels
Code:
apt-get remove pve-kernel-4.4.76-1-pve
apt-get remove pve-kernel-4.4.83-1-pve

this freed some space...and managed to install the new one...

i got this message



Code:
Setting up proxmox-ve (5.1-31) ...
W: APT had planned for dpkg to do more than it reported back (6 vs 10).
   Affected packages: pve-kernel-4.13.13-1-pve:amd64

Is this something important?
 
I have the same thing, boot gets filled up. autoremove does what ever but does not touch boot.

after deleting some old stuff in boot I managed to finish apt --fix-broken install since it was even for autoremove complaining about the abroted install and no free space on boot.

then I purged like showen here:
https://forum.proxmox.com/threads/proxmox-ve-4-4-kernel-update-failed.34796/post-170623

after that I emptied /boot with rm *18-xx* from everything expet the current (in my case 26) and the before last (in my case 25)

then a reboot and apt-get update && apt-get dist-upgrade.