Which drive is actually hosed? OR: Best way to attempt a fix on a RAID0 or properly retrieve at least some of the files?

At 4 AM last night my trusty Synology DS224+ (2 8TB HDDs, RAID0 config to make single Volume) went oopsie and an apparent power drop took out Drive1 (yes, I now have learned my lesson about redundancy lol, and will probably end up selling this machine and moving up the ladder to greater things). I attempted repairs and online builds etc. as suggested in the UI itself, but nothing would work and mostly it would tell me the drive was now read-only (this was actually true, I could even still view the files in DSM, MacOS Finder UI, and via ssh.

After fiddling with it probably too much and a couple reboots, I had it instead showing Drive2 as the problem bay, not connecting but Detected (in red of course). This made me second guess whether the actual Drive1 was broken, but around this time the filesystem also stopped being accessible via DSM, a Critical System Error warning popped up, and I desperately 'followed up' into the ether on my support ticket. Still no dice yet.

I am self-taught in this stuff so *it's kind of hard for me to in the meantime ascertain what the actual problem is*, except that clearly the RAID0 in Volume1 is not able to talk to itself properly. Of course I thought one HDD crapped out somehow, but I don't even know if the drive (either!) is actually physically hosed, because I went out and got a 2 bay USB dock and have them plugged into a Win10 machine, and I can basically look inside these volumes via DiskInternals Linux Recovery as if, seemingly, nothing is even wrong with them.

If I was better at knowing how to look inside these - or better yet, attempting a hail mary of a repair - I would be in there trying to save my docker-compose.yaml and a few other things worth salvaging. I can accept I might not be able to recover several terabytes of video and music, unless the community just knows of some obvious approach I have been ignoring.

So... Did anything physically fail on these drives? Is there a tool that I can run from Windows or Mac that can just sew these two things back into a Linux RAID0 my Synology will recognize again (not trying the Linux Seagate Bootable USB saga again lol)? Can any of that be done without losing my precious trove of stuff on the drives (or is there something popular I can use to more easily navigate thru and collect the key items)? I see DiskInternals has a paid RAID fix tool but I am guessing the community knows best on this matter.

Apologies if this gets asked seven times a day; I checked around here for similar questions/answers, have read a fair amount of the Synology and Seagate doco, but bad advice and seedy tools grow on trees, and I figured y'all are just going to be much savvier.