Okay. Then you are in pretty good shape. At least the LVM looks to be intact.
Now repeat those steps. But first make sure that your rescue media is the correct architecture - this typically means 32-bit or 64-bit. In order to rescue, you have to boot from rescue media of the same architecture.
Unlock the LVM as before.
Then mount the root volume. That should be:
# mount /dev/mapper/system-root /mnt
Hmm. I hope you are not using “btrfs”. Because, if you are, you then need to mount the various subvolumes.
If you have a separate “/boot” partition, mount that at “/mnt/boot”.
You should probably also mount “/dev/mapper/system-home” at “/mnt/home”.
If this is a UEFI box, then mount your EFI partition at “/mnt/boot/efi”.
Next step: Look at “/mnt/etc/crypttab”. It might have the wrong device-id for your encrypted partition. You will need to fix that.
Hmm, you unlocked the encryted partition using the symbolic name “cr_lvm” (if you followed my suggestions). Maybe it’s a good idea for consistency, to use that in “/mnt/etc/crypttab”. That’s the first item on that line.
When you think you have all of that setup, then use the following:
# mount --bind /dev /mnt/dev
# mount --bind /sys /mnt/sys
# mount --bind /proc /mnt/proc
# chroot /mnt
That puts you logically inside your mounted system.
# mkinitrd ### remake the initrd
# grub2-mkconfig -o /boot/grub2/grub.cfg
It is possible that you might need to reinstall grub while in that chroot shell. But try it without. So just exit from the chroot environment, then reboot and see if your system now boots properly.