Before, as you said, it was hard to see where boot process stuck without detail output. I will try what you suggested it if it comes back. Only lines that i could see was Loading Linux linux ... Loading initial ramdisk ...
Randomly, sometims lts, sometimes linux, sometimes both, but fallback (both) was always working.
Chaning bootloader was not so smooth in my case. It didnt work with first try. I had to chroot, even format EFI partition again...
]]>Boot freezes
If booting gets stuck without any error message after GRUB loading the kernel and the initial ramdisk, try removing the add_efi_memmap kernel parameter.
Do you know where that kernel parameter should be? I don't see it in /etc/default/grub.conf
]]>If you really think you'd want to do this you can move the current kernel images/files that are in /boot to /boot/efi and then change the mount point in fstab. It doesn't inherently matter whether boot is empty, but systemd-boot needs to be able to reach the vmlinuz and initramfs images and that is easiest done by copying them to the ESP and mounting said ESP to /boot so that they will be automatically updated on kernel version bumps.
But again the only boot error you have a slight chance of fixing by doing that if your root filesystem wasn't found occasionally but that kind of error would be very visible, you won't fix any issue that is unrelated to identifying the root partition by doing that switch.
]]>