December 28, 20205 yr I'm a recovering Synology user setting up a new Unraid box with a circus of disks pulled from a flaky Synology DS. I have 2 x 500G M2 disks on the board, and the following spinning SATA disks: 1 x 2TB 1 x 4TB 1 x 5TB 2 x 6TB 1 x 8TB Does anyone have any config suggestions for these disks for best performance for simple NFS/CIFS file usage? Your opinions are appreciated. Thanks!
December 28, 20205 yr 15 hours ago, Gordon Shumway said: I'm a recovering Synology user setting up a new Unraid box with a circus of disks pulled from a flaky Synology DS. I have 2 x 500G M2 disks on the board, and the following spinning SATA disks: 1 x 2TB 1 x 4TB 1 x 5TB 2 x 6TB 1 x 8TB Does anyone have any config suggestions for these disks for best performance for simple NFS/CIFS file usage? Your opinions are appreciated. Thanks! Since your parity drive(s) must be as large or larger than any data disk, the 8TB drive should be your parity drive. This will allow you to add or replace data drives in your array up to 8TB. The 2TB-6TB drives would be the array data drives and give you a total of 23TB storage protected by the 8TB parity drive. Note that for future expansion considerations, most people start considering going to a dual-parity configuration at around 8 or so data drives, although, there is no hard and fast rule for that. It's all personal preference based on the level of "insurance" that makes you comfortable. The 500GB M.2 disks would be best utilized as cache disks in a cache pool with either both disks being in the same pool (redundant or increased capacity) or each disk being in a separate pool for different uses. Note that multiple cache pools requires the use of version 6.9 of unRAID which is currently in the release candidate phases. Cache disks have multiple uses such as caching writes to the array, storing docker applications, download or rendering temporary locations, home for VMs, etc. As an alternative to a cache drive, you could use one as an unassigned device for many of the same uses listed above (except user share write caching). I personally have one 500GB NVMe SSD as a cache drive for storing the appdata (docker containers) share and caching writes to one share and another 1TB SSD as an unassigned device for file downloads, temporary transcodes and VMs. Edited December 28, 20205 yr by Hoopster
Archived
This topic is now archived and is closed to further replies.