Server Version#:Working on new build
Player Version#:
Im rebuilding my Plex environment (been up and running for a long time, just a fresh start). I got a Nas and was wondering where my m.2 drive would give me the most benefit. should I, set it up as a cache drive or primary drive and install plex on it.
I feel like installing plex for responsiveness to libraries would be best, but wanted some opinions. Or point me to an article I might have missed. thank you
App Center → Plex Media Server → Migrate to → (new datavol)
QTS will move PMS to that M.2
At this point, to save undue wear and tear on the SSD, a scratch HDD directory somewhere for the transcoder temp (you don’t need SSD speed for that) is usually best practice
@ChuckPa, can I ask another question about this setup?
What is best practice for Raid configuration with Plex?
I’m not overly concerned with losing data, just want to try and keep it. losing files takes a while to replace in the long run.
I have RAID 6 (allows for 2 drives to fail). RAID 5 tolerates 1 drive failure
The speed of reading the data is trivial compared with protecting it (retention).
I have both RAID 6 (for what’s live) and then the (proper) full mirror backup
on HDDs which are turned off until it’s time for the monthly backups again.
(RAID is good online protection but it’s no backup)
Just have good back ups, Raid is not for back ups, it is for uptime. Most people could do without raid, better to spend the money on backup hard drives.
If anything maybe mirror 2 drives for the actual server folder then unraided drives for the movie data, back up those drives.
Unless you are like @ChuckPa with large data pools usually a back up will restore you quicker than rebuilding a raid drive.
It is also safer as you do not have the risk of the raid failing on a restore. (though I guess ZFS has less issues like that, just never used ZFS so no idea.)
@skwor01, thanks Skwor01, Im familiar with Filebot (been using it for a while) and understand the importance of naming convention. Ill defiantly read the article, thanks for the help
I’ve seen too many Syno users lose their entire volume.
BTRFS is a type of RAID & Volume management which can live on a single drive.
If you are partitioning your data volumes 1 driver per volume then BTRFS is far better than nothing.
If you’re creating a real RAID volume of multiple drives then Why RAID on top of RAID ?
Redhat pulled out of BTRFS a few years ago.
BTRFS for SSDs is a No No
Is btrfs bad for SSD?
The btrfs documentation, after a discussion of COW (copy on write), contains a number of warnings on SSDs: Writing “too much” distinct data (e.g. encrypted) may render the internal deduplication ineffective and lead to a lot of rewrites and increased wear of the memory cells.Jun 5, 2023