PMS on Synology 720+, new media auto scan not working (errors in log)

Plex Media Server NAS & Devices
,
1

Hello Plex Community -

Server: DS720+, DSM 6.2.3-25426 Update 3
PMS: version 1.22.1.4275

I’ve got an issue with PMS running on a new Synology 720+, which I recently manually updated to version 1.22.1.4275 running natively on the device.

New media never appears to be detected by auto scans - I have to manually rescan the library, which subsequently does find added media. Checking the logs, I am seeing errors related to permissions issues on folders. For example:

Apr 05, 2021 00:04:16.623 [0x7f22b92be700] ERROR - [Notify] Failed to add watch for "/volume2/Media/TV Shows/TV Series/Banshee/Season 1" (13: Permission denied)

I do know my share of *nix, and have read up a reasonable amount on Plex/Synology, but I’m either missing something simple, or at the mercy of something more subtle that’s causing the permissions issue.

A few details to help with support:

  • Permissions: User ‘plex’ has ‘Full Control’ of my Plex share, and ‘Read/Write’ access on my Media share, which is the root folder for media. (For kicks I previously set Plex to Read-Only on my media share, but nothing changed) These permissions are set on the Media folder itself, and also appear to be identical when items are added. I am the owner for everything, with the group ‘user’, and all these permissions of course check out in the shell via ‘ls’

  • inotify: Also for kicks, I went ahead and increased my table size from the default (8192 apparently) to 32768, because why not. I used ChuckPa’s stickied post on the topic, as per the FAQ. It made no apparent difference. I shouldn’t have needed to do this, as total folders under Media only number in the hundreds.

  • Settings: I do have both “Scan my files automatically” and “Run a partial scan when changes…” enabled, and have tried every combination thereof.

  • Media share: This is a share I created myself (not a default share), with the above listed permissions. Nothing really outstanding to mention. Recycling is enabled, NFS is not.

  • Library: This is a new library on a new device. Fresh install of Plex on a new NAS, and fresh import of media files from another drive. Note that previously, the media on the original drive was used with a Win10 Intel NUC Plex server, and everything worked fine. Have also added new media since, all permissions match

  • PMS Version: I was previously running the public version as per the Package Center (1.18?) which is when I first encountered issues. Updated to 1.22.1.4275

So what gives? Does anyone have leads on what could be causing my permissions issues, as per my logs? What user is being denied what access? plex adding a file watch? How can that be, with the permissions I’ve provided?

I don’t immediately see any additional errors, and the server appears to be working relatively well otherwise.

I feel like I’m quickly exhausting all reasonable options on this, so any help is greatly appreciated. Thanks in advance!

image
image867×577 26.2 KB

3

I did the steps as prescribed, and there’s some improvement – new folders that I create manually do appear to work, but anything copied onto the NAS originally is still giving me the Error 13 permissions issue.

The problem would appear to be at the “leaf” folder level at this point, as new folders will work, even when sharing a parent with a non-working one.

Looking at the permissions in a shell, and in DSM, in both cases they have identical user/group ownership and permissions.

How can this be? What could different about the old folders, that is causing them to not work, when they appear to have identical rights? What am I missing?

image

In the above example “No” works (the log reflects a successful notify) while “Mu” does not (log reflects an error on notify)

5

Man. I followed that exactly, and it worked like a charm, @trumpy81 you’re a real peach, THANK YOU!

Incidentally, I did actually think of trying recursive ‘chown’ w/ admin prior to your post, but alone it didn’t help. I didn’t think of dropping the nuclear option with those repeated type-specific chmod’s…

PMS is running like a champ now, better even thank my old NUC. Thanks again!

6

Hi,

Ive run into the same issue but cannot see @trumpy81 reply that seemed to resolve your issue.

Argh this one is bugging me to no end!

7

If automatic scan isn’t working, it usually has to deal with the total number of directories being monitored.

Linux has 8192 maximum by defalt.

Photos and music can blow that out in nothing flat.

Please do the following:

  1. Setttings - Server - General- Show Advanced
  2. DEBUG - Checked
  3. VERBOSE - unchecked
  4. SAVE if changes made
  5. Restart PMS
  6. – Now the tough part –
  7. Wait 4 minutes for PMS to fully start up (and fill that table if that’s the problem)
  8. Settings - Server - Troubleshooting - Download Logs
  9. Attach the ZIP file it gives you here with your next replies.
8

Hi,

Thank you for your reply, would you please be able to share the line of information you are looking for within the logs so I can pick it out for you?

Kindest regards

9

I don’t have the exact line but it will contain:

[DATE TIME stamp]  - [Notify]  - ERROR:   No space left on device.  (28)

It will contain the error code (28)

10

Ok, thank you for sharing.

I had looked through prior to sending my previous reply and nothing stood out. After looking again but this time with that details you provided, there is nothing there that resembles anything like that.

Music/Photos is also not something I use Plex for at this time, so wasnt sure that tables would be the issue.

Thanks again

11

@MarkToon

These messages appear during the first few minutes after PMS starts as
it initializes the Notify table.

12

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.