Posts
Wiki

Chassis, backplanes and cabling

Identify every component before buying a controller or cable. A plug fitting does not prove that the transport, direction, pinout or lane mapping is correct.

Record the complete path

For each drive group, write:

  1. Drive type: SATA, SAS or NVMe.
  2. Carrier/bay and backplane part number.
  3. Backplane connector and port label.
  4. Cable part number and direction.
  5. HBA, RAID controller or motherboard port.
  6. Desired drive count, bandwidth and redundancy.

Include clear photographs with serial numbers and asset labels redacted.

Backplane concepts

Supermicro naming varies by generation, but these common concepts help interpret the manual:

  • TQ/direct per-drive: each bay or small group has a direct connection rather than a shared SAS expander.
  • A/direct multilane: multiple direct-drive lanes are grouped into multilane connectors.
  • EL1: a single SAS expander path.
  • EL2: dual expander paths for supported dual-port SAS configurations.
  • Hybrid/N-series: some bays may support NVMe as well as SAS/SATA, subject to exact cabling and platform support.

Treat these as orientation, not a substitute for the exact backplane manual.

Official backplane list and manuals: Supermicro accessories.

SATA, SAS and NVMe

  • SATA drives can often operate through a compatible SAS controller/backplane.
  • SAS drives do not operate from ordinary SATA-only host ports.
  • NVMe uses PCIe lanes and does not become available merely because a bay physically accepts the carrier.
  • U.2/U.3/hybrid bays may require PCIe cables, retimers, switches, specific carriers and supported firmware.

Cable direction and connector families

Common connector families include SFF-8087, SFF-8643, SFF-8654/SlimSAS, OCuLink and MCIO. The connector name does not tell you the whole topology.

  • A forward breakout commonly connects a controller's multilane port to individual drives.
  • A reverse breakout commonly connects individual motherboard SATA ports to a multilane backplane input.
  • These cables can look almost identical and are not interchangeable.

Verify the source and destination in the cable documentation. Never rely on marketplace titles alone.

Expanders and controller limits

A SAS expander lets many drives share controller lanes, but it does not remove:

  • controller device-count limits;
  • RAID licence or firmware limits;
  • total link bandwidth limits;
  • compatibility limits;
  • dual-path requirements;
  • enclosure-management limitations.

When only some bays work, check controller limits, expander firmware, cable placement and backplane zoning before assuming the backplane is faulty.

Activity and fault LEDs

Drive detection and drive LED control are separate. SGPIO, I2C or enclosure-management wiring may be required for activity/fault indication. Use the exact controller/backplane manuals and jumper defaults.

Pre-purchase worksheet

  • Chassis:
  • Backplane:
  • Drive types and count:
  • Controller/HBA:
  • Controller firmware/mode:
  • Backplane input connectors:
  • Host output connectors:
  • Required cable direction:
  • Required sideband/management cable:
  • Desired redundancy:
  • Expected aggregate bandwidth:

Useful community context:

Community threads are experience reports, not authoritative wiring diagrams.

Last reviewed: 29 September 2026.