[SOLVED] Cannot remove old kernels, Causes update/upgrade errors

D

DemonChicken1111

New Member
Jun 5, 2025
8
2
3
Hi! I've been trying to update and upgrade my proxmox installation, however I keep getting an error related to an EFI partition being full.

Code: 
@homelab:/# apt-get install intel-microcode
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  iucode-tool
The following packages will be REMOVED:
  proxmox-kernel-6.8.12-8-pve-signed
The following NEW packages will be installed:
  intel-microcode iucode-tool
0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
4 not fully installed or removed.
Need to get 0 B/11.6 MB of archives.
After this operation, 557 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 125768 files and directories currently installed.)
Removing proxmox-kernel-6.8.12-8-pve-signed (6.8.12-8) ...
Examining /etc/kernel/postrm.d.
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
update-initramfs: Deleting /boot/initrd.img-6.8.12-8-pve
run-parts: executing /etc/kernel/postrm.d/proxmox-auto-removal 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
run-parts: executing /etc/kernel/postrm.d/zz-proxmox-boot 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
Re-executing '/etc/kernel/postrm.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/B134-2B37
        Copying kernel and creating boot-entry for 5.15.158-2-pve
        Copying kernel and creating boot-entry for 6.8.12-11-pve
cp: error writing '/var/tmp/espmounts/B134-2B37/EFI/proxmox/6.8.12-11-pve/initrd.img-6.8.12-11-pve': No space left on device
run-parts: /etc/kernel/postrm.d/zz-proxmox-boot exited with return code 1
Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/proxmox-kernel-6.8.12-8-pve-signed.postrm line 15.
dpkg: error processing package proxmox-kernel-6.8.12-8-pve-signed (--remove):
 installed proxmox-kernel-6.8.12-8-pve-signed package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 proxmox-kernel-6.8.12-8-pve-signed
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)

Running proxmox-boot-tool gets me this:

Code: 
@homelab:/# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
B134-2B37 is configured with: uefi (versions: 5.15.158-2-pve, 6.8.12-10-pve, 6.8.12-11-pve)
B136-8FA7 is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
B138-258F is configured with: uefi (versions: 5.15.158-2-pve, 6.8.12-11-pve, 6.8.12-9-pve)
B139-5B94 is configured with: uefi (versions: 5.15.158-2-pve, 6.8.12-11-pve, 6.8.12-9-pve)

After mounting all of the EFI partitions my df -h looks like this:

Code: 
@homelab:/# df -h
Filesystem        Size  Used Avail Use% Mounted on
udev               48G     0   48G   0% /dev
tmpfs             9.5G  1.7M  9.5G   1% /run
rpool/ROOT/pve-1  1.8T   48G  1.8T   3% /
tmpfs              48G   46M   48G   1% /dev/shm
tmpfs             5.0M     0  5.0M   0% /run/lock
efivarfs           64K   22K   38K  37% /sys/firmware/efi/efivars
rpool             1.8T  128K  1.8T   1% /rpool
rpool/ROOT        1.8T  128K  1.8T   1% /rpool/ROOT
rpool/data        1.8T  128K  1.8T   1% /rpool/data
/dev/fuse         128M   20K  128M   1% /etc/pve
tmpfs             9.5G     0  9.5G   0% /run/user/0
/dev/sdd2         511M  511M     0 100% /tmp/fixme/B134-2B37
/dev/sdb2         511M  144M  368M  29% /tmp/fixme/B136-8FA7
/dev/sda2         511M  213M  299M  42% /tmp/fixme/B138-258F
/dev/sdc2         511M  213M  299M  42% /tmp/fixme/B139-5B94

In the /dev/sdd2 partition I have an older kernel left over. I remove it, and it's configuration file, unmount the partition, and still receive the same error.

Code: 
@homelab:/# ls tmp/fixme/B134-2B37/EFI/proxmox/
5.15.158-2-pve  6.8.12-10-pve  6.8.12-11-pve
@homelab:/# rm -rf /tmp/fixme/B134-2B37/EFI/proxmox/5.15.158-2-pve/
@homelab:/# rm /tmp/fixme/B134-2B37/loader/entries/proxmox-5.15.158-2-pve.conf
@homelab:/# umount /dev/sdd2
@homelab:/# apt-get install intel-microcode
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  iucode-tool
The following packages will be REMOVED:
  proxmox-kernel-6.8.12-8-pve-signed
