Hi,
Since a few versions back, PMS regularly crashes after a few days. Synology model is a DS3617xs running DSM 6.1.5-15254 Update 1. PMS version is 1.12.1.4885.
Another issue is that I have to kill the PMS process via CLI and htop, stopping and restarting the package doesn’t seem to work and the server shows as unavailable.
I’ve included the logs just after one of those crashes.
Already thanking to the ones that are going to look into it.
Thanks for your quick reply !
About the video folder, does it matter if I don’t use video station ?
Just asking before starting to move huge amounts of data !
Even if I disable indexing for that folder ?
Ok, I’m currently expanding my volume with a hard drive, I’ll wait for that to finish and come back to you !
Thanks again.
Thanks for the tips, can I create different shared folders for certain libraries or would you advise against it ?
Alright, everything has been moved to the media folder and it’s subfolders, permissions are correct and I did a repair on the DB even if it wasn’t showing any errors.
My content is slowly updating with the new location.
Is there anything else I need to turn on or off inside DSM ?
Thanks again for everything, I guess I’ll just let everything run for a while and see if the crashes come back !
Do you know if optimizing the database would help, the file scanning seems to be slowing down ?
Any idea why it would take so long to scan my music library ? is it due to the number of files ? (200k+)
I feel like this will take weeks…
Jesus Christ… I’ll be dead of old age before I can use my Plex server normally.
Is there a problem here?
How can I help?
I don’t think so, unless you have a suggestion on how to speed up the scanning process ?
I do have another question, what happens if I cancel the scan for music and scan another small library, just to get access to it ?
Will it start from the beginning for my music library ?
Music libraries, because of how many individual tracks most folks have, are a pain to load that very first time.
A lesson I learned when I ripped all my media made a huge difference on small NAS boxes (DS1815+)
example being:
/music/A-D/
Daft Punk/
Album/
01 - title.ext
etc
/music/E-G/
Now, to load the music library,
/music/A-D directory/music/E-G
The target for me has been about 10-15,000 total tracks maximum per block.
The fundamental problem is database fragmentation. By adding in smaller blocks, locality of reference is more tightly preserved. It results in faster indexing and general operation because both all the tables follow the same block-load order
Just realized I missed part of your question.
When PMS scans again, it will scan through the blocks as listed. It will go through the entire library because iNotify isn’t available but because the DB has the locality, it will be a lot quicker because of the synergy between DB rows and reading the directories in the same sequence.
Sorry, I meant, if I cancel the music library scan to scan the TV Show library, does canceling stop the whole process or will it resume when I rescan the music library ?
Yes. If you cancel… it’s a hard cancel. There is no incremental scan.
“Partial scan” would help here. It will look at “last modified” information. It will save it time from descending into albums for each album directory that hasn’t been modified. It’s not a huge saving per album but does add up quickly.
Thanks, I guess I’ll let it run since I’m already a few days in !
The scanning ended a few hours ago, now to see if this will lead to more stability !
Another unrelated question, I saw another post where you recommend changing the inotify limit:
Would you still recommend it ? My music folder is large enough to not get automatic updates.
