Completed DIY Networked Attached Storage
- Thread starter sswilson
- Start date
So what is your final decision on the NAS OS you will be using?
I have been using unRAID for years and it gets the job done for me.
You can use all 10TBs and 8TB drives with a single 10TB parity (largets drive in the array) for single parity.
22TB might not be used in this setup, but you can set it up as an external backup though.
You can also use TrueNAS Scale and have 4 x 10TB in a RAIDZ1 setup and 2x8TB in a mirror. Again, 22TB might be a waste to include in the array, use it as an external drive.
I have been using unRAID for years and it gets the job done for me.
You can use all 10TBs and 8TB drives with a single 10TB parity (largets drive in the array) for single parity.
22TB might not be used in this setup, but you can set it up as an external backup though.
You can also use TrueNAS Scale and have 4 x 10TB in a RAIDZ1 setup and 2x8TB in a mirror. Again, 22TB might be a waste to include in the array, use it as an external drive.
Still planning on unraid. Looks to me like it'd be a lot easier to navigate than TrueNAS would be especially when it comes to docker "apps". The only thing I'm not completely sure on ATM would be if unraid will incorporate my 1TB NVMe as read/write cache for the array... most cache drive topics seem to focus on using the NVMe for the docker apps/data. I'm going to be taking my time to put this whole thing together, I won't be surprised if it takes me a few weeks just to get the basics set up in a way that I've got a basic understanding of what's going on (and why).
As far as the drives go..... I'll probably go with all of the drives I got off of you and keep the new 22TB as my spare. If one of the drives starts to fail I'll bring the 22TB in as parity and move the 10TB parity drive over to the array.
As far as the drives go..... I'll probably go with all of the drives I got off of you and keep the new 22TB as my spare. If one of the drives starts to fail I'll bring the 22TB in as parity and move the 10TB parity drive over to the array.
with enuff HDD of varing sizes and an HBA or two, anyone can make a NAS!
Currently topping out sub- 80c, but had been hitting 100c (and presumably throttling). Checked the board and found that the fan wasn't kicking in.... swapped the bios setting to manual and then back to automatic but increased the "PWM Start" to 100 from 80 and it seems to be working properly now (max rpm is supposed to be 100c so I'm guessing this is a 5-6K fan?).
Going to have a look at the tim, and do a quick measurement on the mounting holes to see if they'd line up with any kind of third party cooler.
About the NVMe cache. Everywhere I look always says not to use a single drive for write cache. Only a mirrored drive for write cache as it can otherwise corrupt things durring a failure. And if it is a single drive to only ever use it as read cache.
That makes sense. We'll see when I get to that point. 
I know the focus for cache drives seems to be having your docker instances on there along with their associated data for quicker access.
I'm not even sure if the speed benefits of a cache apply in this use case.... you're not going to speed up write times, and read times are probably not that critical outside of initial seek.
I know the focus for cache drives seems to be having your docker instances on there along with their associated data for quicker access.
I'm not even sure if the speed benefits of a cache apply in this use case.... you're not going to speed up write times, and read times are probably not that critical outside of initial seek.
correct! that's why branded NAS have two M.2 slots, to run in mirrors.
Well.... I do have 2 NVMe slots.....
Maybe I need to swap out the two 512 drives in my gym PC for the single 1TB........
Maybe I need to swap out the two 512 drives in my gym PC for the single 1TB........
Had to go into the adapter to change from 2.5G to 5G on my main PC but I'm now getting my 5G (ish) transfers between the two pcs.
xentr_legal_notice_title
xentr_legal_notice_description