The following NEW packages will be installed:
  intel-microcode iucode-tool
0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
4 not fully installed or removed.
Need to get 0 B/11.6 MB of archives.
After this operation, 557 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 125768 files and directories currently installed.)
Removing proxmox-kernel-6.8.12-8-pve-signed (6.8.12-8) ...
Examining /etc/kernel/postrm.d.
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
update-initramfs: Deleting /boot/initrd.img-6.8.12-8-pve
run-parts: executing /etc/kernel/postrm.d/proxmox-auto-removal 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
run-parts: executing /etc/kernel/postrm.d/zz-proxmox-boot 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
Re-executing '/etc/kernel/postrm.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/B134-2B37
        Copying kernel and creating boot-entry for 5.15.158-2-pve
        Copying kernel and creating boot-entry for 6.8.12-11-pve
cp: error writing '/var/tmp/espmounts/B134-2B37/EFI/proxmox/6.8.12-11-pve/initrd.img-6.8.12-11-pve': No space left on device
run-parts: /etc/kernel/postrm.d/zz-proxmox-boot exited with return code 1
Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/proxmox-kernel-6.8.12-8-pve-signed.postrm line 15.
dpkg: error processing package proxmox-kernel-6.8.12-8-pve-signed (--remove):
 installed proxmox-kernel-6.8.12-8-pve-signed package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 proxmox-kernel-6.8.12-8-pve-signed
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)

How should I go about further diagnoising and resolving this issue?
 
If your EFI partition is full, you have to mount all your EFI partitions manually and remove at least one Kernel with "rm". For example:

Code: 
mount /dev/sdX /boot/efi
# check the available space:
df -h /boo/efi
rm -rf /boot/efi/EFI/proxmox/<kernelversion>
umount /boot/efi

And the next EFI partition.
After you have edited all EFI partitions, remove the kernel that you manually deleted with “rm” using the package manager. For example:

The command purges all kernels with a specified version from the system. e.g. 5.15

Code: 
apt remove proxmox-kernel-<version>* --purge

If everything has been successful so far, you can now remove all unused packages with autoremove. Check the list carefully!

Code: 
apt autoremove --purge
 
@mariol I attempt to do so and still am receiving similar errors

Code: 
@homelab:~# df -h
Filesystem        Size  Used Avail Use% Mounted on
udev               48G     0   48G   0% /dev
tmpfs             9.5G  1.7M  9.5G   1% /run
rpool/ROOT/pve-1  1.8T   48G  1.8T   3% /
tmpfs              48G   49M   48G   1% /dev/shm
tmpfs             5.0M     0  5.0M   0% /run/lock
efivarfs           64K   22K   38K  37% /sys/firmware/efi/efivars
rpool             1.8T  128K  1.8T   1% /rpool
rpool/ROOT        1.8T  128K  1.8T   1% /rpool/ROOT
rpool/data        1.8T  128K  1.8T   1% /rpool/data
/dev/fuse         128M   20K  128M   1% /etc/pve
tmpfs             9.5G     0  9.5G   0% /run/user/0
/dev/sdd2         511M  511M     0 100% /tmp/fixme/B134-2B37
/dev/sdb2         511M  144M  368M  29% /tmp/fixme/B136-8FA7
/dev/sda2         511M  213M  299M  42% /tmp/fixme/B138-258F
/dev/sdc2         511M  213M  299M  42% /tmp/fixme/B139-5B94
@homelab:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
B134-2B37 is configured with: uefi (versions: 5.15.158-2-pve, 6.8.12-10-pve, 6.8.12-11-pve)
B136-8FA7 is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
B138-258F is configured with: uefi (versions: 5.15.158-2-pve, 6.8.12-11-pve, 6.8.12-9-pve)
B139-5B94 is configured with: uefi (versions: 5.15.158-2-pve, 6.8.12-11-pve, 6.8.12-9-pve)
@homelab:~# rm -rf /tmp/fixme/B134-2B37/EFI/proxmox/5.15.158-2-pve/
@homelab:~# rm -rf /tmp/fixme/B138-258F/EFI/proxmox/5.15.158-2-pve/
@homelab:~# rm -rf /tmp/fixme/B139-5B94/EFI/proxmox/5.15.158-2-pve/
@homelab:~# umount /tmp/fixme/B134-2B37
@homelab:~# umount /tmp/fixme/B136-8FA7
@homelab:~# umount /tmp/fixme/B138-258F
@homelab:~# umount /tmp/fixme/B139-5B94
@homelab:~# apt remove pve-kernel-5.15.158-2-pve --purge
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  proxmox-kernel-6.8.12-8-pve-signed pve-kernel-5.15* pve-kernel-5.15.158-2-pve*
0 upgraded, 0 newly installed, 3 to remove and 4 not upgraded.
4 not fully installed or removed.
After this operation, 977 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 125768 files and directories currently installed.)
Removing proxmox-kernel-6.8.12-8-pve-signed (6.8.12-8) ...
Examining /etc/kernel/postrm.d.
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
update-initramfs: Deleting /boot/initrd.img-6.8.12-8-pve
run-parts: executing /etc/kernel/postrm.d/proxmox-auto-removal 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
run-parts: executing /etc/kernel/postrm.d/zz-proxmox-boot 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
Re-executing '/etc/kernel/postrm.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/B134-2B37
    Copying kernel and creating boot-entry for 5.13.19-6-pve
    Copying kernel and creating boot-entry for 6.8.12-11-pve
