Comment 3 for bug 1918265

Forgot to add the part about data corruption, kernel images and initrd used by grub and systemd-boot are absolutly identicals:

4188eea45cdb76ebe2b313aef0ac9d7d3f2772cdcf536798b2eeef64fd33a810 vmlinuz-5.8.0-44-generic
4188eea45cdb76ebe2b313aef0ac9d7d3f2772cdcf536798b2eeef64fd33a810 efi/1c1f1f7eb0df44baa7b6399299ee251a/5.8.0-44-generic/linux

4fba2fb3cf0a46cfb839687d5431850473bcc702a1334ffc9dfb7aa06bd76694 initrd.img-5.8.0-44-generic
4fba2fb3cf0a46cfb839687d5431850473bcc702a1334ffc9dfb7aa06bd76694 efi/1c1f1f7eb0df44baa7b6399299ee251a/5.8.0-44-generic/initrd

And the file-systems seems clean

root@ubuntu-template:/# e2fsck /dev/disk/by-uuid/94ebc17e-6aca-4e42-b489-b3eaa8a32d90
e2fsck 1.45.5 (07-Jan-2020)
/dev/disk/by-uuid/94ebc17e-6aca-4e42-b489-b3eaa8a32d90: clean, 313/65536 files, 63289/262144 blocks

root@ubuntu-template:/# fsck.vfat /dev/disk/by-uuid/3AA9-F317
fsck.fat 4.1 (2017-01-24)
/dev/disk/by-uuid/3AA9-F317: 34 files, 69881/130812 clusters

Also the issue is happening on another 2012R2 cluster, but on this one i cannot even start the installation process, this is very weird