I have a sizeable music library. When I select “scan library”, it starts and adds albums for a few minutes. However, it then stops without any error message. When I restart, it yet again scans for a few minutes and adds more albums. But then stops again. etc etc.
Any thoughts what I can try to troubleshoot this issue?
For starters, disable all the music-related analysis features on
Settings - [server name] - Settings - Library
That way, no time is spent doing these in-between the actual scan.
Ensure that there is plenty of free space on both the storage volume which holds the Plex data folder, as well as the one which houses the system /tmp folder. It is not a good idea to use a small RAM drive for the latter.
Ensure proper health of your server database file by using GitHub - ChuckPa/DBRepair: Database repair utility for Plex Media Server databases before the scan attempt.
Also, if you happen to have rather large albums (i.e. with more than a few dozen tracks, like box-sets and large retrospective collections), take these out temporarily.
Chances are that the scan will continue afterwards.
Thanks for offering help!
No database corruption. Plenty of free space on the storage volume. Disabled the analyses.
I don’t know where my /tmp folder is. How to find out?
I have increased database cache size to 8GB, but this didn’t help.
I may have some boxsets (tagged with Picard / MBZ). May be a bit cumbersome to remove them and it doesn’t seem to be the issue as it stops at different artists. I can look into this though.
Other thoughts appreciated!
Revert that. This is not a file cache for the database file. A setting of 8Gb will eat up your server’s RAM.
I have quite a bit of Ram, so thought this would help. Have now reduced it back to the standard 40MB.
Just ran it again and attaching my log file.
If this is Docker, and there is no explicit link of /tmp to a folder on a real storage device in the docker config file, then AFAIK /tmp goes into RAM.
Which can get pretty crowded when ingesting a whole library’s worth of new files.
Do you have “Prefer local metatags” enabled or not?
(Don’t enable it unless your embedded meta tags are immaculate.)
Yes, I have it enabled and my meta tags are immaculate. They all went through Picard tagging.
Let me change the /tmp folder to someone on the SSD. Though I have 100+ GB of Ram, so I doubt that this is the issue?
Anything you are seeing in my logs?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
