cross-posted from: https://lemmy.ml/post/36604428

Hello everybody,

I want to ask for some opinions on my current setup and how I pretend to use it for my Media Server:

Current Layout

I currently use an UGREEN DXP2800 NAS running TrueNAS Scale with two 4 TB HDDs in Mirror mode. This is planned to be my “long-term storage” for backups, photos, and so on.

Additionally, I have 1 TB SSD installed in the system. I created two datasets on it: one for Docker containers and the other one for Media, following the TRaSH guides folder layout

My current plan:

My idea is to use the SSD for the torrents and the seeds, and once the file (e.g. the ~~movie ~~ Linux ISO Image) is completed, to move it to the HDDs. From there, Jellyfin would read the corresponding dataset and play the media.

The question:

The TRaSH guides puts a lot of emphasis on hardlinks and atomic moves, and that forces you to operate in one single filesystem. Is it worth it to stick to the TRaSH guide or my current setup would work just fine? What do y’all think?

Thanks in advance and happy self-hosting!

  • CriticalMiss@lemmy.worldEnglish
    21·
    8 hours ago

    I think TRaSH serves as a good base. Their custom filters can be instantly imported using recyclarr and give you a general idea of how custom filters are meant to be used (which can be very overwhelming when you’re new to the ordeal) but sadly I disagree with TRaSH a lot on their group tiers for media formats. I think they make some mistakes placing some encoders as high as they do. (for example: micro encodes from PTer and BHDStudio shouldn’t be in the BluRay groups at all, as some of their releases are compressed harder than WEB releases from streaming services. I download BluRay encodes because I want it to be compressed to the point where it still looks identical to the BluRay it was sourced from.) Once you’re in the game long enough you just make up your own mind on what release groups should be prioritized over others.

    As for your question regarding staying within the same file system, the answer is yes. Moving things over to the SSD does two things for you. 1) for every file you also need a duplicate on the SSD, not very efficient. 2) there’s not much to gain from this unless you’re expecting a large amount of simultaneous traffic. An HDD can carry about ~20 streams of 1080p content (as most releases are compressed to 8-10mbps) which is more than enough for most households.

    I’d keep the SSD for seeding honestly, so that you can build up buffer on the trackers you’re on, but for most it’s still perfectly doable with HDDs only.