SATA storage and negotiated interface rates

SATA connects storage devices through a negotiated serial interface whose link rate is separate from useful file throughput.

SATA, or Serial ATA, is a storage interface used by both hard disks and SSDs. A controller sends commands over a serial connection to the drive. The drive's medium then has to perform the requested operation.

The distinction matters when reading specifications: SATA 6Gb/s describes an interface capability. It does not mean an attached HDD supplies six gigabits of movie data each second.

For SATA's 8b/10b encoding, eight data bits occupy ten transmitted bits. The encoding-only calculation for a 6-Gbit/s link is:

6,000,000,000 bits/s × 8/10 ÷ 8 bits/byte
= 600,000,000 bytes/s
= 600 decimal MB/s

Protocol traffic reduces the useful payload ceiling further. An individual drive's actual workload rate can be much lower again. A slow HDD read does not necessarily indicate that its SATA link negotiated incorrectly.

SATA-IO uses the names SATA 1.5Gb/s, SATA 3Gb/s and SATA 6Gb/s for the interface rates. A controller, device and connection must support the negotiated mode. A capable drive on a slower controller does not bypass that controller.

Interpreting an attached drive

Observation What it establishes
SATA 6Gb/s appears in the device specification The specified interface capability
A lower negotiated link rate is reported The rate of this connection
A large sequential copy reaches a given rate That transfer's observed workload result
Small-file operations are slow A latency or workload problem that needs separate evidence

A usual internal arrangement has a SATA data cable and a separate power connection. M.2 SATA devices use another physical arrangement while retaining SATA as the storage protocol. Conversely, an M.2 NVMe device uses NVMe over PCIe. Connector, protocol and medium answer different questions.

For an Emby server, a healthy SATA connection is often sufficient for bulk media reads. The next useful question is whether the workload is limited by the link, the drive's positioning or write behavior, or competition from other requests. Sequential and random I/O helps distinguish those cases.

See Also

References