RAID Levels Explained: RAID 0, 1, 5, 6, 10, 50 and 60 for Business Servers
RAID levels appear in nearly every storage decision, usually as though everyone already knows why RAID 6 beats...
Our RAID guide and backup server build both say "large SAS hard drives" and leave it there. This is the guide that fills in what to actually buy, because spinning drives are still what most file servers, backup targets, surveillance recorders, and NAS builds run on, and the market for them is full of traps that look like bargains.
The most important of those traps is one most buyers have never heard of. Shingled magnetic recording drives are cheaper per terabyte, widely sold, often not clearly labelled, and they fail badly in RAID and ZFS arrays. Not slowly. They cause rebuilds to stall and healthy drives to be ejected from the array at the exact moment the data is least protected. That distinction alone is worth reading this for.
This guide covers SAS versus SATA in practice, spindle speeds and why 15K is effectively finished, CMR versus SMR and how to check, drive classes, the compatibility gotchas on Dell and HPE hardware, and what heat does to spinning drives in Qatar.
At 7,200rpm, a SAS drive and a SATA drive with the same platters have the same mechanics and the same sequential speed. The interface doesn't make the drive faster. What SAS adds is around the drive rather than inside it:
Practical rule: for a backup target or a large file array in a single server, enterprise SATA is fine and cheaper. For a production array under a RAID controller that will see sustained mixed load, nearline SAS (NL-SAS: 7,200rpm platters with a SAS interface) is the standard choice and the price gap is modest. Mixing SAS and SATA in one array works but the array behaves like its weakest member.
Spindle speed sets random access latency, and for years 10K and 15K SAS drives were how you got IOPS out of a database server. SSDs ended that. A SATA SSD delivers hundreds of times the random IOPS of a 15K drive at lower cost per IOP, and the high-speed spinning drive market has shrunk to small capacities as a result.
| Class | Form Factor | Max Capacity | Random IOPS | Latency | Status |
|---|---|---|---|---|---|
| 7.2K SATA / NL-SAS | 3.5" (and 2.5" to ~2TB) | 20TB+ | 75 to 100 | ~12ms | The capacity workhorse |
| 10K SAS | 2.5" | ~2.4TB | 125 to 150 | ~7ms | Legacy, still common in refurbished R640/DL360 |
| 15K SAS | 2.5" | ~900GB | 175 to 210 | ~5ms | Effectively obsolete; replaced by SSD |
| SATA SSD (for comparison) | 2.5" | 8TB | 60,000+ | ~0.1ms | Where the IOPS went |
The practical consequence: buy 7,200rpm drives for capacity and SSDs for performance, and don't buy new 10K or 15K drives at all. The one exception is replacing a failed drive in an existing 10K array on a refurbished server, where matching the array matters more than the spindle speed. Those replacement drives are readily available and cheap precisely because the market has moved on.
If you're inheriting a refurbished server full of 10K SAS drives, they're perfectly serviceable for file storage or a small VM host. Just don't expand the array with more of them for a workload that needs IOPS; put that on a small SSD RAID 10 instead. The pattern is covered in our NVMe, SAS, and SATA SSD comparison.
This is the section to read if you read nothing else. Two recording technologies exist on modern hard drives, and one of them is unsafe in any array.
CMR (Conventional Magnetic Recording)
Tracks sit side by side without overlapping. Any track can be rewritten independently at consistent speed. This is what every enterprise and NAS-class drive uses, and what RAID and ZFS assume.
SMR (Shingled Magnetic Recording)
Tracks overlap like roof shingles to fit more data per platter. Rewriting one track means rewriting every track that overlaps it. Cheaper per terabyte, and catastrophically slow under sustained random writes.
An SMR drive hides the penalty behind a small conventional-recording cache area. For light desktop use, writes land in the cache and get shuffled into the shingled zones during idle time, and the drive behaves normally. A RAID rebuild or ZFS resilver is the opposite of light use: sustained writes across the entire drive with no idle time. The cache fills within minutes, every subsequent write becomes a read-modify-write of a whole shingled band, and throughput collapses.
What happens next is worse than slowness. RAID controllers and ZFS have command timeouts. A drive that stops responding for long enough is treated as failed and ejected. During a rebuild, that means a physically healthy replacement drive gets dropped from the array partway through, the rebuild aborts, and the array is back to degraded or gone. Rebuilds that should take hours take days or never finish, and the window during which a second failure loses everything stretches accordingly.
SMR is acceptable for exactly one role: a standalone archive drive that's written once and rarely rewritten, not in any array. For RAID, ZFS, NAS, backup targets, or anything that will ever be rebuilt, CMR only. This is a data-loss risk, not a performance preference.
Less famous than SMR but the same failure mode. When a hard drive hits a sector it can't read cleanly, it retries. A desktop drive will retry for thirty seconds or more, trying heroically to recover the data on its own. An enterprise or NAS-rated drive caps that at around seven seconds, reports the error, and lets the RAID controller reconstruct the sector from parity. The feature is called TLER by Western Digital, ERC by Seagate, and goes by other names elsewhere.
The reason it matters: most RAID controllers time out a non-responding drive at around eight seconds. A desktop drive in deep recovery looks, to the controller, identical to a dead drive. It gets ejected, the array degrades, and a rebuild starts, all because of one marginal sector that parity could have fixed in milliseconds. In a rebuild, the same thing on a surviving drive fails the rebuild.
Enterprise and NAS-class drives have capped error recovery as standard. Desktop drives don't. This is the second reason, after SMR, that desktop drives don't belong in a server array regardless of how good the price looks.
| Class | Examples | Rated Workload | Suits |
|---|---|---|---|
| Enterprise / data centre | Seagate Exos, WD Ultrastar, Toshiba MG | 550TB/year, 24×7, 2.5M hr MTBF, 5-yr warranty | Any server array. The default. |
| NAS / RAID-rated | IronWolf Pro, WD Red Pro, Toshiba N300 | 300TB/year, 24×7, 1M hr MTBF | Small NAS and lighter arrays; CMR and TLER included |
| Surveillance | Seagate SkyHawk, WD Purple | Sustained sequential write, many streams | NVRs; see our CCTV storage guide |
| Desktop | Barracuda, WD Blue | 55TB/year, 8×5, often SMR, no TLER | Not servers. Not arrays. |
The workload rating is worth understanding. It's the volume of data the drive is warranted to read and write per year. A backup target that ingests 2TB nightly moves over 700TB a year, which exceeds a NAS-class rating and sits comfortably inside an enterprise one. Match the class to the volume, not just to the interface.
Two other things to know about modern large drives. Capacities above roughly 10TB are helium-filled, which reduces drag and heat and is entirely standard. And enterprise 3.5" drives now commonly ship at 16TB, 20TB, and beyond, which brings the RAID 6 rebuild-window argument into force on every array built from them.
Buying a bare drive for a PowerEdge or ProLiant involves three things that waste afternoons if they're not known in advance:
Hard drives are the one server component where "used" needs the most scrutiny, because they're the component with a mechanical life and the most likely to fail. That doesn't make used drives a bad buy; it makes the SMART data mandatory.
Of every component in a server, the hard drive is the one most sensitive to sustained heat. Motors, bearings, and lubricants all age faster, and the failure statistics bear this out: drives run above roughly 40°C fail measurably sooner than drives kept in the low 30s. A full 12-bay chassis of 7,200rpm drives generates its own heat on top of the room's.
| Role | Drive | Notes |
|---|---|---|
| Backup target, 8 to 12 bays | Enterprise 7.2K NL-SAS or SATA, 8 to 16TB, CMR | RAID 6 or RAIDZ2. Workload rating matters here. |
| File server, document shares | Enterprise or NAS-class 7.2K, CMR | RAID 6. NAS-class is adequate for lighter volumes. |
| TrueNAS / ZFS pool | Enterprise 7.2K, CMR, via HBA | CMR is non-negotiable for resilvers. Never SMR. |
| CCTV / NVR | Surveillance-class or enterprise 7.2K | Sustained sequential write rating. |
| VM host or database | Not hard drives | Enterprise SSD in RAID 10. See the SSD endurance guide. |
| Replacing a failed drive in an existing array | Match the array: same capacity, speed, and interface | Even if that means a 10K SAS drive nobody would buy new. |
| Standalone archive, no array | Any CMR drive; SMR tolerable if write-once | The only role where SMR is acceptable. |
At ServerDove Trading & Services, we supply enterprise SAS and SATA hard drives for Dell PowerEdge and HPE ProLiant servers across Qatar, with caddies included, CMR confirmed, sector format verified, and SMART data disclosed on every used drive. Spares are stocked in Doha for same-week replacement.
Not at the same spindle speed. A 7,200rpm SAS drive and a 7,200rpm SATA drive have identical mechanics and sequential throughput. SAS adds dual ports, deeper command queues, and better error handling, which matter under concurrent load and in dual-controller arrays, not in raw speed. High-speed 10K and 15K spindles exist only on SAS.
CMR writes tracks side by side so any track can be rewritten independently. SMR overlaps tracks like roof shingles to fit more data, so rewriting one track means rewriting its neighbours. SMR is cheaper but collapses under sustained random writes, which is exactly what a RAID rebuild or ZFS resilver generates. Never use SMR in an array.
Not in an array. Desktop drives lack capped error recovery, so a marginal sector makes the drive retry for 30 seconds or more and the RAID controller ejects it as failed. Many are also SMR. They're rated for a fraction of the annual workload of an enterprise drive. Enterprise or NAS-class drives cost more for reasons that show up during the first rebuild.
Only to replace a failed drive in an existing 10K array. For any new purchase, 7,200rpm drives provide capacity and SSDs provide performance, and 10K drives are worse at both. They remain cheap and available precisely because the market has moved on.
Usually not. Third-party enterprise drives work in almost all cases, though iDRAC or iLO may flag them as uncertified and some HPE generations show an amber indicator. The drive functions normally. For a production array where every warning matters, vendor-branded drives are the path of least friction. Either way, you need the correct generation-specific caddy.
ServerDove supplies enterprise SAS and SATA hard drives for Dell and HPE servers across Qatar, with caddies, CMR and sector format confirmed, and SMART data disclosed on used drives, delivered in Doha and nationwide with local warranty.
Three rules cover nearly every hard drive purchase for a server. Buy 7,200rpm for capacity and leave performance to SSDs. Buy enterprise or NAS-class, never desktop, because capped error recovery and CMR recording are what keep an array alive through a rebuild. And confirm CMR by exact model number before ordering, because the cheapest large drive on the listing is cheap for a reason.
Then match the caddy to the chassis, keep a spare on the shelf, and keep the drive-heavy server in the cool room. The drives will outlast the server around them.
Tell us your server model, the array you're building, and the capacity you need, and we'll supply the right drives with the right caddies, CMR confirmed, delivered across Qatar with local warranty. Request a Quote · Chat on WhatsApp
RAID levels appear in nearly every storage decision, usually as though everyone already knows why RAID 6 beats...
A backup server isn't a production server with the workload turned down. It has inverted priorities, and Veeam...
The question behind every refurbished purchase: how long before it fails? The answer comes from failure data on...
A rack has to outlast everything else in the server room. Buy a shallow one to save money...