leman

I'm about to switch to unraid on F4-424 Pro in a pretty similar way and I like the suggested setup a lot, so plan use all the advice above and set up the array / pool exactly as described above. 2 questions though: 1. I'll be moving from 2-bay Synology NAS with 2*4tb HDDs in it and ca. 2.5tb of files. I have extra 2*4tb HDD and 2*1tb SSD for F4-424 Pro, so my plan is to start unraid on F4-424 Pro with just 2 HDDs / 2 SSDs (setting up the array + pool as described above), move the files and then wipe and move 2 remaining HDDs and rebuild the array. Any issues with this plan? If no, should I designate 1 HDD as data and 1 HDD as parity before moving the files or it would be essentially the same to just have 1 HDD as data and only add parity after I have moved the files and put all HDDs in F4-424 Pro? I realize the second option gives no protection during the transfer process whatsoever, but it will be faster I guess (as F4-424 pro won't have to write the parity disk during files transfer) and then both options have an "unprotected" phase when the parity is rebuilt after adding the remaining 2 disks... 2. In the setup above NVMe pool acts as "system" shares storage plus a kind of cache for "media" share (as it will have all files written to NVMe and then moved to HDD array by Mover) - all that without designating it as "cache" for "media" share, right? To use this quasi-cache setup for other shares I'll just have to create those shares replicating Primary / Secondary storage configuration described above? I understand this Primary / Secondary storage approach is different from another option which is to create a share on HDD Array and then designate NVMe pool as "cache" - what are the benefits of Primary / Secondary storage + Mover setup? Sorry if I misunderstood something in above, I'm yet to tinker with unraid to see how things are done there.