Just wanted to follow up here. I looked into this behaviour further and noticed we’ve had some previous reports of some makes/models of 3TB or 4TB drives not being correctly detected in the SATADOCK22UE. Based on the troubleshooting you’ve already done, and especially since the same drive does work in our newer SDOCK2U33EB, I’m rather sure it is related to this scattered chipset compatibility issue.
That SATADOCK22UE has been discontinued for some time now, and its successor is actually the SDOCK2U33EB you already have. Hopefully, you can repurpose the older one for use with smaller drives in your environment. I’m glad to hear the newer one is working, and I’m sorry I don’t have an easy fix to suggest for that older unit.