Hi,
today, I tried to update my system with zypper dup. I got the following error messages:
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-2.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-19.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-21.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-57.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-58.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-59.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-60.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-105.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-106.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-107.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-110.conf
Removed /boot/efi/loader/entries/snapper-opensuse-tumbleweed-6.19.3-1-default-111.conf
ERROR: No free space in /boot/efi for new kernel
ERROR: No free space in /boot/efi for new kernel
Garbage after device path end, ignoring.
Garbage after device path end, ignoring.
Garbage after device path end, ignoring.
Garbage after device path end, ignoring.
WARNING:esys:src/tss2-esys/api/Esys_PolicyOR.c:286:Esys_PolicyOR_Finish() Received TPM Error
ERROR:esys:src/tss2-esys/api/Esys_PolicyOR.c:100:Esys_PolicyOR() Esys Finish ErrorCode (0x000001c4)
None of the alternative values for PCR 8 encoded in policy match the current TPM state. Either the system has been tempered with or the provided policy is incorrect.
Error creating the systemd-pcrlock policy!
warning: %post(kernel-default-6.19.5-1.1.x86_64) scriptlet failed, exit status 1
( 648/2874) Installieren: kernel-default-6.19.5-1.1.x86_64 ........................................................................................[fertig]
/sbin/augenrules: No change
No rules
Updating /etc/sysconfig/backup ...
[..]
Ausgabe des Skripts %posttrans(coreutils-9.10-3.1.x86_64):
ERROR: No free space in /boot/efi for new kernel
warning: %posttrans(coreutils-9.10-3.1.x86_64) scriptlet failed, exit status 1
Error from %posttrans(coreutils-9.10-3.1.x86_64)
Ausgabe des Skripts %posttrans(java-25-openjdk-headless-25.0.2.0-1.2.x86_64):
++ /usr/bin/file --mime-type -b /var/lib/ca-certificates/java-cacerts
++ stat -c %s /usr/lib64/jvm/java-25-openjdk-25/lib/security/cacerts
++ /usr/bin/file --mime-type -b -L /usr/lib64/jvm/java-25-openjdk-25/lib/security/cacerts
Ausgabe des Skripts %posttrans(selinux-policy-targeted-20260219-2.2.noarch):
++ SELINUX=enforcing
++ SELINUXTYPE=targeted
++ SELINUX=enforcing
++ SELINUXTYPE=targeted
skipping the directory /sys
skipping the directory /proc
skipping the directory /mnt
skipping the directory /var/tmp
skipping the directory /home
skipping the directory /root
skipping the directory /tmp
Ausgabe des Skripts %posttrans(container-selinux-2.246.0-1.2.noarch):
++ SELINUX=enforcing
++ SELINUXTYPE=targeted
Ausgabe des Skripts %posttrans(tpm2.0-abrmd-selinux-3.0.0-8.2.noarch):
++ SELINUX=enforcing
++ SELINUXTYPE=targeted
Ausgabe des Skripts %posttrans(flatpak-selinux-1.16.3-1.2.noarch):
++ SELINUX=enforcing
++ SELINUXTYPE=targeted
Ausgabe des Skripts %transfiletriggerin(sdbootutil-1+git20260210.81c4815-1.2.x86_64):
2.14-202602091118 == 2.14-202602091118
Nach-Transaktions-Skripte werden ausgeführt .......................[fertig]
After reboot I only have one entry in Grub: the old kernel 6.19.3. The system booted normal. Before there were several entries from snapshots.
I tried to run zypper dup again, but there are no updates. Then, I decided to switch to the old snapshop bevor the update. Zypper doesn’t show any updates. I switched to an even older snapshot from yesterday, same problem, not update from zypper.
On the weekend I reinstalled my whole system with whole disk encryption and secure boot. Before, I had two efi-Partitions
nvme0n1p1 and
nvme0n1p7
Now, I only have the first parition.
It is a dual boot system.
> lsblk -f ~@localhost.localdomain
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1 vfat FAT32 SYSTEM FCE1-6693 73,9M 72% /boot/efi
├─nvme0n1p2
├─nvme0n1p3 BitLocker 2 ZENBOOK OS 05.09.2024 882d55fb-287e-4aab-90c7-cf1343f2b166
├─nvme0n1p4 ntfs RECOVERY C0CA7EBCCA7EADF2
├─nvme0n1p5 vfat FAT32 MYASUS 50FC-E440
├─nvme0n1p6 BitLocker 2 ZENBOOK DATA 23.08.2025 b0303910-b5b5-434d-88b7-d6eb28610901
└─nvme0n1p7 crypto_LUKS 2 d59c3afd-8076-4439-9ac6-ba2690bce912
└─cr_nvme-eui.e8238fa6bf530001001b444a41f1ae97-part7
│ LVM2_member LVM2 001 v9ROog-svcX-oLc7-IZOY-WI8V-LzDJ-cy9Rkx
├─system-root btrfs 5e659972-3d04-4e3d-8671-533b8fdc3235 1,2T 41% /var
│ /usr/local
│ /srv
│ /root
│ /home
│ /opt
│ /.snapshots
│ /
└─system-swap swap 1 0b2620ae-7d58-4324-bde9-282dbab86f01 [SWAP]
>
What can I do now? Do you need any additional infos?
Best regards
Kay