cp: error writing '/var/tmp/espmounts/B134-2B37/EFI/proxmox/6.8.12-11-pve/initrd.img-6.8.12-11-pve': No space left on device
run-parts: /etc/kernel/postrm.d/zz-proxmox-boot exited with return code 1
Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/proxmox-kernel-6.8.12-8-pve-signed.postrm line 15.
dpkg: error processing package proxmox-kernel-6.8.12-8-pve-signed (--remove):
 installed proxmox-kernel-6.8.12-8-pve-signed package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 proxmox-kernel-6.8.12-8-pve-signed
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)

And after remounting I get this output:

Code: 
@homelab:~# df -h
Filesystem        Size  Used Avail Use% Mounted on
udev               48G     0   48G   0% /dev
tmpfs             9.5G  1.7M  9.5G   1% /run
rpool/ROOT/pve-1  1.8T   48G  1.8T   3% /
tmpfs              48G   49M   48G   1% /dev/shm
tmpfs             5.0M     0  5.0M   0% /run/lock
efivarfs           64K   22K   38K  37% /sys/firmware/efi/efivars
rpool             1.8T  128K  1.8T   1% /rpool
rpool/ROOT        1.8T  128K  1.8T   1% /rpool/ROOT
rpool/data        1.8T  128K  1.8T   1% /rpool/data
/dev/fuse         128M   20K  128M   1% /etc/pve
tmpfs             9.5G     0  9.5G   0% /run/user/0
/dev/sdd2         511M  511M     0 100% /tmp/fixme/B134-2B37
/dev/sdb2         511M  144M  368M  29% /tmp/fixme/B136-8FA7
/dev/sda2         511M  144M  368M  29% /tmp/fixme/B138-258F
/dev/sdc2         511M  144M  368M  29% /tmp/fixme/B139-5B94
 
Last edited:
Here is some more outputs and steps I've taken

