Non-Stop Indexing Without Progress

Hi. Just checking in. Thanks.

Any news on this? I feel as though I should give up.

No… don’t give up but there is only so much I can do, for which I do apologize.

With PMS running, as it is now, Please go to Settings - Server - Help and click “Download Logs”.

It will give you all the log files in a ZIP file including those of all the agents (Music included)

I haven’t tried to index for awhile as it doesn’t work. should I do this after trying to reindex?

I would rather have the DB start in a completely new set of tables

Create a new library point it to the same data (less if you can) and see the result. Something isn’t right but cannot figure out what it is. nothing is jumping out

Thanks. I didn’t see this response until now. I will do this now and report back.
I have been told that other services (like Roon) seem to handle the data ok.

I just started the index again, and it already seems to be stuck. Here are the logs. Please let me know if you can help, or I should look at another service. Thanks.

It seems to still be indexing, but VERY slowly.

it’s out of disk space

Feb 19, 2017 20:44:46.215 [0xe8bc5b40] ERROR - [Notify] Failed to add watch for /volume1/QNAP NAS Music/QNAP/Music/Hi Rez A/Classical [Hi Rez]/Mahler/Mahler Project - Symphonies - Michael Tilson Thomas, San Francisco SO (2010) [24-96] (28: No space left on device)

That is very strange, as it appears to still be indexing. How can it be indexing if it is out of space? Also, how do I determine where it is saving the data for the index?

It will keep trying until it hard crashes. It’s not going to complete.

Thanks. How do I determine where it is saving the index to?

It’s either running out of space on /volume1 (most likely), or the DSM root (/) volume (which is very bad).

Check the free space of volume1 first as this is where the Plex share exists.

If there is ample free space there,

  1. enable ssh into the DiskStation
  2. ssh to it as admin using the admin password (ssh -l admin ip.of.syno.nas)
  3. sudo -su root
  4. df and examine all the mounted filesystems to see which is 100%

It looks like none of them is at 100%.

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md0 2385528 922028 1344716 41% /
none 1018308 4 1018304 1% /dev
/tmp 1022524 1396 1021128 1% /tmp
/run 1022524 11412 1011112 2% /run
/dev/shm 1022524 8 1022516 1% /dev/shm
none 4 0 4 0% /sys/fs/cgroup
/dev/vg1000/lv 5804800176 5167646052 637035340 90% /volume1

Hi ChuckPA. Could you please check the attached logs instead. It seems that it truly has stopped indexing at this point (whereas that wasn’t the case before).

Updated logs attached. There is still a good amount of room on the NAS.

I’m seeing where it’s actually updating metadata. Can you please check “I Let A Song Go Out Of You” and those items in that vicinity?

Feb 25, 2017 16:35:22.901 [0xdf26bb40] DEBUG - There was a change for metadata item 376682 (I Let A Song Go Out Of You), saving.
Feb 25, 2017 16:35:22.902 [0xdf26bb40] DEBUG - Updating metadata item (save) (I Let A Song Go Out Of You) with ID 376682
Feb 25, 2017 16:35:22.915 [0xdf26bb40] DEBUG - There was a change for metadata item 376668 (Supreme Jazz (SACD-R 5.1)), saving.

I do think it’s time I get a more senior member of the team to take a look as this is on the edge of my mastery.

In looking over our thread, I believe I owe you an apology.

I don’t see where I suggested you increase the update interval to something higher than 15 minutes. It’s entirely possible (and likely given how long this is going on), it keeps retriggering just as it’s about to finish.

I would suggest setting it to update when changes are detected, only do a partial scan, and then go to daily default interval.

Thanks. No apology needed. I think you did tell me this. My current settings are daily / run a partial scan when changes are detected / update my library automatically.

Interestingly enough, I’m not actually sure if it’s timed out yet. It is entirely possible that it is finishing. I’m still moving through the NAS and I will let you know what happens.

when all else fails… Just restart it. It will start clean