Self Hosted - Self-hosting your services.

16240 readers

29 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate. This is strongly encouraged!

Cross-posting

!everything_git@lemmy.ml is allowed!
!docker@lemmy.ml is allowed!
!portainer@lemmy.ml is allowed!
!fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
!selfhosted@lemmy.ml is allowed!

If you see a rule-breaker please DM the mods!

founded 4 years ago

MODERATORS

dogmuffins@lemmy.ml

testman@lemmy.ml

Zoe8338@lemmy.ml

[Help] Media Server + *arr stack: Follow TRaSH guides or my own setup? (lemmy.ml)

submitted 2 weeks ago by viszz_@lemmy.ml to c/selfhost@lemmy.ml

9 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] FreedomAdvocate@lemmy.net.au 1 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

What is your reasoning for using the SSD for torrents? Just put the torrents on the HDD(s). Having them on the SSD has no benefits whatsoever and is a waste of an ssd.

[–] viszz_@lemmy.ml 1 points 2 weeks ago (2 children)

I was considering using the SSD to avoid wear and tear in the HDD because of the nature of the torrent downloads. My idea was using the SSD as a temporary/cache drive for the download itself, and then only executing one transfer move to the HDD once the media is completed. Drive noise was another concern, since my NAS sits in my living room and I want to avoid hearing the drives spinning constantly.

I am using two Seagate Ironwolf HDD, which are NAS certified. Will they suffer if I use them for downloading as well as seeding?

[–] grapemix@lemmy.ml 2 points 2 weeks ago

Hdd is a lot tougher than you think unless you are really running a data center.

[–] CoyoteFacts@piefed.ca 2 points 2 weeks ago

As an idea, I use an SSD as a "Default Download Directory" within qBittorrent itself, and then qB automatically moves it to a HDD when the download is fully finished. I do this because I want the write to be sequential going into my ZFS pool, since ZFS has no defragmentation capabilities.

Hardlinks are only important if you want to continue seeding the media in its original form and also have a cleaned-up/renamed copy in your Jellyfin library. If you're going to continue to seed from the HDD, it doesn't matter that the initial download is done on the SSD. The *arr stack will make the hardlink only after the download is finished.