eRacks Systems Tech Blog
Open Source Experts Since 1999
The Apps Were Never the Box: Why We Build Open NAS Systems
An XDA Developers writer published a piece last week that we could have written ourselves. He kept his Synology NAS (network-attached storage: a box of drives on your network that serves files and apps) and walked away from almost every app Synology ships with it. His photos moved to Immich, his music to Navidrome, his movies to Plex and Jellyfin, his documents to Paperless. All of them run in Docker, a way to package an app with everything it needs so it runs the same on any Linux machine.
His reasons are specific. Synology Photos, in his words, is “pretty dated”: no major new features in a while, and missing the GPS tagging, import workflows and shared libraries Immich has, with a mobile backup he found less reliable. Synology’s music app is “not very good at all”. And Synology discontinued its own video streaming app, which leaves a basic DLNA server as the only first-party option.
We have been saying this for years. It is worth saying why.
A NAS is two things
Every NAS is storage plus the apps that use it. Appliance vendors sell the two as one product, and for a while that was a fair trade: the apps were the reason to buy the box. Docker ended that. The open-source apps now move faster than the vendors’ own, which is the writer’s first reason, and because they are containers, they do not care which hardware they run on.
The XDA writer makes the point himself. His apps are “as independent as possible”, so if he moves from Synology to another brand, or to his own server, Immich comes with him. A proprietary app cannot make that promise, and neither can a vendor that decides which of its own apps survive the next release.
Once the apps are open, the box is just storage. And storage should be open too.
What open storage looks like
This is how we build NAS systems, and have for a long time:
- ZFS by default. ZFS is an open-source file system that checksums every block, so it detects and repairs silent corruption instead of serving it back to you. Our NAS line defaults to RAIDZ2, dual parity: any two drives can fail without losing data.
- The drives talk to ZFS directly. We offer an HBA (host bus adapter, the card the drives plug into) in IT mode, which passes each drive straight through instead of hiding it behind a hardware RAID controller. ZFS sees the real disks and their health.
- Standard NAS drives. Our current default is the 24TB Seagate IronWolf Pro, a CMR drive (conventional magnetic recording, the kind that behaves well in a rebuild), bought in the channel like any other part. If a drive fails in year four, you buy another one anywhere.
- Your choice of operating system. Ubuntu LTS by default, or Debian, TrueNAS Community Edition, OpenMediaVault and others. The data outlives the choice: a ZFS pool exported from one machine imports on another running a current OpenZFS.
- Sizes that fit the job. From NAS4, a 1U four-bay unit, to NAS100, 102 bays in 4U, plus the QUIET3 for a home or an office where a rackmount fan would be too loud.
The same apps, without the vendor in the middle
Immich, Jellyfin, Plex, Navidrome and Paperless run on any of these systems exactly as they run on the XDA writer’s Synology. The difference is what sits underneath: an operating system you can update on your schedule, a file system you can move, and hardware with no vendor deciding which parts or apps you may use. Name the apps you want and we install and test them before the system ships, the same way we set up TrueNAS with Jellyfin on a quiet media server this month.
To be fair to Synology: if you want an appliance you never think about, and you are happy with its apps, it is a reasonable buy. The writer still uses his as the backbone of his setup. But if you are already running your own apps, as he is, part of what the appliance price pays for is software you have stopped using.
Where to start
The full NAS line is configurable online, and our July post covers how we re-verified every default drive and part against this year’s shortages. The XDA article is here.
Tell us what you store and which apps you run, and we will size it. Write to info@eracks.com, or start with a quote request.
joe September 24th, 2026
Tags: Docker, Immich, Jellyfin, NAS, Navidrome, Open Source, self-hosting, Synology, TrueNAS, ZFS
We Re-Verified Every NAS Default Against the 2026 Drive Shortage. Here’s What Changed.
The 2026 drive and memory shortage has quietly broken a lot of storage price lists. Drives that vendors still advertise as standard are backorder-only at every national retailer. Memory prices moved 50 percent in a quarter. A configurator that hasn’t been re-checked against real supply this year is, politely, fiction.
So we re-verified our entire NAS line: every default component, checked against multiple named suppliers, for both price and actual in-stock availability. Here is what changed, and what it means if you’re shopping for storage this summer.
The 30TB drive problem
Our large NAS models used to default to the 30TB Seagate IronWolf Pro. It’s a fine drive, and it has become effectively unobtainable: backorder-only at the one national supplier still listing it, dropped from Seagate’s own current lineup, unavailable everywhere else we checked. Continuing to default to it would mean quoting systems we could not ship this week.
The fix: our high-capacity systems now default to the 24TB IronWolf Pro, in stock at multiple national retailers at about $35 per terabyte, and we added the 32TB IronWolf Pro, also in stock, at the top of the ladder at nearly the same cost per terabyte. Every drive in our NAS configurators remains CMR (conventional magnetic recording); we do not use shingled SMR drives, whose write performance collapses during the sustained writes of a RAID rebuild, exactly when you can least afford it.
ZFS RAIDZ2, now the default everywhere
Every eRacks storage system, from the 1U four-bay NAS4 to the petabyte-class NAS100, now defaults to a ZFS RAIDZ2 pool: dual parity, meaning any two drives can fail without losing data. RAIDZ3 (triple parity) and striped mirrors (the performance-first layout) are right there in the dropdown, and traditional hardware RAID remains available for shops that require it, just never as a silent default.
Under every pool is an IT-mode HBA (a host bus adapter that passes drives directly to the operating system), because ZFS wants to see raw drives to do its end-to-end checksumming and self-healing. If you’re deciding between RAIDZ2, RAIDZ3, and mirrors, our free ZFS layout guide works through the math.
Prices that match what parts cost
Component costs moved, so prices moved: mid-size and large models are repriced to current reality (the NAS12 now starts at $8,995, the NAS72 at $25,995), and every price in the configurator reflects a component list we verified we can buy this week. The entry line held: the NAS4 still starts at $1,995 and the NAS6 at $2,995, now with 16GB of DDR5 standard and ECC memory available as an upgrade.
This is the same discipline we described on our refreshed Components We Use page: new parts only, authorized US distribution, multi-source price-and-availability checks before anything gets quoted, and a 72-hour burn-in before anything ships.
Browse the re-verified line at eracks.com/products/rackmount-nas-servers, or ask us to spec one for your workload, a human answers.
joe July 9th, 2026
Tags: CMR, drive shortage, IronWolf Pro, IT-mode HBA, NAS, RAIDZ2, supply chain, transparent pricing, TrueNAS, ZFS