PC power, expansion slots, drive connectors and board headers are easy to confuse. Read the actual role, then the interface, then the exact device documentation—before routing a cable or buying an adapter.
Begin with the question
Separate the visible form from the host interface, power role and exact documentation. Each question leads to a source-linked comparison—not a guessed setup.
Field notes 04 / Storage
4 existing references, now with device examples, unresolved requirements and an actionable next check.
P029 / SATA data
Read the drive label and the complete adapter model. A SATA data connector is not the whole drive connection; the USB3S2SAT3CB example also has a documented drive-size limit.
Device examples, evidence & next check →P196 / SAS drive connection
No compatibility conclusion follows from the outline alone. Molex’s 78717-0002 is a named SAS/SATA receptacle example; it does not certify an unknown drive and USB adapter together.
Device examples, evidence & next check →P030 / M.2 storage
The card format and the supported storage interface are separate checks. SM2NGFFMBU33 is a concrete SATA-only enclosure that excludes NVMe and AHCI PCIe drives.
Device examples, evidence & next check →P298 / mSATA / Mini PCIe socket
A shared socket description is not a host-interface verdict. Kingston distinguishes SATA-only mSATA from M.2, while TE describes a particular socket for Mini PCI Express and mSATA.
Device examples, evidence & next check →Use the destination label, PSU documentation and exact connector revision. Never use visual resemblance as proof that wiring or a modular PSU cable is safe.
Read the motherboard, cpu and graphics-card connectors reference ↗02 / FIELD DESKA card that fits does not establish the electrical lane count, link generation, storage protocol, mounting clearance or device firmware support.
Read the key, physical length, installed lanes and protocol reference ↗03 / FIELD DESKDistinguish separate SATA data and power paths from SAS combos and slimline variants. Controller/backplane topology must be documented independently.
Read the a drive-side socket is not a complete route reference ↗04 / FIELD DESKInternal/external shells, high-density revisions, lane groups, direction, protocol and controller implementation must all be checked at the exact adapter and backplane.
Read the connector family does not name the signal reference ↗05 / FIELD DESKLook at the actual board manual and the connector label. Motherboard headers are not universal plugs: incorrect power, keyed position or wiring can damage equipment.
Read the pin key, silk-screen and voltage are separate clues reference ↗Even an apparently correct connector can have an incompatible controller, voltage, modular power lead, cable direction, disabled motherboard slot or unsupported firmware. These pages never certify a combination.
Also learn USB / Thunderbolt / display capability →VISUAL REFERENCE / NOT A PINOUT
These are source-scoped educational descriptions, not safe-repair instructions, pin assignments, connector drawings at scale, electrical validation, manufacturer approval or independently reviewed material. Use genuine device manuals and qualified technical help for high-power wiring. The canonical factual database is preserved unchanged. New outside source URLs remain clearly segregated from registered claims.
PC POWER / SOURCE-QUALIFIED REFERENCE
CPU and PCIe roles, original and revised 16-contact identities, and exact-image requests that remain unresolved.
Open the power role and generation reference →MAIN & AUXILIARY POWER / REFERENCE
ATX roles, PCIe six-position context and the identity of a named bare housing.
Open the power identity guide →
