March 12, 20251 yr Hi, I've successfully passed through my Arc310 gpu and it works great. I've found that I don't need to use --device=/dev/dri/:/dev/dri/ in extra parameters too, just use the "add path, variable, ..." button and choose Device. But the assignment for my Arc310 keeps changing on reboot (eg. /dev/dry/card1 and /dev/dri/renderD128 to /dev/dri/card2 and /dev/dri/renderD129). So I created 2 udev rules to make symbolic links tied to the vendor ID + device ID of the GPU. The gpu symbolic links are /dev/arc310-card and /dev/arc310-render. I've verified that both symbolic links do in fact refer back to the gpu (ls -l /dev/arc310-card --> /dev/dri/card1) But when I pass these 2 symbolic links through in the docker, Plex doesnt recognize that I passed through a GPU at all. Is there something additional I need to do to get these symbolic links to work in the docker run command for this container?
April 13, 20251 yr Lately my Plex install is ballooning my docker folder (I switched from image years ago) and I'm not sure what's up. Not the appdata, but the actual docker container folder data itself as reported by Unraid when you hit "container size" in the docker section of the Unraid gui. I woke up to a notification that my ssd was filling up, and after trying to figure out the source I found the Plex docker size to be reporting over 1TB. Updating/restarting the container seems to reset the size back to the expected 300 or so MB. As far as I can tell all of my mounts are correctly mounted to outside of the container (I have not changed them in well over a year). Looking at the different support channels, I seem to be having a similar issue to this post: https://forums.plex.tv/t/unraid-plex-ballooning-overlay2-folder-in-docker-directory/865874 but since the issue was not resolved over on the Plex forums I figured I'd try here as well. I just restarted the container to clear some space and neglected to grab logs, I'll update this post later when I start to see it fill up again. I was wondering if anyone has any ideas where to start for dealing with this.
April 13, 20251 yr We've had a report of this before, it's likely the Sonic Analysis dumping files in `/run/plex-temp/` and not deleting them. Really plex should be dumping this in your tmp folder/memory and at least deleting them when done.
April 13, 20251 yr my guess would be do to this folder data path: as /tmp/transcode is what I use for plex and don't have a issue. /tmp is unraids tmp folder already in ram. the /dev/shm needs made before using that path and is another memroy disk in ram... /dev/shm may be too smal for your transcode casing a disk full eror make extra unneded read and writes...
April 13, 20251 yr 30 minutes ago, j0nnymoe said: We've had a report of this before, it's likely the Sonic Analysis dumping files in `/run/plex-temp/` and not deleting them. Really plex should be dumping this in your tmp folder/memory and at least deleting them when done. Gotcha, thanks for the tip! I'll see if I can find a solution.
April 13, 20251 yr 41 minutes ago, bmartino1 said: my guess would be do to this folder data path: as /tmp/transcode is what I use for plex and don't have a issue. /tmp is unraids tmp folder already in ram. the /dev/shm needs made before using that path and is another memroy disk in ram... /dev/shm may be too smal for your transcode casing a disk full eror make extra unneded read and writes... Thanks for the tip but transcoding to ram has been working for me for a long time this way, I have 128GB of ram and have never had an issue before. I also don't notice disk usage increasing when transcodes are being done.
April 13, 20251 yr @jedivoodoo Did you create a pool called "app" or did you put this in wrong? Typically it's "/mnt/user/appdata/plex"
April 13, 20251 yr 6 minutes ago, MowMdown said: @jedivoodoo Did you create a pool called "app" or did you put this in wrong? Typically it's "/mnt/user/appdata/plex" I have separate SSDs for the appdata/system shares and download/cache, that's just what I named the appdata drive.
April 13, 20251 yr --shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 as example of a extra parameter... that can set and docker manger paths and sizes.. But if transcode it is not. as I have seen this happen due to temp files created for dvr and live stram access for usb/card tuners.... This I start to question old plex configs such as plugins... you could use the above comands and make a docker variable for /run/plex-temp/ Mapping container path /run/plex-temp/ to /tmp cache worth a test...
May 3, 20251 yr Just read the news about Plex starting to charge for remote streaming from my own server. Incredibly stupid move, what is the best alternative? Emby or Jellyfin?
May 3, 20251 yr 32 minutes ago, truetype said: Just read the news about Plex starting to charge for remote streaming from my own server. Do you have Plex Pass (subscription or lifetime)? If so, this does not affect you. Only the admin user needs Plex Pass and all users can still stream remotely free of charge. Glad I got a lifetime Plex Pass years ago on one of their sales for $75. It's now $250
May 3, 20251 yr 3 hours ago, truetype said: Just read the news about Plex starting to charge for remote streaming from my own server. Incredibly stupid move, what is the best alternative? Emby or Jellyfin? jelly fin... I have a plex lifetime pass. If you don't have a pass and you share your libary to those who don't have a pass then the non pass users have to pay a sub fee to access your server... (This assumes your going through plex auth...) via npn and other reverse proxy means one can setup a secure guest share not go through plex auth to access your local content... -Not easily setup and can be problematic... more on turning off remote access and setting plex config line long forgotten and network advance setting.... *Possible yes, but plex will edit and change that to circumvent soon enouth... *waiting for plex to kill that to support their sub model... ATM have a half hazard version going through tailscale... -Have been testing this for a while with a few who dont' want plex.app or plex.tv to interact with there own self-hosted server... But anywho: Embry is more kodi era while embry is developed, jellyfin would be the better / easier move. Or have others buy the lifetime pass... as Plex is rolling out with non sub member due to maintenance and keeping plex auth BS... *Remote Watch Pass so non-paying users and these who don't have a sub / lifetime pass... members will need the "remote watch" pass to remote connect to your server you are hosting... AS we the community in plex let them slowly take this away from us... but also at the same time lifetime support and continue server maintenance to maintain a api login server is not free... $2 a month for non-members to connect to your self-hosted contact and access to plex iptv is not bad... https://www.plex.tv/plans/ By no means am I fan, but I rather see change to maintain then pelx go bankrupt and belly up and no plex at all... Edited May 3, 20251 yr by bmartino1 remove PI
May 3, 20251 yr 2 hours ago, bmartino1 said: If you don't have a pass and you share your libary to those who don't have a pass then the non pass users have to pay a sub fee to access your server... The key is if the server owner does not have a Plex Pass subscription or lifetime. If the server owner has a Plex Pass, other users of the server can still stream remotely with no charge. From the Plex announcement on the changes: IMPORTANT NOTE FOR CURRENT PLEX PASS HOLDERS: For users who have an active Plex Pass subscription, remote playback will continue to be available to you without interruption from any Plex Media Server, after these changes go into effect. When running your own Plex Media Server as a subscriber, other users to whom you have granted access can also stream from the server (whether local or remote), without ANY additional charge—not even a mobile activation fee. More on that later in this update. Edited May 3, 20251 yr by Hoopster
May 3, 20251 yr 26 minutes ago, Hoopster said: The key is if the server owner does not have a Plex Pass subscription or lifetime. If the server owner has a Plex Pass, other users of the server can still stream remotely with no charge. From the Plex announcement on the changes: IMPORTANT NOTE FOR CURRENT PLEX PASS HOLDERS: For users who have an active Plex Pass subscription, remote playback will continue to be available to you without interruption from any Plex Media Server, after these changes go into effect. When running your own Plex Media Server as a subscriber, other users to whom you have granted access can also stream from the server (whether local or remote), without ANY additional charge—not even a mobile activation fee. More on that later in this update. I'm getting mixed info and results. Thank you for this.
May 4, 20251 yr Same here. I had only read 3rd party articles about it. Good to see info direct from the source. Like Hoopster, I also grabbed a $75 Lifetime Pass, back in 2018.
May 22, 20251 yr Started getting this today:Critical: libusb_init failedAnd the container seems to continue running but accessing the plex host:port spins forever....A restart of the container fixes it but it has happened twice now.EDIT: Nevermind, the log line above it literally says that it can be ignored... lol, so that's a red herring i guess...Not sure why plex is hanging then all of a sudden Edited May 22, 20251 yr by HynesJeff
May 22, 20251 yr 5 minutes ago, HynesJeff said:Started getting this today:Critical: libusb_init failedAnd the container seems to continue running but accessing the plex host:port spins forever....A restart of the container fixes it but it has happened twice now.EDIT: Nevermind, the log line above it literally says that it can be ignored... lol, so that's a red herring i guess...Not sure why plex is hanging then all of a suddenSo in the past, hanging Plex for me has been for a few reasons.First the user induced ones:- major library update or addition where the new library has Thumbnail Creation enabled which slows down the entire server- incorrect drive mapping for temp or transcode to a RAM drive or SSD share where I ran out of space- incorrect CPU pinning and a rogue VM was hogging all the CPU threads and Plex just couldn't do anythingSecond, some non-user ones:- failing SSD pool with NVME read errors in the logs preceding the crash; in the worst case this led to a corrupt database and had to recover from CABackup a month ago and lost some watch history. this one happened to me twice, once was because my second M.2 slow off the chipset was just not good, second was actually a bad aging SSD per the SMART settings- GPU driver lockup; happened on an older NVidia card and after a few failed transcodes, Plex just decided to freeze up in the running state- ISP issues; my ISP got stuck in a loop constantly renewing my WAN IP address with a new one and Plex just couldn't maintain a connection. This wasn't exactly Plex hanging, just no clients could connect unless it was my local PC in web-browser; local Chromecast would keep failing to connect
May 22, 20251 yr 8 minutes ago, axipher said:So in the past, hanging Plex for me has been for a few reasons.First the user induced ones:- major library update or addition where the new library has Thumbnail Creation enabled which slows down the entire server- incorrect drive mapping for temp or transcode to a RAM drive or SSD share where I ran out of space- incorrect CPU pinning and a rogue VM was hogging all the CPU threads and Plex just couldn't do anythingSecond, some non-user ones:- failing SSD pool with NVME read errors in the logs preceding the crash; in the worst case this led to a corrupt database and had to recover from CABackup a month ago and lost some watch history. this one happened to me twice, once was because my second M.2 slow off the chipset was just not good, second was actually a bad aging SSD per the SMART settings- GPU driver lockup; happened on an older NVidia card and after a few failed transcodes, Plex just decided to freeze up in the running state- ISP issues; my ISP got stuck in a loop constantly renewing my WAN IP address with a new one and Plex just couldn't maintain a connection. This wasn't exactly Plex hanging, just no clients could connect unless it was my local PC in web-browser; local Chromecast would keep failing to connectThanks for the reply!So its freezing again. not a lot of reads on my SSD but there are some. Other apps are running fine off it. Not much CPU activity either.What else is interesting is I could actually connect to the local ip:port but it said the backend was down .... so it wouldn't load any media. but the webui was up :Dnow the webui hangs as well.Does look like there was a job "optimizing databases" that seemed to have been running before i could reconnect. There's no array activity so its not accessing any of my media.EDIT:Yes looks like its thed database optimization that is being very slow... From the plex logs:May 22, 2025 10:00:50.674 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db/DatabaseFixups] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/DatabaseFixups.cpp:234): 0.170000 secondsMay 22, 2025 10:00:50.873 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db/DatabaseFixups] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/DatabaseFixups.cpp:402): 0.130000 secondsMay 22, 2025 10:00:52.172 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/FullTextSearch.cpp:58): 1.290000 secondsMay 22, 2025 10:00:53.211 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/FullTextSearch.cpp:71): 0.770000 secondsMay 22, 2025 10:00:55.879 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/FullTextSearch.cpp:81): 2.560000 secondsMay 22, 2025 10:00:58.782 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/FullTextSearch.cpp:94): 2.710000 secondsMay 22, 2025 10:25:59.627 [23294880897848] WARN - JobManager: Could not find job for handle 398 Edited May 22, 20251 yr by HynesJeff
May 22, 20251 yr 3 minutes ago, HynesJeff said:Thanks for the reply!So its freezing again. not a lot of reads on my SSD but there are some. Other apps are running fine off it. Not much CPU activity either.What else is interesting is I could actually connect to the local ip:port but it said the backend was down .... so it wouldn't load any media. but the webui was up :Dnow the webui hangs as well.Does look like there was a job "optimizing databases" that seemed to have been running before i could reconnect. There's no array activity so its not accessing any of my media.There is a chance there is a database issue, there have been many in the past with so many different troubleshooting methods.Especially if you had a freeze/hang during a database task.I would just make sure you take a full backup of where you are now and take a look at some Plex database fixing threads to use when Plex is shutdown. It's annoying, tedious and can take a while to figure out.
May 22, 20251 yr 21 minutes ago, axipher said:There is a chance there is a database issue, there have been many in the past with so many different troubleshooting methods.Especially if you had a freeze/hang during a database task.I would just make sure you take a full backup of where you are now and take a look at some Plex database fixing threads to use when Plex is shutdown. It's annoying, tedious and can take a while to figure out.looks like my db file com.plexapp.plugins.library.db went from ~300MB to over 20GB! between May 15 and 18... what? I didn't do anything.
May 22, 20251 yr looks like it might be this:https://forums.plex.tv/t/library-db-size-more-than-doubled-in-latest-version/918851EDIT:fixed after following this post: https://forums.plex.tv/t/library-db-size-more-than-doubled-in-latest-version/918851/64the steps I took were to shut down plex, make a backup of the db. then follow the steps to connect to the sql database and rundelete from statistics_bandwidth where account_id is NULL;this took HOURS...and then I ran this, which shrunk the size back down to ~300MB after the deletions (much faster):VACUUM; Edited May 23, 20251 yr by HynesJeff
May 27, 20251 yr Guys, I just had to rebuild my Plex docker because my appdata become corrupt.Got Plex up and running, however remote users with Nvidia Shield Pros cannot direct play HDR titles. They used to flawlessly.Here's how their stream shows on my end.Even when disabling subtitles, there's no difference. There should be no transcoding, but I can't figure out why Plex is insisting on it.I've noticed that when unchecking 'enable HDR tonemapping' it allows him to play the title back in HDR - but previously I had this checked so that clients who couldn't play HDR could still benefit from HDR tonemapping. Those who could direct play HDR could still do so flawlessly.Any ideas? Edited May 27, 20251 yr by Corvus
May 29, 20251 yr SOLVED!I fixed my own problem. It wasn't anything mentioned on any other help forum. Instead, it's a new quirk of Plex. In 'remote access' settings, I had my correct upload speed entered (just like I did on the old server). I didn't think anything of it, especially since the old server no longer exists. All I did on a hunch was delete the value and press 'save'. Despite Plex telling me 'no upload speed set', HDR now streams flawlessly!Thanks for the new 'feature', Plex!
June 9, 20251 yr Solved! Solution just below by ConnerVTSuddenly today I have multiple files not able to be played, some played for a bit then stalled, while others won't even start. These files play fine when using my Nvidia Shield that is hardwired, but when trying to play them on my phone or tablet via wifi as well as on my Windows desktop (through Firefox, hardwired), the files will stall or not even open. I did notice that there was an update for the linuxserver plex docker, but even after updating the issue persists.Running Unraid 7.0.1 and just updated Plex to the latest version available.Edit: Been poking around, trying to find a possible solution and when checking the plex docker, I get multiple lines of:Jobs: Exec of /config/Library/Application Support/Plex Media Server/Codecs/EasyAudioEncoder-8f4ca5ead7783c54a4930420-linux-x86_64/EasyAudioEncoder/EasyAudioEncoder failed. (13)Jobs: Exec of /config/Library/Application Support/Plex Media Server/Codecs/EasyAudioEncoder-8f4ca5ead7783c54a4930420-linux-x86_64/EasyAudioEncoder/EasyAudioEncoder failed. (13)Jobs: Exec of /config/Library/Application Support/Plex Media Server/Codecs/EasyAudioEncoder-8f4ca5ead7783c54a4930420-linux-x86_64/EasyAudioEncoder/EasyAudioEncoder failed. (13)Now trying to figure out how to correct this. Edited June 10, 20251 yr by bitzie Solved
June 10, 20251 yr Stop Plex.Delete the Codecs folder.Start PlexPlex will download a fresh Codecs folder with the correct files.This has been an ongoing thing with Plex for several years.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.