Ask HN: What type of personal NAS would you recommend?
It's 2021 and I am still using my home-built NAS (FreeNAS!), but I am increasingly interested in reducing energy consumption and maintenance time (mostly to improve compatibility with the family life, which leaves me less time to tinker with hardware).
So I humbly ask the hivemind:
- what are good solutions for storing personal backup on-site (other than a bunch of external hard drives)?
- What are some caveats that I should avoid?
- Can I trust the 'standard' companies (Synology, QNAP, Seagate, ...) to keep my data sufficiently safe?
Strong opinions, war stories, and all other suggestions are highly welcome!
113 comments
[ 2.5 ms ] story [ 180 ms ] threadI always comeback to FreeNAS, which I have had configured various ways. I recently updated all my core hardware to mac mini so it has power/sleep modes that save that energy consumption...however payback is a lot longer than a PC..
In the end it will always be a challenge of performance vs. energy consumption.
One thing that surprised me was RAID - I am not very experienced with home servers and such and was really disheartened by how much of my disk got eaten up by RAID. I was using the Synology Hybrid RAID which I think is similar to RAID 5.
TL;DR Synology is pricey but full featured and very pleasant, understand your RAID configuration before you purchase disks.
EDIT: Another thing I will say is that docker compose is not supported IIUC, so just watch out for that if your configuration depends on that (like mine initially did).
The NAS is an underpowered DS216 (two 5.25" drives mirrored, 800MHz ARM, 256MB RAM) that I'd bought new, foolishly assuming the official OS would work just fine on it. More fool me, eh?
I still have the device - but I am never buying another, and I actively disrecommend Synology going forward.
My next NAS box will probably be an old Microserver running FreeNAS or some reasonable OS. The Synology's predecessor was a tiny Linux box that I had to install my desired services on by hand, so I know it's feasible.
One thing to watch out for is upgradability. My system has 4 GB of RAM, which is Not A Lot. There's an easily-accessible SODIMM slot that I can throw an 8 GB stick into, and an almost-completely-inaccessible SODIMM slot with the original 4 GB. If you're going to have slow disks you'll need lots of disk cache, and maxing out mine is looking to be a full afternoon project and not a quick in-and-out.
SHR1/2 is basically RAID 5/6 but with a mechanism for handling disks that have different sizes. Basically it breaks the disks up into partitions such that any "extra" space on other disks becomes part of another array which is only redundant within the disks that have that space.
Anyways, SHR1 is 1 disk redundancy so you should see (disk_count * space_per_disk) - space_per_disk for an array where all the disks are the same size. SHR2 has 2 disk redundancy and I'm sure you can figure out the math for that. Are you not seeing the expected amount?
For the record, I like synology. They keep updating old hardware for an incredibly long time. My parents have my old DS212j (release 11/2011) and it can run the latest DSM 6.
The one thing that burned me recently is DSM version 7 removed support for any USB device that's not a mass storage device. This effectively kills a lot of what I love about the Synology. Next time I'll probably roll my own.
My friend however wanted a no hassle solution, he brought Synology and it just works, he's never had to mess with it. To quote him: "if Apple made a NAS"
[1] https://github.com/zelon88/HRCloud2
You have carefully omitted your budget. Your budget will likely ultimately determine your options.
Otherwise I'll tell you to get a 10Gb switch and build a five node CEPH cluster. :-)
OP was looking to spend less time, not more :P
The setup per node is super simple, Ubuntu 20.04, install Docker, and then one command to add the new node to the cluster, and one more command to add a disk.
(Ceph version 16 switched to cephadm for deploying and managing a cluster and it's a lot easier now than with previous versions.)
With just 4 nodes I'm already saturating a 1Gb connection on my client (Ryzen desktop).
Perhaps the most surprising thing for me was how stable and forgiving a native CephFS client is on my Linux laptop. After waking up from sleep, it takes about a second to reconnect.
This weekend I'm planning on expanding to 7 nodes. With 7 nodes total power usage should be ~31 watts (not counting network switch), which is less than my current 6 disk ZFS RAIDZ2 setup in my desktop.
The NAS gurus always say "RAID is not a backup", and it is true you should have additional backups. But no backup solution is perfect, none get updated every day, especially if you plan on keeping the backup off-site. For most users, the NAS is the backup. All I'm saying is that when a disk fails on your NAS, you'll be in panic mode and will want the easiest, most direct path to data recovery, and there is no RAID option in this scenario preferable than RAID-1.
But I think there's a semi-common exception: people who are using ZFS where they are maxing out the drives their enclosure can hold (or have a plan for that expansion). In that case, sure, fine, use raidz1 or raidz2 (with a hot or cold spare), because the rebuild commands are the same.
If the RAID is in software I can slap those disks into anything (like my desktop) and keep going.
If the RAID is NAS specific or on hardware, well, now you need something specific.
Of course you should have backups too, but why add something that will make your life more complicated in an already stressful time?
It's all still just lvm partitions and mdadm.
> Do you DSM to rebuild?
Depends what you mean. If a disk fails, I hot-swap a replacement in and press the volume rebuild button in the GUI.
[0] https://kb.synology.com/en-my/DSM/tutorial/What_is_Synology_...
> Do you need DSM to rebuild?
I don't think so. I've never had to do it without DSM, but since it is just mdadm and lvm you should be able to connect all the remaining disks to and Linux box and run the appropriate mdadm commands to fix the array.
Yes, I already figured out based on your previous response (and modified the question for others).
With that in mind, the NAS is not the backup. Once a file is deleted, it's gone.
With regard to recovering from a RAID-5 dual disk failure, typically a USB 2x sata toaster is enough to connect the failed disk and the replacement disk to a system that can run a ddrescue to clone the failed disk. Often times disks that are ejected from a RAID array still have enough life left to copy data off very slowly (over several tries/passes)
For backup, a simple solution is connecting very large external USB3 disk(s) and running daily rsync hardlink backups. There are several scripts to do this, and it's quite low effort to maintain after its set up.
Snapshots can be used to catch that failure mode, so I don't think this is universally true. Whether there actually are NASes that would have snapshottable file systems out of the box... Is there?
https://www.truenas.com/truenas-mini/
1. Think about the contents of your bare disks, in terms of what is required to read them. Lots of RAID-1 will stick headers at the start of the disk (including Linux software raid by default, iirc). Using ZFS mirroring will necessitate the use of ZFS to read it, and so on. I prefer using only Free software raid for this reason, while opting to make myself reliant on Linux/ZFS.
2. Mirroring is much simpler for the sake of rebuilds/performance, and if you're looking for a simple hassle-free setup that's the way to go. I've got a 4+3 raidz3 for my main array, not even for capacity's sake but rather for redundancy's sake (it was going to be a 3+3 until I realized how ZFS deals out chunks). But I realize that's going to be a hassle if I do start getting correlated disk failures (I've also got true backups).
If you are using only 2 disks, the only reasonable options are 0 or 1. So, you are saying that 0 is too unreliable, what I think nobody will disagree.
But when you have enough disks, RAID 6 is a no-brainier.
I have 3 + 2 disks Truenas setup, so when a disk fails, i’m still another failure away from single copy of data state. No panic, just relaxed shopping for replacement drive.
ZFS or MDADM don’t have the same limitation, but there are other caveats there.
The new model is also half the size, still with 4 full size drives.
Additionally, I have a DLink DNS-320 NAS, which is pretty old but does the job.
I would make your first / boot drive a SSD, and put WD Reds in the rest, 2 drive redundancy if you want to be super safe.
In addition, I recommend using the built-in cloud backup software to backup high-value data to Blackblaze B2.
Happy to answer any other questions.
The TLDR is they switched the WD Red drives from CMR to SMR technology without announcing it or noting it on drive specifications, and then when they got caught they announced the WD Red Plus line which became their cheapest CMR drives with NAS -focused firmware.
So before this, WD Red was just fine, but for new purchases, we have to specify WD Red Plus, not just WD Red.
https://www.extremetech.com/computing/311182-red-alert-wd-su...
[0] https://www.backblaze.com/b2/hard-drive-test-data.html
Given the history of the WD Red series they should be avoided by anyone who cares about data integrity in a NAS.
After the SMR scandal, WD did a rebrand and now any drive with any form of promise for NAS use are called WD Red Plus.
I'd go with Toshiba or Seagate Ironwolf.
A solid product with zero regrets (thus far).
At this point i have installed it and i stopped looking around for other solutions. It works for Windows, it works for Mac, i did not try Linux, but i don't really backup my Linux data, its all in Github anyway.
Is your data safe? Definitely as safe as 2 NAS-type drives can be. Did not experience data loss, but don't trust a comment on the internet, look for some research and statistics if you can find.
This is a different NAS model, in that each hard drive has its own micro server attached. Which I like, because it means that I won't be constrained by a NAS chassis, and it mitigates a lot of single points of failure. Plus it will scale in both performance and capacity as I add drives.
The HC2 costs about 50 bucks each, so it's the cost of a drive, +$50 and some maintenance overhead to keep the small cluster running. Starting off with 2 or 4 drives it's cheaper than most comparable synology or similar traditional NAS and for my use case is far more robust and flexible.
If you want more of a "set it and forget it" simple approach, the big players you listed (Synology and others) can work amazingly well.
I wanted to have a backup of my Dropbox on my NAS, so I used Synology's CloudSync service to back up to an encrypted folder. Unfortunately Synology's encryption actually encrypts each file individually, which Dropbox happily syncs to all of the computers that use that Dropbox, making all of those files unusable!
In the end, I had to write a script that detected which files were encrypted (files start with `__CLOUDSYNC_ENC__`), then use a WINDOWS ONLY decryption utility provided by Synology to decrypt and finally get back to a clean state. Then I wrote another script to move the decrypted files back into the proper path in Dropbox while correcting the newly decrypted files with the original metadata (creation date) from the encrypted bad files. What a pain!!
I'm still not sure of a good way to achieve my original goal of backing up Dropbox while still protecting my data with encryption. Let me know if anyone has a solution!
To back up data from Dropbox, I'd create an encrypted Shared Folder on the NAS, turn off CloudSync encryption, and sync into the folder with the sync direction set to pull-only. That gives you a mirror with local file system-level encryption (using ecryptfs; buyer beware) and keeps Dropbox as your source of truth.
There may be a different way to do it with DSM 7, but I've only tried this on 6.
If you want something simple and standalone that just works, buy a MacMini and a DAS.
If you need a cold storage backup server that you only boot once a month, build that.
If you want something that you can assign to a Windows domain and scale, maybe some Intel NUCs would work.
A netbooted, POE-enabled Raspberry Pi 4 or two can do quite a lot, depending on your needs.
I've use several proprietary consumer NAS products over the years, and mostly I've found they make great gifts to friends after a year or two.
All possible to roll your own, of course, but time is money.
As for trust, you can trust anybody for anything. Should you is a different question. I rest easy knowing there will never be an article about a product I critically rely on deciding to sell me out. And needing to navigate least-worst commercial options seems like a much larger maintenance burden.
- Whatever crazy tunneling and so forth that they do so that I can access the admin interface over the internet regardless of how brain-dead my home ISP router is. Synology is very good at this.
- Mobile apps that make it fairly easy to do stuff like "sync any photos after I take them to the NAS, but only when the phone is on WiFi, and optionally delete it from the phone after the sync is confirmed.".
Also worth looking at with Synology is their support for really cheap offsite backup, like Backblaze B2. I was able to set something up to protect against say, a house fire, and be selective about what I was sending, and it's something like $1/month for that peace of mind.
[1] For example, it's fairly easy to mostly brick them and the recovery process is having to send hand-crafted/altered ICMP packets to it during boot and hope that coaxes it into a BOOTP mode. They are also quite underpowered and just go unresponsive for minutes at a time. The WD products are awful all around.
I've thrown tens of thousands of photos at it, and my only complaint there is the background processing to generate thumbnails is very slow, especially with "Live Photos" from iPhones (which are essentially photos with short videos attached). If I upload a couple thousand of those, the NAS might not finish generating the thumbnails for over day, so if you browse using the apps Synology provides for photos, you just see lots of placeholders for a while.
I did have a (SeaGate IronWolf) disk fail on me already, and the NAS did it's thing correctly - it made audible beeping alerts (which were definitely attention getting as the NAS had never played a sound prior to that). When I swapped in a new disk I was easily able to instruct the NAS to add it to the RAID array and recover, and everything was back to healthy pretty quickly.
If I were to shop for a replacement I'd be tempted to look for something with a beefier CPU as the thumbnail generation thing is occasionally annoying. But honestly the CPU is mostly idle most of the time, so if I did get a more powerful NAS the CPU would probably be idle 99.9% of the time instead of 99% of the time.
Ideally you want to follow 3-2-1 (3 total copies, 2 local, 1 offsite) for backup, so I'd recommend the following setup:
A small FreeNAS box. Like, 3 hot data drives at most, small. If you really want to save on power and are willing to take a hit on performance, you can use something as small as a raspberry pi. (again, if you don't want freenas, then swap this for anything with 2 drives that can RAID 1 and can automatically sync with backblaze or similar).
On the local PCs pick a specific folder to back-up instead of everything, since you'll only have a small backup.
Personally, I would stay away from anything that isn't ZFS backed, but i've heard good things about synology. I wouldn't trust any solution from an HDD mfg, because i don't think their code is that good for that sort of thing (eg https://www.theverge.com/2021/7/2/22561140/wd-cloud-os-3-sec...)
1. Intel NUC + Internal 2TB NVME SSD (24/7)
2. Dell T20 + 32GB ECC RAM with encrypted ZFS 10TB RAID 1 (wake on lan / on demand) 3. Alix APU 4GB with ZFS (24/7, off site at my fathers home) Its pretty low power, but also low on storage - it took a while to find out that the data for my all day use is < 2TB. This is often not enough for most people...I can recommend to use an cheap old machine as NAS with ECC RAM (a must) and ZFS, like a
OS can be FreeNAS/TrueNAS, napp-it or another reliable one. I never had problems with these and once configured, there is hardly any effort to maintain them.What I don't recommend is:
Soho NAS like Synology are ok-ish, but I don't like them - Bad things happend to me. Broken filesystems, damaged files, non-working backups, slow performance and so on. But that was a while ago, maybe now they are better :-)(I share your reservations wrt. Synology; it's working for my parents so far but I like the extra degree of control)
There's also the issue of some of your NAS devices getting hacked. Happened to me.
Without knowing anything else, for a small and power-efficient setup I can recommend the Odroid HC4 with Armbian (manually upgraded to Bullseye; Bullseye builds are currently broken but building Buster and then upgrading works fine) and a ZFS mirror of whatever SATA drives you choose. I use one as a backup sink.
https://www.hardkernel.com/shop/odroid-hc4/
As for drives, I've been committing myself for Toshiba recently. They have a good reputation for reliability/durability and reasonable cost-performance.
If you're going for SSDs, that market segment is in a bit of constant flux.
For something beefier and way more extendable I've been writing about my experiences with ASROCK RACK's X570 boards here: https://news.ycombinator.com/item?id=28302303
Though, from what I understand you may get lower idle power consumption from the right Intel CPU/chipset combo than AMD Ryzens as of now. This is just something I gathered from others' remarks and not something I researched or benchmarked properly myself so take that with a grain of salt.
I never used a prebuilt QNAP/Synology but I'm curious what it is that takes time for you these days that you hope to cut down on? A DIY can be pretty much as fire-and-forget once you have it set up and on the flip side you still have plenty of room for tinkering with containers and whatnot on Synology et al... Like, is there ongoing maintenance you have to do on your FreeNAS box just to keep things in place or is it more a personal tendency to keep changing things that makes it never ending?
The main reservation I had for going DIY is that there's a lot of initial building involved (getting hardware that works well together etc.) whereas Synology et al. is more like 'plug and play.' However, I revised that opinion whilst reading that thread, primarily because I learned about NUCs and other such alternatives. I know myself very well, though, and I know that if there's a fully-fledged OS, I am bound to change stuff, try out new things, etc., when in reality all I should be doing is making backups :D