Seagate ST8000NM0175 8TB SATA Exos HDD: Specs and Shelf Planning
Eight terabytes on SATA in a nearline drive is the most common shape in bulk storage today, and the reason is straightforward economics. This is the capacity point where cost per terabyte, rebuild time and drive availability all sit in a comfortable place at once.
The Seagate ST8000NM0175 is an 8TB SATA 6Gb/s 7200RPM 3.5-inch Exos drive, and it is the sort of part that fills backup targets and archive tiers by the shelf-load.
Why 8TB became the default bulk capacity
Capacity decisions in bulk storage are a balance between three competing pressures, and 8TB sits close to the middle of all three.
Cost per terabyte improves as capacity rises, up to a point. Very large drives carry a premium for being at the leading edge, and very small ones waste bay slots. The middle of the range is usually the sweet spot.
Rebuild exposure worsens as capacity rises. An 8TB rebuild is long — measured in many hours — but it does not stretch into the day-plus windows that 12TB and 14TB drives can produce, which shortens the period during which a second failure would be fatal.
Bay efficiency improves with capacity. Twenty-four 8TB drives in a 4U enclosure deliver a great deal of raw capacity on one power and cooling footprint, and rack space is a recurring cost rather than a one-off.
The practical result is that 8TB drives populate a very large share of the backup, archive and media storage deployed over the last several years, which is also why they are readily available refurbished.
ST8000NM0175 specifications
| Part Number | ST8000NM0175 |
| Manufacturer | Seagate |
| Product Family | Exos |
| Capacity | 8TB |
| Interface | SATA 6Gb/s |
| Rotational Speed | 7200 RPM |
| Form Factor | 3.5 inch LFF |
| Drive Class | Enterprise Nearline |
| Condition | Refurbished, function-tested |
| Warranty | 30-day TechSellerUSA warranty |
SATA is the right interface here
The instinct that a drive this size deserves SAS is understandable and usually wrong for what these drives do.
Bulk nearline workloads are sequential. Backup software writes large streams. Archives are written once and read rarely. Media and object storage move big files. Surveillance recording is continuous sequential write. None of these generate the deep concurrent command queues that SAS is built to handle, so the SAS premium buys capability the workload never uses.
What these workloads do care about is cost per terabyte, and across a fully populated shelf the SATA saving is significant.
The SAS argument holds where you have redundant controllers and genuinely need dual-port path redundancy, where the array serves production traffic throughout rebuilds, or where the backplane already runs SAS and mixing interfaces behind one expander would cause complications. Outside those, SATA at 8TB is the sensible choice rather than the cheap one.
SKU: ST8000NM0175 | Refurbished & function-tested | 30-day warranty
View Details & Request a Quote →Building a shelf around 8TB drives
Three things worth settling before you order the drives rather than after.
RAID level. At 8TB, RAID 6 or another double-parity scheme is the sensible default. Rebuilds run for many hours, during which a single-parity array has no redundancy left and every surviving drive is under sustained read load — precisely the condition that provokes a second failure.
Spares allocation. A hot spare within the array lets a rebuild begin automatically rather than waiting for someone to notice. A cold spare on the shelf then restores full protection quickly once the hot spare is consumed. On a large shelf, budget for both.
Group sizing. Very wide RAID groups increase both rebuild time and the number of drives that must survive it. Several smaller groups usually recover faster and fail less catastrophically than one very wide one, at the cost of a little more parity overhead.
Bare drive, generic chassis
This is the manufacturer part with no server carrier and no OEM firmware coding, which makes it correct for Supermicro builds, white-box storage servers, JBOD enclosures and NAS units using generic trays. It costs less than an OEM-branded drive built on the same mechanism.
It is the wrong choice where an HPE Smart Array, Dell PERC or IBM ServeRAID controller expects vendor firmware, or where you need the tray supplied. Our compatibility guide covers which part numbers apply to which platform.
Ordering
We supply the ST8000NM0175 refurbished and function-tested with a 30-day warranty, single spares or in volume for shelf population. At this capacity the saving against new is substantial, which is why many operations buy refurbished for bulk tiers and keep new-drive budget for performance storage. Browse the full Seagate range or our complete enterprise hard drives catalogue.
Common questions
Why is 8TB such a common bulk storage capacity?
It balances three competing pressures well: cost per terabyte is good without paying the leading-edge premium, rebuild time is long but not the day-plus window that 12TB and above produce, and bay efficiency is strong on a single power and cooling footprint.
Is SATA acceptable on an 8TB enterprise drive?
Yes, for the sequential workloads these drives serve — backup, archive, media and surveillance. None generate the deep concurrent command queues SAS is built for, so the SAS premium buys capability the workload never uses. Choose SAS behind redundant controllers or where the backplane already runs SAS.
What RAID level should I use with 8TB drives?
RAID 6 or another double-parity scheme. Rebuilds run for many hours, during which a single-parity array has no redundancy left and every surviving drive is under sustained read load, which is exactly when a second failure tends to arrive.
Should I use one wide RAID group or several smaller ones?
Several smaller groups usually recover faster and fail less catastrophically, because a very wide group increases both rebuild time and the number of drives that must survive it. The cost is a little more parity overhead.
Filling a shelf? Tell us the bay count and RAID level and we will quote the drives plus spares.
