Radxa's SATA HAT makes compact Pi 5 NAS
jeffgeerling.com
jeffgeerling.com
https://www.aliexpress.us/item/3256806198066931.html
The N100 processor offers 2-3x the performance and lots of additional PCIe lanes compared to a Raspberry Pi 5 despite having half the TDP (6W vs 12W).
The overall build footprint will also be larger, and you'll have to pick up a set of SATA cables ($10 or so for four) and possibly a case or bracket to support the drives ($10-20).
It does have 16 GB of RAM (Pi tops out at 8GB for $147), the CPU is faster, and it has 4x 2.5 GbE which is a huge upgrade!
But I wouldn't quite put a mini ITX motherboard in the same price class, even though it's a better all-round board for a 'homelab in one box' type of setup.
Couldn't see one in quick searching though. :(
When I bought my drives a couple years ago they were around $400. I wish there were more options for 4-8 TB SSDs that went for capacity over performance. Honestly I would be happy with some larger lower-cost SSDs that ran at 100-200 MB/sec just for silent, low power capacity.
The only non-junk PCIe3 option that's even advertised here recently is the overpriced WD Red SN700.
Other than that it's just lemons and more power-hungry PCIe 4-5.
I still have better operational cost-performance from 5 year old drives compared to anything on the market today.
Those WD drives seem to have some real issues, at least with ZFS and btrfs. :(
Space. You trade off the physical space to get more storage space.
Random IO bandwidth. Until 6+ HDDs (w/o counting parity/mirrors) there is no point even speaking about random IO bandwidth.
> longer lifetime (writes)
To each their own. You need a lot of writes to deplete TBW of a modern drive, even MLC/QLC ones.
> kind of cargo culting
I would say what it's not the right term here. But hey, calling everyone who uses SSD in NAS because reasons is totally the right way. Rite?
Noise.
Feeling. Solid state devices always felt more durable to me. I know I won't use too many writes on the NAS, but mostly read.
And then there's "rare" access time: If you don't want to spend power on spinning disks, you need to wait some time for them to spin up if you want to access your NAS.
The physical space required is not significantly different. They're both small form factor things even if HDDs are 2 to 3 times the volume it's 2 to 3 times an insignificant amount. Plus you need only about 1/5 the HDD to match SSD storage.
Random IO bandwidth doesn't matter at all when you're putting it at the end of an ethernet connection to an rpi. You could certainly benefit from it if you put them in your actual computer though.
By cargo culting I meant the entire concept of NAS in the first place for home use. Just put the drives in your desktop PC and it'll be much much faster, much cheaper, and significantly less likely to break. The power cost of leaving your desktop on for the lifetime of such a thing will be less than the extra cost of NAS parts.
O RLY?
Toshiba X300
4TB 16TB 10TB 8TB
Operating W 6.81 6.91 9.48 8.41
Idle W 4 4.03 7.22 5.61
Samsung 870 QVO 8TB
Operating W 2.4/3.3 (R/W)
Idle W 0.045
> But you're talking transient spin-up power of course which is significant and might require an external power supply which costs moneyYou need an external PSU for 3.5" HDDs because they require 12V and 5V. 870 QVO only require 5V.
> The physical space required is not significantly different
Come on:
3.5" HDD: 26 x 147 x 100 = 382200 mm3 (Toshiba X300)
2.5" SSD: 7 x 70 x 100 = 49000 mm3 (Kingston A400)
382200 / 49000 = 7.8
870 QVO is listed as "100 X 69.85 X 6.8 (mm)" so essentially the same> Random IO bandwidth doesn't matter at all when you're putting it at the end of an ethernet connection to an rpi.
Ah, yes, because everyone is only doing sequential IO to NAS, like you?
Sorry, but you arguing here in a bad faith and without even a bits of a basic knowledge.
In comparison 3 8TB SAMSUNG 870 QVO cost $1500 total, or, ~$1000 more than the 3x $150 X300 8TB. So it will take 50 years for the $20/yr energy cost of the HDD over SSD to matter.
>Ah, yes, because everyone is only doing sequential IO to NAS, like you?
This is a mischaracterization (or misunderstanding) of my statement. I said it doesn't matter because behind a rpi ethernet link it literally doesn't. The latency of the link and rpi compuational power dominates. You could have an optane behind the rpi ethernet link and it'll be about the same as something fairly slow. SSD in rpi 1 gig ethernet NAS are like using sports cars to haul gravel with trailers. If it was connected via infiniband it might make sense.
I don't think you're making your arguments in bad faith but I do think you're a bit confused about what 4 watts is. And the physical volume thing is the same: very small things with large relative differences make for small absolute differences.
This is overstated. You need a lot more than "a couple" of drives to trouble even the most modest ATX power supply. Now if you were trying to run this off the RPi's power I would agree. But since this requires a separate PSU anyway it's a non-issue.
As always, there are trade-offs between all choices and not everything is a no-brainer :)
Putting mapped drives on even garbage QLC drives is a good QoL improvement, remaining unmapped shares can stay on HDD
Far lower latency, and 2.5GbE isn't that bad if you're not already used to something faster.
SSD storage is even an improvement over 1GbE when you're working with lots of small files, or really any scenario that's substantially random access.
https://blog.kobol.io/2021/08/25/we-are-pulling-the-plug/
https://wiki.kobol.io/helios64/intro/
An RK3588 version of that with some more PCIe connectivity (another m2 slot or two?) would have been pretty much ideal.
For a NAS newbie, how would it compare to a DS224?
The hardware is fairly similar in terms of what you'll get for performance and efficiency, though you get hot swap bays on the Synology, which is nice. Plus a case... Radxa hasn't told me when they're releasing the case, just that they're working on producing it.