Code: 
@homelab:~# for i in $(cat /etc/kernel/proxmox-boot-uuids); do     mount /dev/disk/by-uuid/$i /tmp/fixme/$i; done
@homelab:~# df -h
Filesystem        Size  Used Avail Use% Mounted on
udev               48G     0   48G   0% /dev
tmpfs             9.5G  1.7M  9.5G   1% /run
rpool/ROOT/pve-1  1.8T   48G  1.8T   3% /
tmpfs              48G   49M   48G   1% /dev/shm
tmpfs             5.0M     0  5.0M   0% /run/lock
efivarfs           64K   22K   38K  37% /sys/firmware/efi/efivars
rpool             1.8T  128K  1.8T   1% /rpool
rpool/ROOT        1.8T  128K  1.8T   1% /rpool/ROOT
rpool/data        1.8T  128K  1.8T   1% /rpool/data
/dev/fuse         128M   20K  128M   1% /etc/pve
tmpfs             9.5G     0  9.5G   0% /run/user/0
/dev/sdd2         511M  511M     0 100% /tmp/fixme/B134-2B37
/dev/sdb2         511M  144M  368M  29% /tmp/fixme/B136-8FA7
/dev/sda2         511M  144M  368M  29% /tmp/fixme/B138-258F
/dev/sdc2         511M  144M  368M  29% /tmp/fixme/B139-5B94
@homelab:~# ls /tmp/fixme/B134-2B37/EFI/proxmox/
5.13.19-6-pve  6.8.12-10-pve  6.8.12-11-pve
@homelab:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
B134-2B37 is configured with: uefi (versions: 5.13.19-6-pve, 6.8.12-10-pve, 6.8.12-11-pve)
B136-8FA7 is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
B138-258F is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
B139-5B94 is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
@homelab:~# rm -rf /tmp/fixme/B134-2B37/EFI/proxmox/5.13.19-6-pve/
@homelab:~# df -h
Filesystem        Size  Used Avail Use% Mounted on
udev               48G     0   48G   0% /dev
tmpfs             9.5G  1.7M  9.5G   1% /run
rpool/ROOT/pve-1  1.8T   48G  1.8T   3% /
tmpfs              48G   49M   48G   1% /dev/shm
tmpfs             5.0M     0  5.0M   0% /run/lock
efivarfs           64K   22K   38K  37% /sys/firmware/efi/efivars
rpool             1.8T  128K  1.8T   1% /rpool
rpool/ROOT        1.8T  128K  1.8T   1% /rpool/ROOT
rpool/data        1.8T  128K  1.8T   1% /rpool/data
/dev/fuse         128M   20K  128M   1% /etc/pve
tmpfs             9.5G     0  9.5G   0% /run/user/0
/dev/sdd2         511M  448M   64M  88% /tmp/fixme/B134-2B37
/dev/sdb2         511M  144M  368M  29% /tmp/fixme/B136-8FA7
/dev/sda2         511M  144M  368M  29% /tmp/fixme/B138-258F
/dev/sdc2         511M  144M  368M  29% /tmp/fixme/B139-5B94
@homelab:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
B134-2B37 is configured with: uefi (versions: 6.8.12-10-pve, 6.8.12-11-pve)
B136-8FA7 is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
B138-258F is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
B139-5B94 is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
@homelab:~# umount /tmp/fixme/B134-2B37
@homelab:~# umount /tmp/fixme/B136-8FA7
@homelab:~# umount /tmp/fixme/B138-258F
@homelab:~# umount /tmp/fixme/B139-5B94
@homelab:~# apt remove pve-kernel-5.15.158-2-pve pve-kernel-5.13 pve-kernel-5.13.19-1-pve  pve-kernel-5.13.19-6-pve
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  proxmox-kernel-6.8.12-8-pve-signed pve-kernel-5.13 pve-kernel-5.13.19-1-pve
  pve-kernel-5.13.19-6-pve pve-kernel-5.15 pve-kernel-5.15.158-2-pve
0 upgraded, 0 newly installed, 6 to remove and 4 not upgraded.
4 not fully installed or removed.
After this operation, 1,709 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 125768 files and directories currently installed.)
Removing proxmox-kernel-6.8.12-8-pve-signed (6.8.12-8) ...
Examining /etc/kernel/postrm.d.
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
update-initramfs: Deleting /boot/initrd.img-6.8.12-8-pve
run-parts: executing /etc/kernel/postrm.d/proxmox-auto-removal 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
run-parts: executing /etc/kernel/postrm.d/zz-proxmox-boot 6.8.12-8-pve /boot/vmlinuz-6.8.12-8-pve
Re-executing '/etc/kernel/postrm.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/B134-2B37
    Copying kernel and creating boot-entry for 6.8.12-11-pve
    Copying kernel and creating boot-entry for 6.8.12-17-pve
