Separating your services from your storage makes things a lot easier in my opinion.
Setup one machine as a NAS and have that manage your (preferably redundant and backuped if storing personal photos or other unique data) storage, then share it to the rest of your selfhosting over nfs and smb.
You could either go for a prebuilt NAS like Ugreen NASync DXP2800 or build your own m-itx with a Jonsbo N2 case and an N100 motherboard or whatever you’re comfortable with.
Your jellyfin server then accesses the media libraries with a simple mount (/mnt/media). Same with your tdarr server and tdarr nodes.
It’s much easier to experiment and reinstall services when you have your storage separated from them.
I can’t buy a 14tb hdd for that price here in Sweden, but I have no idea about your local prices. Is it new or refurb?
Scrath@lemmy.dbzer0.com 12 hours ago
Out of curiosity, do yoy know how Jellyfin handles network failures with mounted network drives?
I had a navidrome server where once my network machine failed to start properly, the entire database was deleted because it looked to the server like I deleted all of my files. I luckily had my favorites cached on my phone client and was able to restore most of my playlists from there but it was still an incredibly annoying thing to go through. I have since turned off automatic scanning of files for that service since that seemed like the only way to prevent this happening again
anamethatisnt@sopuli.xyz 4 hours ago
Just like navidrome it seems like Jellyfin reacts to failed mounts by emptying libraries.
…jellyfin.org/t-solved-network-not-mounted-before…
With version 10.11.0 they offer a built in backup system for db/metadata/subtitles though so once access is restored it’s easy to restore any metadata changes you’ve done to your library. (As long as you got a backup since before that is)
jellyfin.org/docs/general/…/backup-and-restore/#c…