Server Version#: 1.41.3.9292
when selecting/adding volumes on plex server, i show multiple drive shadows for some reason…its most likely super simple…but whats causing this?
i do find cortect path, but why so many listings? how can i correct?
Your logs indicate docker.
Dec 12, 2024 07:02:45.159 [140120637565752] INFO - Plex Media Server v1.41.3.9292-bc7397402 - Docker Docker Container (LinuxServer.io) x86_64 - build: linux-x86_64 debian - GMT 00:00
Dec 12, 2024 07:02:45.160 [140120637565752] INFO - Linux version: 5.10.0-10-amd64, language: en-US
Dec 12, 2024 07:02:45.160 [140120637565752] INFO - Processor: 4-core Intel(R) Celeron(R) CPU N3450 @ 1.10GHz
Dec 12, 2024 07:02:45.160 [140120637565752] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Dec 12, 2024 07:02:45.160 [140120637565752] INFO - /usr/lib/plexmediaserver/Plex Media Server
Dec 12, 2024 07:02:45.159 [140120640101008] DEBUG - BPQ: [Idle] -> [Starting]
That as basis, what you see in PMS is entirely dependent on what you pass in the docker configuration ( run or compose file )
And this reply helps the situation how?
Your OP asks the cause.
My reply: Stating Docker & its config spec (compose or run file) is how these devices get inside the container and hence seen by PMS.
The answer here is to refine / limit / correct the docker config file.
Secondarily, as information only, I’ve not seen anyone use your distro of Linux with success (much like how Mint doesn’t work well with PMS either)
Chuck, nothing. in your two reply is of any help in anyway… at all
and the disro comments, well…no help either…at alll…why have you took time to say nothing at all?
nothing to do?
if you don’t have a solution…please do not reply so someone else can offer way to correct this…
On the host OS, run sudo docker container inspect <plex container name>. In the JSON output, find the ‘Mounts’ section. (Alternatively, if you have jq installed, you can run sudo docker container inspect <plex container name> | jq '.[].Mounts' instead to have it print just the mount information.)
Post the mount information here so we can see what’s being passed to the container. Bonus points: Run ls -alh on the host for each of the paths which is being mounted in the container.
Though, to @ChuckPa’s point, Plex Media Server is presenting to you the paths which the OS/Docker environment is presenting to it. So, adjustments are likely going to be needed in your configuration for this container.
Will give it a go later. I suspect it has to do with making. Or updating plex. Was fine before last update. Plus i added a drive. most likely over powered the little zimmaboard… could stream plex then all the sudden loose path. Then all the shadow drives appeared.
actually did factory os recovery and updated things, installed stable version pms… and up and running perfectly… zimmaboard casaOS
