U.2 (or M.2) SSD connected to OCULink Header on ASRockRack EPYC3251D4I-2T Mainboard is not showing up

Hi everyone, I am not so active here, I apologize, however I am a very regular viewer of the YouTube show.

I am currently wanting to build a no-compromise Home NAS from Quasi-Enterprise Grade Stuff. I have the ASRockRack EPYC3251D4I-2T mainboard (https://www.asrockrack.com/general/productdetail.asp?Model=EPYC3251D4I-2T#Specifications) and want to connect to it:

6x SATA HDD (4x SATA on OCULink 4x Header, 2x SATA on SATA Headers)
5x M.2 SSD (4x PCI-Express x4 from two OCULink x8 Headers, 1xM.2 on-board)

I am currently having a problem connecting up the M.2 SSDs to the OCULink Headers and I am not sure why. I am using the following cables/doodads:

Now the issue is, that no matter what I do, my 4 U.2 (M.2) drives don’t get detected by the UEFI or the Linux Kernel. I have already configured the bios such that the OCULink x8 Headers are in x4x4 Mode and PCIE (not SATA).
The issue has to be the OCULink to U.2 cable in my opinion, but lacking experience with Enterprise stuff, I am unsure where to start looking. In the SFF-9402 spec, this adapter cable is missing a lot of sideband pins on the SFF-8639 (U.2) side, which are present on the OCULink side. E.g.: Two-Wire (SMBUS), CPRSNT[A|B], BP_TYPE[A|B]. Are they not needed? I suspect the PCI-Express Host will require at least some of these pins to have a definite state, if they are not connected through to the SFF-8639 header.

Could this be my problem? How would it be possible to connect the M.2 drives to my OCULink x8 headers?

Thanks a bunch in advance, guys for any pointer you can give me!

EDIT: I can open the OCULink Connector (the other one is overmolded…). Does it make sense to try pulling CPRSNT low permanently?

Okay, I think this can be closed. I just bridge B12/B13 (CPRSNTA and GND) and B33/34 (CPRSNTB and GND). For anyone having the same issue!

Disks are now being detected successfully. Very cool!

4 Likes

This helped me fix a similar issue with the Icy Box M.2 to U.2 2.5" adapter being the common factor.

Bridging P4 to P5 on the adapter resolved this and the drive now shows up. The cable I have connects SFF-8611 pin B13 (CPRSNT#) to SFF-8639 pin P4 while P5 conveniently seems to be grounded.

Honestly not sure which part of this setup is incorrect and the true cause but I have some different cables and adapters on order so will hopefully be able to work it out.

This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.