Guide / DOCUMENTATION & ENGINEERING CONTEXT

PCIe Gen5 SSDs Behind a Gen4 RAID Controller

A Gen5 SSD label describes the drive's capability. System performance depends on the negotiated links and the shared resources between that drive and the application.

Draw the complete path

Trace the route from each SSD through its connector, backplane, any switches, the controller and its host slot. Record link generation and width at each relevant hop. Identify which drives share an upstream connection. Include CPU attachment when the workload crosses a multi-socket topology.

For every adapter or cable, check the supported configuration rather than assuming a physical fit proves electrical compatibility. The final system should expose the expected negotiated links in its diagnostics.

A practical example

Consider Gen5 PM9D3a drives in a proposed H965i-managed array. The drive family's interface capability and the controller's supported NVMe generation differ. That route does not provide a Gen5 drive link through the controller. The exact performance still depends on the rest of the layout and the workload.

This can be an acceptable design if its measured behavior meets the application requirement. It is unsuitable to describe it as an end-to-end Gen5 storage subsystem without checking the full path.

References [1][2]

Understand the size of an upstream link

As an interface illustration, PCIe Gen4 x8 carries approximately 15.75 GB/s in one direction after 128b/130b line encoding but before transaction and other overheads. It is calculated as 16 billion transfers per second multiplied by eight lanes, multiplied by 128/130, and divided by eight bits per byte.

This arithmetic is a link-rate illustration, not a controller benchmark or an application guarantee. Shared resources and workload behavior can reduce delivered throughput further. Do not add simultaneous reads and writes together to claim a one-direction result.

References [3]

Compare three storage designs

DesignQuestion to resolve
Keep the supported Gen4 RAID pathDoes representative application I/O meet the required latency and throughput?
Use a supported Gen5 controller pathAre the server, controller, backplane, cables and drive layout supported together?
Use direct-attached NVMe with software protectionWho manages redundancy, recovery, monitoring and operating-system integration?

Test the final array

Agree the block sizes, read/write mix, queue depth, active dataset, duration and steady-state conditions. Test the normal workload and an agreed degraded/rebuild case where safe and authorized. Report usable capacity, latency distribution and error behavior alongside bandwidth.

A procurement decision should follow the required service level: keep the cheaper design if it meets the requirement; pay for a faster path when the workload can use it.

Sources and documentation

  1. Samsung data center SSD specifications ↗Samsung Semiconductor · checked 17 Nov 2026

    PM9D3a section; family-level interface, form factors, capacity and endurance

  2. H965 and H975 technical specifications ↗Dell · checked 17 Nov 2026

    H965 NVMe Gen4 vs H975 Gen5; restrictions on mixing drive protocols

  3. Intel Core Ultra processor datasheet ↗Intel · checked 17 Nov 2026

    PCIe generation, encoding and theoretical one-direction link bandwidth table