Problem mit Update PBS

h725rk

Member
May 17, 2023
10
2
8
Hallo,

ich habe aktuell das Problem, das der Kernel nicht aktualisiert wird, da angeblich auf der Festplatte kein Platz mehr ist, was komisch ist, da dies nicht stimmt.
Das ist der Fehler:
Code:
No /etc/kernel/cmdline found - falling back to /proc/cmdline
Copying and configuring kernels on /dev/disk/by-uuid/6C4C-8D6F
        Copying kernel 6.14.11-5-pve
cp: error writing '/var/tmp/espmounts/6C4C-8D6F/vmlinuz-6.14.11-5-pve': No space left on device
run-parts: /etc/initramfs/post-update.d//proxmox-boot-sync exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.14.11-5-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.14.11-5-pve-signed (--configure):
 installed proxmox-kernel-6.14.11-5-pve-signed package post-installation script subprocess returned error exit status 2
Setting up python3-urllib3 (2.3.0-3+deb13u1) ...
Setting up bind9-host (1:9.20.18-1~deb13u1) ...
dpkg: dependency problems prevent configuration of proxmox-kernel-6.14:
 proxmox-kernel-6.14 depends on proxmox-kernel-6.14.11-5-pve-signed | proxmox-kernel-6.14.11-5-pve; however:
  Package proxmox-kernel-6.14.11-5-pve-signed is not configured yet.
  Package proxmox-kernel-6.14.11-5-pve is not installed.
  Package proxmox-kernel-6.14.11-5-pve-signed which provides proxmox-kernel-6.14.11-5-pve is not configured yet.

dpkg: error processing package proxmox-kernel-6.14 (--configure):
 dependency problems - leaving unconfigured
Setting up proxmox-kernel-6.17.4-2-pve-signed (6.17.4-2) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.17.4-2-pve /boot/vmlinuz-6.17.4-2-pve
update-initramfs: Generating /boot/initrd.img-6.17.4-2-pve
W: No zstd in /usr/bin:/sbin:/bin, using gzip
I: The initramfs will attempt to resume from /dev/dm-0
I: (/dev/mapper/pbs-swap)
I: Set the RESUME variable to override this.
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.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/6C4C-8D6F
        Copying kernel 6.14.11-5-pve
cp: error writing '/var/tmp/espmounts/6C4C-8D6F/vmlinuz-6.14.11-5-pve': No space left on device
run-parts: /etc/initramfs/post-update.d//proxmox-boot-sync exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.17.4-2-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.17.4-2-pve-signed (--configure):
 installed proxmox-kernel-6.17.4-2-pve-signed package post-installation script subprocess returned error exit status 2
