SAS remains the default interface for enterprise arrays, yet most “SAS vs SATA” explanations stop at connector shape. This guide covers what actually matters when specifying SAS drives: backplanes, dual-port behaviour, expanders, interposers and firmware.
1. What SAS actually gives you
SAS (Serial Attached SCSI) is a dual-port interface designed for enterprise storage. The practical differences from SATA:
- Dual port — two independent paths to the drive, so a single cable or controller failure does not take the drive offline in a multi-path array.
- Higher signalling rate — 12Gb/s per lane in current generations, versus 6Gb/s for SATA.
- Expander support — one controller port can address many drives through SAS expanders, which is how large shelves are built.
- Full-duplex — reads and writes can proceed simultaneously, unlike SATA’s half-duplex link.
SAS backplanes accept SATA drives. SATA backplanes do not accept SAS drives. That asymmetry is the first compatibility check, not the last.
2. Backplane, cabling and interposers
In a 3.5-inch SAS shelf, drives may connect directly or through an interposer board. Interposers change the part number and the firmware path; a drive that works in one shelf can fail to enumerate in another with a different interposer revision. When quoting into an existing array, send the shelf model and, if possible, the current drive part number — we match what the array expects.
3. Form factor and connector
- 3.5-inch SAS HDD — nearline capacity tiers in shelves and JBODs.
- 2.5-inch SAS SSD — hot tier and cache in enterprise arrays.
- U.2 / U.3 — NVMe form factors that can look similar to SAS but are PCIe, not SAS. A SAS bay cannot host U.2, and a U.2 backplane does not speak SAS.
4. Firmware and OEM locking
Enterprise arrays from NetApp, Dell EMC and HPE check drive firmware and may reject or persistently flag non-OEM disks, even when the base part number matches. The same physical drive can ship with different OEM firmware revisions. If the target is a branded array, the request must include the array model and, where known, the OEM part number.
5. When SAS is the right choice
- Existing enterprise arrays with SAS backplanes and expanders.
- Multi-path configurations where dual-port resilience is required.
- Mixed SAS/SATA shelves where SAS drives carry the critical data.
When the target is a simple NAS or direct-attached JBOD with SATA backplanes, SATA drives are usually the cheaper and equally appropriate choice.
6. Condition and test evidence
SAS drives are frequently sourced as new-pull or refurbished stock for array maintenance. For any used condition, ask for per-serial evidence: SMART attributes (including grown defect and error counters) and a full surface scan. Batch-level claims are not enough when the drive is going into a degraded or production array.
Procurement checklist
| Check | What to confirm |
|---|---|
| Interface | SAS 12Gb/s (or 6Gb/s for legacy arrays) |
| Backplane | SAS-capable; expander and interposer revision |
| Dual port | Both paths wired and visible to the controller |
| Firmware | OEM revision for NetApp / Dell EMC / HPE arrays |
| Form factor | 3.5-inch HDD or 2.5-inch SSD — not U.2/U.3 |
| Condition | New / new-pull / refurbished, per line item |
| Evidence | SMART dump + surface scan per serial |
How we quote
Send the array or shelf model, the part number you need and the destination country. If the exact part number is unknown, send the capacity, interface and the array model — we will match the OEM firmware revision rather than substituting a similar drive.
Related
- SAS vs SATA vs NVMe: choosing the enterprise SSD interface
- Enterprise HDD catalog
- Enterprise SSD catalog
Models listed in this catalog