
Granted, this is an upgrade that probably won’t happen for a couple of years, but as my current environment chugs away at adding the first of two new parity drives to upgrade from 14 TB to 20 TB, it’s starting to become clear that this NAS that has been supporting our home streaming and hoarding efforts for the last six years is nearing the end of the line for a couple of reasons…
First and foremost, I just recently replaced the entire motherboard after this giant headache from three months ago that never truly got resolved. The old one had both a CMOS issue where even a new battery wouldn’t retain the BIOS settings and the BMC refused to respond, which is needed for any firmware updates, so I finally spent about a hundred bucks on eBay for a used one and after about an hour to swap everything over, my excess fan noise went away and the whole thing was stable again … for now!
Now second of all … this array is starting to get pretty big.
Ten years ago, having just started playing with Plex the previous fall, I had 20 TB of disks in use total. This year for early Black Friday sales, I picked three new drives up from Best Buy that each have 20 TB of space available!
Plus, looking at my storage array as it stands today, I’ve got a total of 210 TB spread across 18 data disks and 2 parity disks, and all but about 8 TB is in use. So this upgrade, after juggling around my parity disks, will put me at right about 260 TB of data disks, and with my existing chassis (a Dell C2100 and MD1000 disk shelf) limited to 27 disks in total, I’ll have room for about six more until I’m completely maxed out from a hardware standpoint and nearly maxed out from an OS standpoint (Unraid’s limit is 28 data + 2 parity)…
…which if we’re being honest, is my bigger concern because I know that as my array continues to grow and disks get bigger, parity restores continue to take longer and longer, which adds the risk of having additional failures while waiting for the first restore to finish.
In the grand scheme of things, I’d love to see this evolve into a 500 TB or even 1 PB like something out of Linus Tech Tips and I think given enough time, it’s probably possible, however at the same time I also have to think about longevity and the things I can do to protect all of the work that has gone into building an archive this big and making it useful to friends and family to boot!
It makes me wonder if I’m going to eventually have to switch from Unraid over to TrueNAS, which is more capable of housing HUGE amounts of data whereas while Unraid still supports a quarter of a petabyte as I’ll soon be hosting in the near future, they’ve always said that their target audience isn’t for enterprises needing extremely large storage options. Even among power users, I’d still consider having a petabyte of storage at home to be an extreme option…
So here’s the comparison as I see it today, admittedly not knowing a ton about TrueNAS:
| Unraid | TrueNAS | |
| Disk Quantity Limit | 28 data + 2 parity disks | only limited by other hardware (e.g. processing power, backplane, HBA, etc…) |
| Redundancy Options | 1 or 2 parity disks for entire array | need to learn more here, but I believe ZFS allows for multiples with vdevs and pools Example: vdev1 – ten 20 TB disks, 2 parity drives vdev2 – eight 14 TB disks, 2 parity drives vdev3 – 6 10 TB disks, 2 parity drives pool containing all three vdevs – 372 TB, 6 parity drives |
| Disk Size Limit | mix and match – no limit | vdev must contain disks of the same size, can create additional vdevs for other sizes |
| How Data is Stored | individual files are stored on a single disk Result – losing a disk only loses files stored on that disk, not whole array; only disk containing files actively streaming need to be spinning | files are striped across all disks in vdev Result – much faster read/write speeds, but losing a disk loses the whole vdev; all disks in vdev need to be spinning to stream files from that vdev |
I still have a lot of research to do, namely if I can make TrueNAS mimic how Unraid stores data which I think is pretty handy, despite how neat it would be to see those faster speeds. Additionally, I can’t help but wonder if limiting how much my disks are normally spinning has helped to prolong their lifespans, as my oldest disks are currently 7 years old whereas 3 – 5 years seems to be the typical average. In reality, most of the time only a few drives out of the twenty in my array are spun up and in the future, I think I can do some further tweaking with the cache drives to hold newer files longer so that they won’t even get pushed over to the array until users have had several weeks to watch them.
I’m still hoping that we get to build a new house at some point and ideally this upgrade would take place around the same time so that it would be moving into a newer and more accommodating server rack in a dedicated room that isn’t my bedroom closet and boasts better air conditioning and noise dampening to boot! It can be hard to judge how often new drives are actually needed because I often forget to write down my totals each year, so we’ll see if this newest 50 TB lasts for more than 2026 or if I find myself adding more again around this same time next year!













