Looks like you need to look for messages about /dev/md0 and why it may be timing out. Also maybe add nofail to the raid entry in fstab so you can still boot if the root fs is not on it and it fails ( is root on NTFS possible or good?)
I don’t think the edid message is a problem, just an artifact of your monitor not talking to your video card?
Maybe NTFS is the problem, I think it needs special options to automatically remove the dirty bit and replay the journal
Use the nbd system (network block devices) and qemu to create a qcow2 image with your defective device as the base device. Serve this qcow2 image with qemu-nbd and attach it as a NBD device locally. Then run fsck or testdisk on the NBD device. This will let you repair the filesystem Linux sees without writing to the disk. Testdisk can scan for any filesystems left on the device if the partitions no longer match filesystems.
Also, if all else fails use photorec to slice the file types you need.
Also, ddrescue can try to read any actually failing sectors and work out what they contain, but puts a lot of stress on the device.
Beware, any method that puts more wear on the disk should not be used unless you’re willing to accept the risk that the drive could get worse.
The messages you’re getting sound like they’re from the bootloader, so I think secure boot is not causing the problem… Linux should print some stuff right away when it loads, maybe check the architecture of the kernel you’re trying to boot, even an error immediately after loading the kernel should print something unless the architecture is so different that it’s just feeding the CPU bad instructions… Not sure how the bootloader would get installed correctly in that situation though. Is this after installation? Does the system boot from a live USB or cdrom?
Yes this. Imagine posting to a stack themed site, your question would be closed for being incomplete. A screenshot of the failed boot would be great, and some info about the options you chose when installing and the type of machine you’re using.