Plex and Jellyfin apps won't start

[jmcguire525]

Cleanest way is to always plan the use of /mnt/pool/dataset as base, for example /mnt/default/media. Inside it, you can create or move all the directories you want and never worry about any issues in Plex or any other application. This is actually the intended use of a shared dataset.

View attachment 60941

While there, don't forget to add a ramdisk, if you transcode in Plex. See discussion:

View attachment 60942

Is there any issue mounting the ramdisk to an existing directory since /tmp is created during installation?

 

[Daisuke]

You can mount the ramdisk to any directory containing volatile data, that you don’t care losing after a reboot. I personally like to use /tmp because it is a standard directory for this type of data and it does not store any essential Plex files. See this thread.

 

[kjs]

Same problem here with Plex from Official Catalog (stuck DEPLOYING) when /data is in SMB type.

I use it in a Test environment with non-critical data and I use CLI to change:
app kubernetes update validate_host_path=false

after then Plex starts without problems

 

[Daisuke]

See this thread, it explains how I fixed all conflicts with datasets and SMB shares. You should definitely not disable validate_host_path.