[SOLVED] Efi boot zu klein, nach Umzug von grub zu uefi. Kernel Altbestände?

Fischje

Renowned Member
Sep 25, 2014
64
1
73
Mönchengladbach/GER
Hallo,

nach einem Umzug meines rpools von zwei Hdd auf zwei nvme habe ich auch gleich auf uefi gewechselt. Aber ich habe wohl etwas falsch gemacht.

Jedenfals bekomme ich nach dem "sonst erfolgreichen" Umzug jetzt bei apt installs oder apt autoremove folgende fehlerhinweise:

Bash:
root@pve:~# apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  pve-kernel-5.4.128-1-pve
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 289 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 95233 files and directories currently installed.)
Removing pve-kernel-5.4.128-1-pve (5.4.128-1) ...
Examining /etc/kernel/postrm.d.
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 5.4.128-1-pve /boot/vmlinuz-5.4.128-1-pve
update-initramfs: Deleting /boot/initrd.img-5.4.128-1-pve
run-parts: executing /etc/kernel/postrm.d/proxmox-auto-removal 5.4.128-1-pve /boot/vmlinuz-5.4.128-1-pve
run-parts: executing /etc/kernel/postrm.d/zz-proxmox-boot 5.4.128-1-pve /boot/vmlinuz-5.4.128-1-pve
Re-executing '/etc/kernel/postrm.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/4FEA-017C
No linux-image /boot/vmlinuz-5.13.19-6-pve found - skipping
        Copying kernel and creating boot-entry for 5.15.39-3-pve
        Copying kernel and creating boot-entry for 5.15.39-4-pve
Copying and configuring kernels on /dev/disk/by-uuid/83C9-5D53
No linux-image /boot/vmlinuz-5.13.19-6-pve found - skipping
        Copying kernel and creating boot-entry for 5.15.39-3-pve
        Copying kernel and creating boot-entry for 5.15.39-4-pve
[B]cp: error writing '/var/tmp/espmounts/83C9-5D53/EFI/proxmox/5.15.39-4-pve/initrd.img-5.15.39-4-pve': No space left on device[/B]
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/pve-kernel-5.4.128-1-pve.postrm line 14.
dpkg: error processing package pve-kernel-5.4.128-1-pve (--remove):
 installed pve-kernel-5.4.128-1-pve package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 pve-kernel-5.4.128-1-pve
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pve:~#


Irgendwie ist diese Partition zu klein glaube ich, oder es sind im umkehrschluss zu viele "alt-bestände" von kernels da? kann das? ich komme ganz durcheinander mit der systematik.
 
Habs selbst herausgefunden. Dank dieses Threads:

https://forum.proxmox.com/threads/dpkg-hanging-when-upgrading-pve-kernel.95077/#post-412898

Was mich wohl noch wundert:
Bash:
root@pve:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
4FEA-017C is configured with: uefi (versions: 5.15.53-1-pve)
83C9-5D53 is configured with: uefi (versions: 5.15.53-1-pve), grub (versions: 5.15.39-4-pve)

Kann ich den grub loader irgendwie komplett verbannen oder ist das keine gute idee?
 
Last edited:
  • Like
Reactions: datschlatscher

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!