Hey all, been running TrueNAS Scale for a few months now on a PC I built along with Proxmox on another mini PC I bought.
I tried setting up my media server on TrueNAS scale but didn’t like my NAS running hot and being used so much but tried setting up Jellyfin and the arr media suite on Proxmox but ran into some issues with NFS shares and also SMB shares from TrueNAS along with config issues.
Just wondering if anyone has any suggestions or recommendations on how I should setup my media server and home network.
Reduce the need to transcode.
I run jellyfin on my NAS and the arr stack on a separate PC. I then manually sftp things over like and animal. My PC is running bodhi.
Why not use samba or something to map the NAS as a remote drive and have the arrs use it as their destinstion folder?
I was having an issue getting nfs working and it just left a bad taste for me. I think your right I should just mout it and be done.
Running a Debian VM with Docker solved all those issues for me. I set the arrs root /data folder on my NAS to mount with CIFS at boot. It works so well with a ceiling of 4/8 cores and 12GB RAM I’ve moved all my containers to it and mostly just use Proxmox for monitoring and reliable backups/images over NFS.
The only issue I’ve had in the last year or so took me about 30 minutes between realizing something was wrong and fixing it: Make sure you put your CIFS credentials file in a folder accessible to Debian’s main user account or a power loss will break automount until you re-establish the link with a root user. Or create a locked down arrs-only user on your NAS so the CIFS command can include the username and password with less concern.
I have a very similar setup. Jellyfin in Docker on a Debian VM (2 cores, 8GB RAM), and all the media on the NAS. The CIFS/SMB from the NAS is mounted in fstab. I keep all the metadata locally for speed - ie not on the NAS. I don’t like the extra layer of running Docker, but it works like a charm whereas I had a few hassles running Jellyfin natively in the VM. I do have a special ‘media’ user with the name and password in the mount command which only has permissions for the media.
Can’t comment on the arrs suite since I get all my linux distros on those disks attached to the front of magazines.
I run a Plex container on Proxmox and have it connect to my Armbian/OMV NAS via SMB. The way I got SMB shares working was to mount them from the Proxmox host and then mount them read-only from the container. (better security ig) I’d be happy to share my configs although it might take me a couple days to pull them up.
Another alternative I’ve been thinking about is buying an external drive rack and attaching it to the outside of my server’s PC case. Then running SATA extenders but this might not be possible depending on the kind of mini PC and I’ve heard extending power can get dicey if you have more than a few drives.
I run almost exactly the same thing. Plex running in Proxmox VM with a GPU passthrough, and an OMV instance in Proxmox VM hosting all the data shares. Proxmox also hosts multiple Docker stacks for various instances. This is spread out over multiple bare metal boxes.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters NAS Network-Attached Storage Plex Brand of media server package SATA Serial AT Attachment interface for mass storage
3 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.
[Thread #235 for this sub, first seen 24th Oct 2023, 03:55] [FAQ] [Full list] [Contact] [Source code]
I run a couple of instances of Plex in Proxmox containers. I use containers so I can share the GPU/Network across more than one CT. I think if you use a VM it can only pass through the GPU to one
Get a better cooler?