Setting up proxmox-kernel-6.17.4-1-pve-signed (6.17.4-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.17.4-1-pve /boot/vmlinuz-6.17.4-1-pve
update-initramfs: Generating /boot/initrd.img-6.17.4-1-pve
W: No zstd in /usr/bin:/sbin:/bin, using gzip
I: The initramfs will attempt to resume from /dev/dm-0
I: (/dev/mapper/pbs-swap)
I: Set the RESUME variable to override this.
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.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/6C4C-8D6F
        Copying kernel 6.14.11-5-pve
cp: error writing '/var/tmp/espmounts/6C4C-8D6F/vmlinuz-6.14.11-5-pve': No space left on device
run-parts: /etc/initramfs/post-update.d//proxmox-boot-sync exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.17.4-1-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.17.4-1-pve-signed (--configure):
 installed proxmox-kernel-6.17.4-1-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.17:
 proxmox-kernel-6.17 depends on proxmox-kernel-6.17.4-2-pve-signed | proxmox-kernel-6.17.4-2-pve; however:
  Package proxmox-kernel-6.17.4-2-pve-signed is not configured yet.
  Package proxmox-kernel-6.17.4-2-pve is not installed.
  Package proxmox-kernel-6.17.4-2-pve-signed which provides proxmox-kernel-6.17.4-2-pve is not configured yet.

dpkg: error processing package proxmox-kernel-6.17 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.17; however:
  Package proxmox-kernel-6.17 is not configured yet.

dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
Setting up bind9-dnsutils (1:9.20.18-1~deb13u1) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for libc-bin (2.41-12+deb13u1) ...
Processing triggers for initramfs-tools (0.148.3) ...
update-initramfs: Generating /boot/initrd.img-6.17.4-2-pve
W: No zstd in /usr/bin:/sbin:/bin, using gzip
I: The initramfs will attempt to resume from /dev/dm-0
I: (/dev/mapper/pbs-swap)
I: Set the RESUME variable to override this.
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.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/6C4C-8D6F
        Copying kernel 6.14.11-5-pve
cp: error writing '/var/tmp/espmounts/6C4C-8D6F/vmlinuz-6.14.11-5-pve': No space left on device
run-parts: /etc/initramfs/post-update.d//proxmox-boot-sync exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 proxmox-kernel-6.14.11-5-pve-signed
 proxmox-kernel-6.14
 proxmox-kernel-6.17.4-2-pve-signed
 proxmox-kernel-6.17.4-1-pve-signed
 proxmox-kernel-6.17
 proxmox-default-kernel
 initramfs-tools
Error: Sub-process /usr/bin/dpkg returned an error code (1)

Hier ist noch die Übersicht meiner Festplatte:
Code:
root@pbs:~# df -h
Filesystem               Size  Used Avail Use% Mounted on
udev                     1.9G     0  1.9G   0% /dev
tmpfs                    392M  688K  391M   1% /run
/dev/mapper/pbs-root     144G   32G  105G  24% /
tmpfs                    2.0G     0  2.0G   0% /dev/shm
tmpfs                    5.0M     0  5.0M   0% /run/lock
tmpfs                    1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs                    2.0G     0  2.0G   0% /tmp
tmpfs                    2.0G  348K  2.0G   1% /run/proxmox-backup
172.0.0.3:/NASBackupNFS  2.7T  2.0T  741G  73% /mnt/NASBackupNFS
tmpfs                    1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs                    392M  8.0K  392M   1% /run/user/0

Kann einer zufälliger Weise sagen, warum ich trotz freien Festplattenplatz den Kernel nicht aktualisieren kann?

Schönen Montag,
Rob
 
Das sieht mir eher so aus, als ob deine EFI-Partition voll ist (siehe [..] espmounts/6C4C-8D6F [..]).
Gib mal bitte proxmox-boot-tool status

Edit:

Probier bitte auch mal
  • mkdir -p /mnt/esp;mount /dev/disk/by-uuid/6C4C-8D6F /mnt/esp;df -h /mnt/esp;umount /mnt/esp;rm -rf /mnt/esp
  • (Gibt bestimmt hier jemanden der mit awk/sed einen Einzeiler bauen mag um die Usage der Partition auszugeben, aber so gehts auch ;-))
 
Last edited:
  • Like
Reactions: Gilou
Folgendes bekomme ich bei
Code:
proxmox-boot-tool status
Code:
root@pbs:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with legacy bios
6C4C-8D6F is configured with: uefi (versions: grubx64.efi), grub (versions: 6.14.11-4-pve, 6.14.11-5-pve, 6.17.2-1-pve, 6.17.4-1-pve)

Bei
Code:
mkdir -p /mnt/esp;mount /dev/disk/by-uuid/6C4C-8D6F /mnt/esp;df -h /mnt/esp;umount /mnt/esp;rm -rf /mnt/esp
bekomme ich folgendes:
Code:
root@pbs:~# mkdir -p /mnt/esp;mount /dev/disk/by-uuid/6C4C-8D6F /mnt/esp;df -h /mnt/esp;umount /mnt/esp;rm -rf /mnt/esp
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2       511M  511M     0 100% /mnt/esp

Ist wohl zu klein und das System fährt nicht in EFI hoch. Wie kann ich das lösen?