/usr/bin/sdbootutil: line 620: snapper: command not foun

[crrodriguez]

Snapper is not installed, neither I want to installed, this error shows up every time I update.

If snapper is required then we want to know about it, if it is not then no error should be displayed.

[aplanas]

are you using systemd-boot?

[crrodriguez]

Yes, I am using systemd-boot

[aplanas]

I see ... sdbootutil is only partially supporting systems without snapshots. Those systems are not tested, so any code change will break them.

[crrodriguez]

I see ... sdbootutil is only partially supporting systems without snapshots. Those systems are not tested, so any code change will break them.

So far only this error and the very annoying fact that older initrds are never removed and /boot/efi fills to to brim from the time to time.. it kinda works.

[aplanas]

There are more issues for sure. For example, all the FDE (TPM2, FIDO2 ...) should be failing too.

Systems without snapshots was supported by a contributor (#66), but this use case was never in the original goals, so other changes are breaking it bit by bit.

[crrodriguez]

what should I do?..I can't go back to grub2.. I took this path because grub2 EFI broke when I enabled an XFS filesystem feature in the rootfs that it did not understand..why does it need to know about the rootfs if UEFI only works with VFAT..

[aplanas]

If you know some bash shell we can try to fix it. As you do not have snapper, this means that after the update the one that is calling sdbootutil is suse-module-tools. There are some call, but I think that the one that is relevant is: /usr/bin/sdbootutil --no-reuse-initrd --default-snapshot add-all-kernels

You can run the command and verify that the error after the update comes from this call. Then later you can do bash -x sdbootutil .... to have a full execution trace, and figure out when snapper is called and why.

If we make progress in this direction, we can later debug the initrd issue.

[arvidjaar]

Effectively duplicate of #252