CMR (Conventional Magnetic Recording) writes each track independently, so a drive handles sustained random writes without penalty — exactly what a NAS array needs during a RAID rebuild. SMR (Shingled Magnetic Recording) overlaps tracks like roof shingles for higher capacity, but rewriting data disturbs neighboring tracks too, cratering write speed. That gap can turn a rebuild into a multi-day ordeal.
What CMR Does
Conventional Magnetic Recording is how hard drives worked for decades: each concentric track on the platter gets its own lane, with a small buffer of unused space separating it from its neighbors. Because tracks do not overlap, the drive can rewrite any single track in place without touching the data next to it. That independence is what makes random writes and read-modify-write operations fast and predictable — a drive can jump anywhere on the platter and update data immediately, no extra bookkeeping required.
What SMR Trades for Capacity
Shingled Magnetic Recording squeezes more tracks onto the same platter by letting each new track partially overlap the one before it, the way shingles overlap on a roof. That overlap raises areal density — and lowers cost per terabyte — but it comes at a price: writing to an overlapped track can smear the edge of its neighbor. To write anything, the drive often has to read an entire "band" of shingled tracks, hold it in memory, apply the change, and rewrite the whole band. Drives hide this with a small CMR-style cache area and background garbage collection, which is why SMR drives feel normal for light, bursty use and only reveal their limits under sustained write pressure.
Why This Becomes a Crisis Inside a RAID Array
A RAID rebuild is the worst-case write pattern for an SMR drive. When a failed member is replaced, the array must write a long, continuous stream of reconstructed data to the new drive as fast as possible — not bursty, not idle in between, just sustained writes for hours. An SMR drive's small write cache fills almost immediately, and the drive falls back to its shingled read-modify-write housekeeping. Throughput that started in the hundreds of megabytes per second can collapse to a crawl, and some controllers time out entirely, treating a slow-but-working drive as failed. A RAID rebuild already has to touch every surviving drive to reconstruct the missing one — adding a drive that cannot sustain writes turns a stressful process into a genuinely risky one.
The 2020 "Silent SMR" Controversy
In 2020, NAS user communities discovered that several manufacturers had quietly shipped SMR versions of drives inside product lines long assumed to be CMR, without disclosing the change on spec sheets. Owners found out the hard way: RAID rebuilds that stalled for days, or ZFS resilvers that dragged on so long a second failure became a real possibility before the array finished recovering. The backlash forced every major manufacturer to publish clear CMR-vs-SMR technology lists for their drive lineups — information that previously had to be reverse-engineered from forum testing.
How to Tell Which One You're Buying
Check the manufacturer's published technology list before buying, not just the box copy. As a rule of thumb:
- Usually CMR: drives explicitly marketed for NAS and RAID duty — Western Digital's Red Plus and Red Pro lines, Seagate's IronWolf and IronWolf Pro lines
- Often SMR: budget desktop drives, external portable drives, and archive-oriented lines built around cost-per-terabyte rather than sustained I/O
- Openly SMR: Seagate's own Archive HDD line is built on shingled recording by design — fine for a single drive holding cold backups, a poor fit for any RAID member
Bottom Line for NAS Builders
For anything going into a RAID array — mirrored, parity, or otherwise — buy CMR, full stop. Drives like the Western Digital Red Plus 8TB and Seagate IronWolf Pro 4TB are built on conventional recording specifically for sustained, unpredictable I/O. Save SMR for roles that are mostly sequential and rarely rewritten, such as a single external backup target, where its lower cost per terabyte is a genuine advantage rather than a hidden liability. For a deeper look at building out a home array, see our guide to setting up NAS media storage and backup.
Frequently Asked Questions
Can I mix CMR and SMR drives in the same RAID array?
Most controllers will let you try, but the array's rebuild and resync performance is bottlenecked by its slowest member. Mixing technologies defeats the purpose of choosing CMR drives elsewhere in the array.
Is SMR always a bad choice?
No. SMR is a good fit for single-drive, mostly-sequential roles like cold archival storage or a backup target that is written once and rarely touched again. It becomes a problem specifically under sustained random writes, which is exactly what RAID membership demands.
Is SMR noticeably cheaper than CMR?
SMR drives are generally priced somewhat below CMR drives of the same capacity, since the technology's whole purpose is packing more capacity onto the same platter cost. The gap varies by model and is rarely large enough to justify the rebuild risk for a RAID array.
Does SMR affect a single external backup drive the same way it affects a NAS?
Less so. A typical backup job writes data sequentially and infrequently, which plays to SMR's strengths rather than exposing its weaknesses. The risk is concentrated in workloads with heavy random or sustained writes, like a RAID rebuild or a busy multi-user NAS share.
Share this article: Twitter