2019 Mac Pro + Accelsior 4M2 (Major Issues)

The short of it: 

Running Capture One (C1) and Lightroom (LR) with all content (raw files + catalogs) located on the 8TB Accelsior 4M2 would lead to intermittent app-crashing and subsequently slow transfer speeds to/from the drives at the desktop-level. To regain normal functionality, I have to hard restart. 

I'd love suggestions on what else I could do to fix the issues, but I feel this might be more of a cautionary tale for anyone else considering the 4M2. Prove me wrong? Please?

What happens:

• • Regularly getting 4.5GB/S+ read/write in speed tests prior to crashing.
  • Boards are in 'optimal configuration'.
  • Everything is fine editing photos in C1 for 5 mins and up to 3 hours.
  • Images stop fully-rendering from their cached previews. No consistent trigger that I could tell.
  • No longer able to edit photos at all. The app is not frozen (i can navigate to different panels, etc), but images are non-responsive to any input.
  • Capture One won't quit without force quitting.
  • Capture One will not re-open. The app only bounces in the dock.
  • File transfers from the internal drive to Accelsior drive run at about 1/1000th of normal speeds.
  • Lightroom will also not let me edit photos on the 4M2.
  • Restarts hang, and a hard restart is required.
  • Everything is 100% normal upon restart... until it happens again.

What I've done so far to fix it:

• • Checked activity monitor for any non-responsive processes.
  • Validated all SSD drives on the board.
  • Secure boot is turned off.
  • Uninstall and re-install Capture One.
  • Deleted and re-created all cache for Capture One.
  • Maxed out cache preview sizes at the request of C1 (for the 6k XDR display).
  • Sent crash logs to Capture One (found nothing).
  • Reinstall Catalina OS.
  • Clean install of Catalina OS.
  • Exchanged 4M2 units.
  • Checked temperatures to rule out thermal throttling (request of OWC, found not to be a factor).
  • Moved the board to a different slot (From 6 to 5)
  • Sent diagnostic reports to OWC (still no response yet).
  • Captured system data and sent to Apple, they passed to engineering (nothing found).
  • Cleared Library caches across all applications (including in browser to rule out Malware).
  • Applied read and write permissions to everything within the 4M2 drive.
  • Tested working from photos on Apple SSD, no crashes.
  • Tested working from photos on my NAS, no crashes.
  • I'm sure theres something I'm forgetting, but I think thats everything.

It should also be said that I've worked from various large video files and photoshop files on the 4M2 without issue, but I predominantly work in Capture One. I get the sense C1 is exhibiting the most issues because of the constant read/write to the drives, vs the periodic saving in other uses. 

Basically this issue is intermittent which makes it hard to diagnose, and it lives at a very unfortunate cross-section of first and third party hardware (and a nice software aspect to spice things up further). I do appreciate the lengths all parties went to to resolve this, but they've all come back pointing fingers elsewhere. To me the exact source of the issue isn't super important, but it lies somewhere in the interaction of the 4M2 and the Mac Pro. Whether it's something in the Apple OS/hardware thats problematic, or something only with the 4M2 is a non-issue if nobody takes responsibility. At this point, it's seems like nobodys problem but mine– hence the bit about this being a cautionary tale.

Short of a solution here, the best option for me now is returning the Accelsior 4M2 drives and going with the Apple alternative. This is unfortunate because it's more time lost, the Apple drives are slower, and they're more expensive. And also because when the 4M2 works, it is truly amazing. I can't let that get lost in all this– its a great solution thats plug and play and seems to work for a lot of people... besides me.

So if you made it this far, I hope this is something someone finds useful, or if you happen to have something similar happen or have some ideas, I would LOVE to hear from you. I'm a few days away from calling it and going OEM, but the ideal solutions is getting this to work reliably. 

Thanks.