Problem mit Update PBS

h725rk · 2026-01-26T07:12:59+0100

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

fstrankowski · 2026-01-26T09:51:30+0100

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 ;-))

h725rk · 2026-01-26T10:51:28+0100

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?

Impact · 2026-01-26T15:08:18+0100

Teile bitte mal uname -a und dpkg -l "*kernel*". Vielleicht bereinigt apt autoremove --purge ja bereits ein paar alte kernel. Ansonten könnten wir das manuell machen.
Den Inhalt zu sehen wäre auch interessant gewesen. Zb. hiermit

Bash:

mkdir -p /mnt/esp; mount /dev/disk/by-uuid/6C4C-8D6F /mnt/esp; find /mnt/esp/ -type f -exec du -h {} + | sort -h; umount /mnt/esp; rmdir /mnt/esp

Ich habe den meisten Code von oben beibehalten aber ohne rm -rf. Das halte ich hier für zu gefährlich und unnötig.

fstrankowski · 2026-01-26T16:15:05+0100

Impact said:
Das halte ich hier für zu gefährlich und unnötig.

Der Code ist weder das eine noch das andere. Ich möchte, dass das System des OPs nicht verändert wird durch meine Hilfestellungen. Dazu gehören unnötige Ordner wo OP sich am Ende ggf. garnicht dran erinnern kann.

Impact · 2026-01-26T16:29:05+0100

Unnötig weil der Ordner nach umount leer sein sollte und man daher das sicherere rmdir benutzen kann.
Gefährlich da hier ; und kein && benutzt wird. Falls umount aus irgendeinem Grund fehlschlägt, kann es sein, dass ungewollt Dateien gelöscht werden.
Das ist nur meine subjektive Meinung und war nicht als Angriff gemeint sondern nur als Erklärung warum ich von dem bestehenden Code abgewichen bin.

h725rk · 2026-01-26T16:58:10+0100

Folgende Ausgabe habe ich bei uname -a

Code:

Linux pbs 6.17.2-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.2-1 (2025-10-21T11:55Z) x86_64 GNU/Linux

Und folgende Ausgabe habe ich für dpkg -l "*kernel*"

Code:

Desired=Unknown/Install/Remove/Purge/Hold
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                Version      Architecture Description
+++-===================================-============-============-==========================================================
un  kernel-common                       <none>       <none>       (no description available)
un  nfs-kernel-server                   <none>       <none>       (no description available)
iU  proxmox-default-kernel              2.0.2        all          Default Proxmox Kernel Image
iU  proxmox-kernel-6.14                 6.14.11-5    all          Latest Proxmox Kernel Image
un  proxmox-kernel-6.14.11-4-pve        <none>       <none>       (no description available)
rH  proxmox-kernel-6.14.11-4-pve-signed 6.14.11-4    amd64        Proxmox Kernel Image (signed)
un  proxmox-kernel-6.14.11-5-pve        <none>       <none>       (no description available)
iF  proxmox-kernel-6.14.11-5-pve-signed 6.14.11-5    amd64        Proxmox Kernel Image (signed)
un  proxmox-kernel-6.14.8-2-pve         <none>       <none>       (no description available)
rc  proxmox-kernel-6.14.8-2-pve-signed  6.14.8-2     amd64        Proxmox Kernel Image (signed)
iU  proxmox-kernel-6.17                 6.17.4-2     all          Latest Proxmox Kernel Image
un  proxmox-kernel-6.17.2-1-pve         <none>       <none>       (no description available)
ii  proxmox-kernel-6.17.2-1-pve-signed  6.17.2-1     amd64        Proxmox Kernel Image (signed)
un  proxmox-kernel-6.17.4-1-pve         <none>       <none>       (no description available)
iF  proxmox-kernel-6.17.4-1-pve-signed  6.17.4-1     amd64        Proxmox Kernel Image (signed)
un  proxmox-kernel-6.17.4-2-pve         <none>       <none>       (no description available)
iF  proxmox-kernel-6.17.4-2-pve-signed  6.17.4-2     amd64        Proxmox Kernel Image (signed)
ii  proxmox-kernel-6.2                  6.2.16-20    all          Latest Proxmox Kernel Image
rc  proxmox-kernel-6.2.16-12-pve        6.2.16-12    amd64        Proxmox Kernel Image
ii  proxmox-kernel-6.2.16-20-pve        6.2.16-20    amd64        Proxmox Kernel Image
rc  proxmox-kernel-6.2.16-6-pve         6.2.16-7     amd64        Proxmox Kernel Image
un  proxmox-kernel-6.8.12-1-pve         <none>       <none>       (no description available)
rc  proxmox-kernel-6.8.12-1-pve-signed  6.8.12-1     amd64        Proxmox Kernel Image (signed)
un  proxmox-kernel-6.8.12-8-pve         <none>       <none>       (no description available)
rc  proxmox-kernel-6.8.12-8-pve-signed  6.8.12-8     amd64        Proxmox Kernel Image (signed)
un  proxmox-kernel-6.8.12-9-pve         <none>       <none>       (no description available)
rc  proxmox-kernel-6.8.12-9-pve-signed  6.8.12-9     amd64        Proxmox Kernel Image (signed)
un  proxmox-kernel-6.8.4-3-pve          <none>       <none>       (no description available)
rc  proxmox-kernel-6.8.4-3-pve-signed   6.8.4-3      amd64        Proxmox Kernel Image (signed)
ii  proxmox-kernel-helper               9.0.4        all          Function for various kernel maintenance tasks.
un  pve-kernel-6.14                     <none>       <none>       (no description available)
un  pve-kernel-6.17                     <none>       <none>       (no description available)
ii  pve-kernel-6.2                      8.0.5        all          Proxmox Kernel Image for 6.2 series (transitional package)
un  pve-kernel-6.2.16-12-pve            <none>       <none>       (no description available)
un  pve-kernel-6.2.16-20-pve            <none>       <none>       (no description available)