cp: error writing '/var/tmp/espmounts/B134-2B37/EFI/proxmox/6.8.12-17-pve/initrd.img-6.8.12-17-pve': No space left on device
run-parts: /etc/kernel/postrm.d/zz-proxmox-boot exited with return code 1
Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/proxmox-kernel-6.8.12-8-pve-signed.postrm line 15.
dpkg: error processing package proxmox-kernel-6.8.12-8-pve-signed (--remove):
 installed proxmox-kernel-6.8.12-8-pve-signed package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 proxmox-kernel-6.8.12-8-pve-signed
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)

The partition is still filled, but seemingly with other things now:


Code: 
@homelab:~# df -h
Filesystem        Size  Used Avail Use% Mounted on
udev               48G     0   48G   0% /dev
tmpfs             9.5G  1.7M  9.5G   1% /run
rpool/ROOT/pve-1  1.8T   48G  1.8T   3% /
tmpfs              48G   49M   48G   1% /dev/shm
tmpfs             5.0M     0  5.0M   0% /run/lock
efivarfs           64K   22K   38K  37% /sys/firmware/efi/efivars
rpool             1.8T  128K  1.8T   1% /rpool
rpool/ROOT        1.8T  128K  1.8T   1% /rpool/ROOT
rpool/data        1.8T  128K  1.8T   1% /rpool/data
/dev/fuse         128M   20K  128M   1% /etc/pve
tmpfs             9.5G     0  9.5G   0% /run/user/0
/dev/sdd2         511M  511M     0 100% /tmp/fixme/B134-2B37
/dev/sdb2         511M  144M  368M  29% /tmp/fixme/B136-8FA7
/dev/sda2         511M  144M  368M  29% /tmp/fixme/B138-258F
/dev/sdc2         511M  144M  368M  29% /tmp/fixme/B139-5B94
@homelab:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
B134-2B37 is configured with: uefi (versions: 6.8.12-10-pve, 6.8.12-11-pve, 6.8.12-17-pve)
B136-8FA7 is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
B138-258F is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
B139-5B94 is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
@homelab:~#
 
Is there any reason the the 6.8.12-11 kernel on B134 is so big? It takes up 86% of the partition itself

Code: 
@homelab:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
B134-2B37 is configured with: uefi (versions: 6.8.12-11-pve)
B136-8FA7 is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
B138-258F is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)
B139-5B94 is configured with: uefi (versions: 6.8.12-11-pve, 6.8.12-9-pve)

Code: 
/dev/sdd2         511M  436M   76M  86% /tmp/fixme/B134-2B37
/dev/sdb2         511M  144M  368M  29% /tmp/fixme/B136-8FA7
/dev/sda2         511M  144M  368M  29% /tmp/fixme/B138-258F
/dev/sdc2         511M  144M  368M  29% /tmp/fixme/B139-5B94
 
Steps to resolve:

- Removed all unwanted versions from B134-2B37 (and other partitions where necessary)
- Unmounted the drives
- Rebooted
- Remove the kernels with apt remove

Note this may have to be done multiple times (as was my case with a large backlog of kernels). I think I ended up needing to remove 6 or so kernels in the apt command.

Code: 
mkdir /tmp/fixme

# Mount all EFI partitions
for i in $(cat /etc/kernel/proxmox-boot-uuids);
do   
     echo $i;   
     mkdir /tmp/fixme/$i;   
     mount /dev/disk/by-uuid/$i /tmp/fixme/$i;
done

# Check space
df -h

# Check what kernels are on drives
proxmox-boot-tool status

# Remove unwanted kernels
rm -rf /tmp/fixme/{device ID}/EFI/proxmox/{kernel version}

# Reboot

# Remove kernels via apt
apt remove {kernel version} --purge
apt autoremove --purge

The older kernels were named pve-kernel-{version} whereas the newer kernels are named proxmox-kernel-{version}. I am unsure why the reboot helped me out in my case but it now is working again.
 
Last edited:
  • Like
Reactions: mariol and Onslow
Thanks for the Update.

Code: 
/dev/sdd2         511M  511M     0 100% /tmp/fixme/B134-2B37

I am unsure why the reboot helped me out in my case but it now is working again.
Click to expand...
If a file system is 100% full, the kernel may not recognize this correctly even after files have been deleted. A reboot will help in this case.
Perhaps “partprobe” would have helped too.

Good that everything is working great again.
 
You must log in or register to reply here.
Top Bottom