Jellyfin unable to attach or mount volumes

Hello everyone,

currently I’m trying to install Jellyfin as an App.
The installation itself works without any problems.
As soon I’m trying to connect it with an SMB share Jellyfin isn’t able to properly start anymore.
I was following a video guide from “Frozen North” (TrueNAS Scale: Plex and Jellyfin Setup with SMB) because I couldn’t find any documentation.

Here’s the error message I receive:

MountVolume.MountDevice failed for volume "jellyfin-jellyfin-0-3107982171" : rpc error: code = Internal desc = volume(truenas.local/Bag of Holding#jellyfin-jellyfin-0-3107982171) mount "//truenas.local/Bag of Holding" on "/var/lib/kubelet/plugins/kubernetes.io/csi/smb.csi.k8s.io/4fcdc7d26adfe416babaf39f202b15db6589a75051799f227e1bc727c3d840e0/globalmount" failed with mount failed: exit status 1 Mounting command: mount Mounting arguments: -t cifs -o noperm,gid=568,<masked> //truenas.local/Bag of Holding /var/lib/kubelet/plugins/kubernetes.io/csi/smb.csi.k8s.io/4fcdc7d26adfe416babaf39f202b15db6589a75051799f227e1bc727c3d840e0/globalmount Output: mount error: could not resolve address for truenas.local: Unknown error

Huge thanks in advance to everyone who is willing and able to help me out here!

Kind regards
Gévarred

Do you have a bridge set up to allow the app to communicate with local storage? Accessing NAS From a VM | TrueNAS Documentation Hub

I haven’t.
Unfortunately I didn’t mention that I installed Jellyfin through the “App Store”. I’m not running a virtual machine in any way.

Or am I misunderstanding something here and a virtual machine is necessary to use Jellyfin in combination with SMB share?

Nevertheless, I will try out the method later!

Gévarred

I have JF running - it’s the TrueNAS app - and I also have it running via docker (compose, c/o dockge). However, my shares are both NFS and SMB, so perhaps that makes a difference.

Here are the screenshots of my TN app and further down my docker compose file should you wish to pursue that route.

Please note that I am an expert on neither!



services:
  jellyfin:
    image: lscr.io/linuxserver/jellyfin:latest
    container_name: jellyfin
    environment:
      - PUID=65534
      - PGID=65534
      - TZ=Etc/UTC
      - JELLYFIN_PublishedServerUrl=192.168.1.193:8096 #optional
    volumes:
      - /mnt/data/jellyfin/config:/config
      - /mnt/data/jellyfin/transcodes:/config/data/transcodes
      - /mnt/music:/data/music
      - /mnt/photographs:/data/photographs
      - /mnt/videos:/data/videos
    ports:
      - 8096:8096
    #      - 8920:8920 #optional
    #      - 7359:7359/udp #optional
    #      - 1900:1900/udp #optional
    restart: unless-stopped
networks: {}

Thanks for your answer!
I’ve now tried both methods and had more luck with the solution from E_B.
Jellyfin is able to start but I don’t see any media.


I can’t see anything “obvious” but the only ideas I have are these (bearing in mind my knowledge is limited - there are few people here who know less than me!):

1 - linux doesn’t like gaps in directory or filenames, needing to be “escaped”. Perhaps the space in your /mnt/Little Friend/ ... is upsetting things

2 - if you can’t easily change that directory name to Little_Friend, or perhaps it is a red herring anyway, you could set up a test dataset which you could put a couple of jpegs or MP3s inside, and try pointing to it. Datasets are easy to create and delete with no risk.

3 - What does the directory contain that you’re currently pointing at (“/mnt/ ...Shenanigans”)? Maybe there’s something in there which is causing distress for JF … maybe make it only contain MP3s or only contain jpegs … maybe one of each as per (2) above.

1 Like

Thanks for the advice!

I’ll try out option 1 and 2 as soon I’ve got the time and will let you know how the results are!
Inside the folder are only .mp3’s.

Gévarred