Having gradually built up my media collection to near the capacity of my 16TB external HDD, I've reached the point where I'll probably need to build a RAID array to keep the collection in one place. Assuming the RAID array will be at least 32TB, I have a few questions:
From what I've read RAID arrays can help mitigate the risk of individual drives failing if extra space is allotted on the hard drives. Assuming a total capacity of 32TB, how much of that space would be reserved by the RAID array for data loss prevention?
Is there a certain type of hard drive I would have to use? Aside from my 16TB drive, I also have two 2 8TB drives that I'd ideally like to be able to re-use in the RAID array, but have left them in their enclosures for the time being.
If the hard drives in the array have different transfer speeds, does the array as a whole default to the slowest one?
Whether the hard drives I already have are compatible or not, what RAID enclosure and hard drives would you recommend?
The general datahoarder hive mind seems to be moving away from shucking and towards manufacturer refurbished drives, see https://serverpartdeals.com/ for example, especially in RAID where you can lose a drive with impunity and warranty is uncomplicated by shucking.
In RAID and similar strategies the redundancy comes from a parity drive, which protects against the loss of one (or more with some schemes) drive, so if you only have two drives of the same size it's just a mirror (50% of total pool) but you can have a drive die without data loss. With four drives you get to use three of the drives (75%), five you can use four (80%) etc. Classical RAID uses identical sized disks but there are other approaches that allow different sizes e.g. mergerfs + SnapRAID or Unraid, here you lose your largest disk to parity.
RAID is generally faster than the individual drives, e.g. mirroring is nearly twice as fast.
Perhaps go with another 2*8Tb which will get you 24Tb usable and use the 16Tb for offline, preferably offsite backup (remember RAID is not a backup, it protects you from disk failure, but not user error for example accidentally deleting things)
One thing I will also suggest is looking into https://home.tdarr.io/. It's software that will re-encode your media to h265, saving you a lot of space. I just set it up on my synology NAS because I am at 80% storage and don't feel like buying another drive yet.
I mostly watch Plex on my home network, however I use a Chromecast to watch Plex remote from my location with slow internet. Would this be an issue? Would it make the experience better?
I'm running two external tens and I just bought an 18. I'd love to save some space and I'll have to buy a drive for a long time.
I am not an expert but I think compatibility is the only significant downside. If your device supports it, you h265 will give you better quality at the same file size.
RAID for uptime, backups for data you care about. RAID(1+) will keep your data online when a disk fails, but backups are the real way to keep data around if shit hits the fan. For a personal media collection, you might be better served with a non resilient RAID0 (total failure if one drive fails) with a backup around to recover from when that happens. If you do e.g. a raid5 you lose 1 disk of capacity in exchange for 1 disk of resiliency, raid6 same but 2 disks. That gives you some safety but there are a lot of instances where those raids don't save you from losing all your data. If you buy 4x 18TB drives, you could have 36TB from the 1st two drives and then backup to the other two drives.
There's no specific type of drive to worry about unless you're doing RAIDs especially with ZFS. Search shingle RAID rebuild for the biggest thing to worry about there.
Almost always, yes. Slow drives throttle the rest.
I've never used them but people say good things about synology most of the time. Everything comes with a cost and it's hard to make any sensible recommendations without knowing your constraints; primarily your budget.
Want to echo what was said here. RAID is not a backup solution. RAID is for always on capability. Do not use RAID as a way to keep valuable data safe. Just have double the drive space and keep a backup of the data on the second drive.
You can also use SnapRaid along side MergerFS to provide some data redundancy. MergerFS will allow you to create a parity drive, without requiring all of your drives to be in your typical RAID pool. This way, if you have several drives die, then you can still access whatever data is available on the remaining drives.
No, but more RAID configurations than not are limited by the smallest size drive. It's a factor to consider, assuming you can't afford to just buy a bunch of disks. I wound up maintaining two separate NAS devices, one of which gets my old, smaller disks.
Generally yes, though you'd be surprised how little difference disk speed makes once you get enough of them in an array.
I use Synology with various shucked WD externals. I have a bunch of other stuff in my homelab though, so I need the storage to not be it's own project, else I likely would have built something less expensive. I'm sure there will be better suggestions in this thread than mine.
Start googling. Hardware or Software based? How techy are you? RAID should not be considered for backup. Think of it as an individual drive. Still needs a backup. Personally I use a ZFS pool in my Linux homelab that's been rock solid. However the pucker factor would be high if a drive fails.
Depends on how you set them up. There are calculators online that can estimate this for you.
I used NAS drives bc they're expected to be spinning a lot.
No. You will see better performance on average compared to your slowest drive.
I have no relevant experience with specific hardware. For a general base of knowledge figure out what RAID type you want to use. Look at what ZFS or btrfs can do in this space. Same for unraid.
Personally I use a ZFS pool in my Linux homelab that’s been rock solid. However the pucker factor would be high if a drive fails.
I use a ZFS pool for my home stuff too.
To minimize the pucker factor, I have an extra drive of the same capacity and I rotate through them in the mirror pool.
It makes good practice replacing and resilvering drives and since it's a mirror it's also kind of an offline backup.
Also, I had bought the initial drives at the same time and figured rotating though them would minimize the odds of failing around the same time.
I'm much less wary of the whole thing now that I've resilvered the drives several times.
Are you planning to use this only for media storage, or other tasks as well?
Many dedicated NAS boxes from the likes of Synology and QNAP come with low-powered CPUs that in addition to handling media storage can do many other useful things. For example - running various self-hosted apps like password managers, photo organizers, even office suites. Those do have many downsides as well. They use proprietary hardware and software, so you are at the mercy of the manufacturer if they suddenly decide that your NAS is too old for them to support. The CPUs in them are not as powerful as consumer-grade ones found in most desktops, and they don't usually come with a lot of RAM. They are also quite expensive for what they offer - for example, a very basic 4-bay enclosure with 2GB RAM and Realtek 4-core CPU costs $370, and that's without the cost of the disks. For that kind of money you can build a desktop from used server parts that will be ten times as powerful, and more versatile since it will be able to run any OS that you want. Granted, it will not be as small or power efficient.
If you just need a turn-key off-the-shelf solution, a prebuilt NAS may be the way to go. If you want to tinker with hardware and experiment with software however, self-built system with used parts may be better suited for you. Most homelabbers don't start off with a rack full of equipment, they grow their hardware organically. You have outgrown your external enclosure, so now you have several choices. For prebuilt NAS appliances Synology and QNAP are not the only choices; there are many other lesser known in this category - Asustor, Terramaster, Buffalo, to name a few. For building a server on your own I would recommend doing some research before going on a shopping spree - https://serverbuilds.net is an excellent resource.
That said, I'd echo others' answers. RAID is not backup. It offers some resiliency from disk failure, but that shouldn't replace a proper backup strategy. Synology offers various RAID levels, including their own take on it that allows for different sized drives. For self-built option there's UnRaid which handles resiliency differently, but requires an entire separate drive for parity.
In terms of hard drive choice, it all depends on how comfortable you are with possible data loss. If you back up your critical data (e.g. family photos, important documents) and don't care about downloaded media (you can always re-download it) then go ahead and use whatever - shucked, used, etc. If you absolutely cannot handle any data loss, then new drives made specifically for NAS appliances are the way to go. Enterprise level HDDs are an option also, but those mostly use SAS interface instead of SATA, and require specialized hardware (HBA adapters).
Gonna go with MalReynolds and mention buying refurbished drives over shucking. You are able to get a drive tailored for server use, rather than the crappy drives theyve been sticking in external enclosures lately. In a some cases, youre even getting a unused drive, even though its refurbished.
I use mergerfs to pool a bunch of varying sized drives and then run snapraid on the whole pool to protect it. Then, I've got Kopia backups running and backup up to a remote repository. This solution has been flexible and I've already been able to recover from 2 drive failures very quickly and easily.
There is btrfs - a linux filesystem. It keeps hashes for blocks to prevent data rot. And you can configure it into a raid that duplicates data across drives but doesn't require the exact same drives. You can just group any old drives together to create one large volume where everything is duplicated. At least that is how I understand this, I'm new to this too.