A neighbor called me last spring because his two-bay Synology had thrown a red light and he was sure his 4TB of family photos were gone forever. They were fine. What worried me was the sentence he said next: "But I don't have a backup, the RAID is my backup." That single belief is the reason I still write about this topic years later.
RAID is one of the most useful and most misunderstood features on a home NAS. It does exactly one job well, and beginners keep asking it to do three or four jobs it was never designed for. Let me walk through the myths I hear most often, and what the reality actually is.
Myth 1: RAID is a backup
This is the big one, so it goes first. RAID protects you from a drive failure, not from a mistake, a virus, or a lightning strike that fries the whole box.
Picture a RAID 1 mirror with two disks. If you delete a folder by accident, that deletion is instantly mirrored to both drives. If ransomware encrypts your files, both copies get encrypted at the same speed. RAID faithfully copies whatever happens, including the bad things.
A real backup lives somewhere the NAS cannot reach in a single action: a USB drive you unplug, a second NAS in another room, or a cloud service. The widely quoted 3-2-1 backup rule is the standard here: three copies, two media types, one offsite.
Myth 2: RAID means my data is safe from corruption
RAID keeps the array online when a disk dies. It does not check whether the bits sitting on those disks are still correct.
Traditional RAID has a nasty habit called silent corruption. A block quietly rots, and standard RAID has no idea which copy is the good one. This is where a checksumming filesystem earns its keep.
File systems like ZFS and Btrfs store a checksum for every block and can detect and repair bad data during a scrub. If you want protection against corruption, the filesystem matters as much as the RAID level. You can read the plain-English version on the ZFS overview page.
Myth 3: More drives always means more safety
New owners often assume a big RAID 5 with six drives is safer than a simple mirror. It is not that simple.
RAID 5 survives exactly one drive failure. Add more disks and you add more chances for a second failure to happen before you finish rebuilding. The larger the array, the longer and riskier the rebuild.
Here is how the common home levels actually compare.
| RAID level | Drives needed | Failures survived | Usable space |
|---|---|---|---|
| RAID 0 | 2+ | 0 | 100% |
| RAID 1 | 2 | 1 | 50% |
| RAID 5 | 3+ | 1 | (n-1) drives |
| RAID 6 | 4+ | 2 | (n-2) drives |
For a four-bay box holding big 12TB or larger drives, I usually steer people toward RAID 6 or a similar dual-parity setup, because a rebuild on huge modern disks can take a day or more, and that is a long window to be one failure from disaster.
Myth 4: RAID 0 counts as redundancy
RAID 0 has the word RAID in it, so beginners assume it protects them. It does the opposite.
RAID 0 stripes data across drives for speed and capacity, with zero redundancy. Lose one drive out of the set and the entire array is gone, every byte on every disk.
Myth 5: A rebuild is quick and risk-free
The first time I replaced a failed drive in a RAID 5, I expected it to finish over lunch. It took nineteen hours, and the whole time the array was running with no safety net.
During a rebuild the surviving drives are read from end to end under heavy load. Those drives are the same age and often the same batch as the one that just died, so the rebuild is exactly when a second failure is most likely.
This is why I nudge people toward dual parity on large arrays and toward mixing drive purchase dates when they can. A rebuild is a stress test, and stress tests find weak parts.
Myth 6: Any RAID setup lets me hot swap and keep working
People assume every NAS lets you yank a bad drive and slot a new one while everything keeps humming. Cheaper and older units do not always support hot swap.
On a budget two-bay unit you may need to shut down before changing a disk. Check your model's manual before a drive dies, not during the panic. Vendors like Synology publish clear guides, for example this drive replacement walkthrough.
How to actually stay safe
- Pick a RAID level that matches how many failures you need to survive, not just the biggest number of drives.
- Keep at least one backup that the NAS cannot delete on its own.
- Run a filesystem scrub on a schedule so corruption is caught early.
- Enable email or push alerts so a failed drive is not discovered months later.
- Test a restore once, because a backup you have never restored is only a hope.
What RAID is really for
Strip away the myths and RAID has a single honest promise: it keeps your files available while you replace a dead drive. That is genuinely valuable, especially if the NAS runs services your household depends on daily.
Just do not let that one promise stand in for backups, corruption checks, or good habits. Treat RAID as the seatbelt, and treat your backup as the airbag, the insurance, and the spare tire. Get both in place and a failed drive becomes a minor Tuesday chore instead of the worst week of your year.
Frequently asked questions
Is RAID 1 a backup for my photos?
No. RAID 1 mirrors every change to both drives instantly, including deletions and ransomware encryption. If you delete a folder it vanishes from both disks at once. You still need a separate backup on a device the NAS cannot reach in a single action.
Which RAID level should a beginner pick for a four-bay NAS?
For general home use, RAID 5 gives a good balance of capacity and single-drive protection. If your drives are 12TB or larger, consider RAID 6 or a dual-parity option, because the long rebuild time makes a second failure more likely. Synology Hybrid RAID is a friendly option if you want flexible drive sizes.
Why is a RAID rebuild considered risky?
During a rebuild the surviving drives are read from end to end under heavy load, and they are usually the same age and batch as the one that failed. That stress is exactly when a second drive is most likely to fail. A rebuild on large disks can also take 12 to 24 hours or more.
Does RAID protect against file corruption?
Standard RAID keeps the array online during a drive failure but does not verify that the stored bits are still correct, so silent corruption can slip through. Filesystems like ZFS and Btrfs add per-block checksums and can detect and repair bad data during a scrub. Run scrubs on a schedule to catch problems early.
Can I always hot swap a failed drive?
Not on every NAS. Many budget and older two-bay units require you to shut the unit down before replacing a disk. Check your specific model's manual before a drive fails so you know the correct procedure in advance.
