Dave11342

So I moved Emby to the appdata folder on the cache pool. The cache pool is the 2 1tb ssd's and the entire pool is assigned to the cache. The pool is set to btrfs raid 1. The cache pool is used for all shares first, then move to the array except for the appdata, domains, and system shares . I do have appdata backed up using the backup plugin to an backup share directly to the array. I then converted the unassigned drives, the 256mb nvme and 256mb ssd, to a new pool using raid 0. I'm using this for the download share only. I did make the array secondary only if more space becomes needed for large downloads.

I misspoke earlier. My appdata, domains, and system shares are all already on the cache pool, not the array. I also use the cache pool for downloads as well as iso's and any media I add directly to a share before they get moved to the array. Would it be beneficial to create a second pool just for the appdata, domains and system? Leaving the cache for the downloads and direct file share transfers.

@trurl I will definitely have to look into pools. I do have a cache pool with 2 1tb ssd drives since the beginning. Even though I've had this system running for many years, I still have a lot to learn. Especially when it comes to optimizing the system. I appreciate the help and insight. I have to look, but I may have some spare ssd's I can add to the system. I can make a pool from them for the docker containers, move emby over to it and then add the nvme to the pool.

I assume using this plugin to stop the parity build would reduce the chance of errors? Or just to make Emby and access to the array quicker?

The nvme is only 256gb. Just didn't see a reason to add something that small to the array. I'm running v7.3.3

Oh, now that much simpler. Thanks. How about running the Emby docker? I assume running docker containers would slow the parity building process, but I would shut down all the containers that write to the array.

I've been researching how to upgrade my current server from single parity to larger dual parity. I just want to make sure I do this the safest and best way. Currently I have 4 8tb drives with one parity. Plan is to add 2 new 10tb for parity, reuse old parity for data and also add 2 new 8tb for data. So I'll end up with 2 10tb parity drives and 6 8tb for the data array. Good ole Gemini is suggesting I install the drives then run New config then choose Retain Current Configuration and select All to keep the current 3 data drives intact. Next I do the drive assignments on the main screen. Should I wait to reassign the old 8tb parity drive till the new parity is finished? Also, I know it's probably best to leave the docker containers disabled, but I do rum Emby on this server and waiting a day or longer kills nighttime tv (lol). Would it be ok to enable docker but disable all other containers (the *arrs) and leave Emby running? At least long enough to tv time. The Emby docker is actually stored on an unassigned nvme device, not the drive array. Not that it matters to the main question, I'm also taking this opportunity to add more ram and a video card for transcoding in Emby. This server has been running for several years now like a champ. Surprised it took me this long to do the upgrades, but when it works, it works.