SAS, SATA or NVMe: Picking Drive Interfaces

Capacity numbers get the attention, but the interface decides how storage behaves under pressure: how many operations can be in flight, how low latency can go, and whether the backplane will even accept the drive. On refurbished platforms the question has an extra edge, because generation determines which interfaces the bays speak at all.

SATA: the economics answer

6Gb/s, single-ported, queue depth 32. None of that matters for bulk storage: a backup pool or media library bounded by network speed gains nothing from a fancier interface, and SATA capacity per dollar is unbeatable. Enterprise SATA SSDs with power-loss protection are also the quiet bargain of the used market — superb OS mirrors and general datastores. Know the two limits: single-porting means no dual-controller redundancy paths, and QD32 caps how hard a single busy drive can be driven.

SAS: built for dense, busy chassis

12Gb/s, dual-ported, deep queues, a stricter error-recovery model, and expander-friendly — which is how one controller addresses 24 bays or an external shelf. Dual porting matters in storage arrays where two controllers hold paths to every drive. Used enterprise SAS spinners (10K/15K SFF, 7.2K nearline LFF) are abundant and cheap; SAS SSDs split the latency difference to NVMe while keeping backplane compatibility. Note the rule that surprises people: a SAS controller runs SATA drives, never the reverse.

NVMe: when latency is the product

PCIe lanes straight to the drive, tens of microseconds instead of hundreds, queue depths in the tens of thousands. Databases, heavy virtualization stores and anything with synchronous writes feel the difference immediately. The refurbished-platform catch is mechanical: U.2 hot-swap bays arrive properly with 14G Dell (R640/R740 NVMe-capable backplanes) and HPE Gen10; on 13G/Gen9 the practical route is PCIe add-in-card NVMe — excellent drives, no hot-swap. Check the specific backplane configuration in any listing; NVMe-ready and NVMe-installed are different words for a reason.

Mixing tiers in one box

The standard pattern works well: NVMe (or SAS SSD) mirror for the hot tier, SAS/SATA capacity behind it, boot on its own small mirror. Keep RAID groups interface-uniform — an array runs at its slowest member's character — and remember that one NVMe device can saturate what an entire shelf of spinners once delivered; the network becomes the next bottleneck fast.

The short version

Bulk and backups: SATA. Dense chassis, expanders, dual-path arrays, cheap fast spinners: SAS. Databases and latency-sensitive stores, on 14G/Gen10 or newer: NVMe. Most well-built refurbished servers end up with all three, each doing the job its economics fit.