Folgende Fehlermeldung bekomme ich bei apt autoremove --purge:

Code:

REMOVING:                      
  proxmox-kernel-6.14.11-4-pve-signed

Summary:
  Upgrading: 0, Installing: 0, Removing: 1, Not Upgrading: 0
  8 not fully installed or removed.
  Freed space: 630 MB

Continue? [Y/n] y
(Reading database ... 85169 files and directories currently installed.)
Removing proxmox-kernel-6.14.11-4-pve-signed (6.14.11-4) ...
Examining /etc/kernel/postrm.d.
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 6.14.11-4-pve /boot/vmlinuz-6.14.11-4-pve
update-initramfs: Deleting /boot/initrd.img-6.14.11-4-pve
run-parts: executing /etc/kernel/postrm.d/proxmox-auto-removal 6.14.11-4-pve /boot/vmlinuz-6.14.11-4-pve
run-parts: executing /etc/kernel/postrm.d/zz-proxmox-boot 6.14.11-4-pve /boot/vmlinuz-6.14.11-4-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/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/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.14.11-4-pve-signed.postrm line 15.
dpkg: error processing package proxmox-kernel-6.14.11-4-pve-signed (--remove):
 installed proxmox-kernel-6.14.11-4-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.14.11-4-pve-signed
Processing was halted because there were too many errors.
Error: Sub-process /usr/bin/dpkg returned an error code (1)

Muss die EFI-Partition erweitert werden?
Ich verstehe den Fehler leider nicht so richtig.

Impact · 2026-01-26T17:25:38+0100

Mir fehlen Informationen über deinen ESP Inhalt und ich gebe hier keine Gewähr aber du könntest noch mal mounten und dann manuell alte Kernel löschen.

Bash:

apt install -y gdu
mkdir -p /mnt/esp
mount /dev/disk/by-uuid/6C4C-8D6F /mnt/esp
gdu /mnt/esp

Wähl die initrd/vmlinux Ordner mit den alten Kernel Namen (nicht 6.17.*) aus und drücke d um sie zu löschen.
Dann wieder entmounten/aufräumen

Bash:

umount /mnt/esp
rmdir /mnt/esp

Probier danach dann noch mal so etwas

Bash:

apt purge --auto-remove proxmox-kernel-6.14 proxmox-kernel-6.14.11-5-pve-signed proxmox-kernel-6.2 pve-kernel-6.2
apt autoremove --purge
apt install -f
proxmox-boot-tool refresh

ich finde das etwas unsauber aber mir fällt gerade kein besserer Weg ein. Eine größere EFI Partition wäre gut aber sie zu vergrößern ist nicht so einfach.

h725rk · 2026-01-26T18:01:32+0100

Da das eine VM ist, kann ich das gerne ausprobieren.

/Edit: Und wenn ich die VM einfach neu installiere? Kann ich die alten Backups, die ich auf mein NAS packe, wieder einbinden?

/Edit2: Ich bekomme nichtmal gdu installiert.

Code:

root@pbs:~# apt install -y gdu
Installing:                     
  gdu

REMOVING:
  proxmox-kernel-6.14.11-4-pve-signed

Summary:
  Upgrading: 0, Installing: 1, Removing: 1, Not Upgrading: 0
  8 not fully installed or removed.
  Download size: 3,420 kB
  Freed space: 619 MB

Get:1 http://ftp.de.debian.org/debian trixie/main amd64 gdu amd64 5.25.0-1+b8 [3,420 kB]
Fetched 3,420 kB in 1s (3,839 kB/s)
(Reading database ... 85169 files and directories currently installed.)
Removing proxmox-kernel-6.14.11-4-pve-signed (6.14.11-4) ...
Examining /etc/kernel/postrm.d.
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 6.14.11-4-pve /boot/vmlinuz-6.14.11-4-pve
update-initramfs: Deleting /boot/initrd.img-6.14.11-4-pve
run-parts: executing /etc/kernel/postrm.d/proxmox-auto-removal 6.14.11-4-pve /boot/vmlinuz-6.14.11-4-pve
run-parts: executing /etc/kernel/postrm.d/zz-proxmox-boot 6.14.11-4-pve /boot/vmlinuz-6.14.11-4-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/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/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.14.11-4-pve-signed.postrm line 15.
dpkg: error processing package proxmox-kernel-6.14.11-4-pve-signed (--remove):
 installed proxmox-kernel-6.14.11-4-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.14.11-4-pve-signed
Processing was halted because there were too many errors.
Error: Sub-process /usr/bin/dpkg returned an error code (1)

Impact · 2026-01-26T19:16:42+0100

Dann musst du wohl ls -lh /mnt/esp und rm -f /mnt/esp/... nutzen.

Search

Search

Problem mit Update PBS

h725rk

Member

fstrankowski

Famous Member

h725rk

Member

Impact

Famous Member

fstrankowski

Famous Member

Impact

Famous Member

h725rk

Member

Impact

Famous Member

h725rk

Member

Impact

Famous Member

We value your privacy