[BUG] Auto refresh on Ugreen Docker

[MarkusMory]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hello everyone,
I migrated my Plex server from an old QNAP T-251+ to a new Ugreen DXP4800 Pro. Everything works fine but the automatic refresh of media files.

When I drop or remove a file in one of the mounted folders Plex does not notice it. The changes only appear, when I start a manual scan cycle.

I'm not alone with this problem (https://www.reddit.com/r/UgreenNASync/comments/1miq0pu/plex_in_docker_on_ugos_not_autoscanning/). Someone mentioned that UGOS doesn't support inotifiy but I checked that and it works well.

Thank you very much for your support.

Expected Behavior

New or removed files should be automatically noticed by Plex

Steps To Reproduce

1. On my Ugreen DXP4800+
2. Docker compose: see below
3. Put a new file into /volume1/Video/Filme
4. No automatic refresh happens

Environment

- OS: UgreenOS 1.14.1.0107
- How docker service was installed: via Ugreen App store
- Automatic refresh of libraries is activated within Plex

CPU architecture

x86-64

Docker creation

Docker compose:
version: "3"
services:
  Plex2:
    container_name: Plex2
    image: linuxserver/plex:latest
    restart: always
    devices:
      - /dev/dri:/dev/dri
    dns:
      - 192.168.200.20
      - 192.168.200.1
    domainname: fritz.box
    environment:
      - TZ=Europe/Berlin
      - PUID=1001
      - PGID=100
      - VERSION=docker
    hostname: Plex2
    ipc: private
    networks:
      LAN-Docker:
        ipv4_address: 192.168.200.23
    volumes:
      - /volume1/docker/Container-Shares/Plex/Config:/config
      - /volume1/Video/Filme:/movie
      - /volume1/Video/Serien:/tv

networks:
  LAN-Docker:
    external: true

Container logs

[migrations] started

[migrations] no migrations found

usermod: no changes

───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗

      ██║     ██╔════╝██║██╔═══██╗

      ██║     ███████╗██║██║   ██║

      ██║     ╚════██║██║██║   ██║

      ███████╗███████║██║╚██████╔╝

      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io

───────────────────────────────────────

To support LSIO projects visit:

https://www.linuxserver.io/donate/

───────────────────────────────────────

GID/UID

───────────────────────────────────────

User UID:    1001

User GID:    100

───────────────────────────────────────

Linuxserver.io version: 1.43.0.10492-121068a07-ls299

Build-date: 2026-04-06T10:15:13+00:00

───────────────────────────────────────

    

**** permissions for /dev/dri/renderD128 are good ****

**** permissions for /dev/dri/card0 are good ****

**** Server already claimed ****

#######################################################

# Update routine will not run because you haven't set #

# the VERSION variable or you opted out of updates.   #

#          For more information checkout :-           #

#    https://github.com/linuxserver/docker-plex       #

#######################################################

[custom-init] No custom files found, skipping...

Starting Plex Media Server. . . (you can ignore the libusb_init error)

Connection to localhost (::1) 32400 port [tcp/*] succeeded!

[ls.io-init] done.

Critical: libusb_init failed

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[j0nnymoe]

This isn't going to be a container problem. Likely related to the file system of your ugreen nas.
Seen similar issues with unionfs and mtime not being presented to plex so it doesn't detect the new files.

[MarkusMory]

This isn't going to be a container problem. Likely related to the file system of your ugreen nas. Seen similar issues with unionfs and mtime not being presented to plex so it doesn't detect the new files.

Thank you very much for the quick response. I already talked to Ugreen support but they said it's not a problem on there side. Could you tell me how I can check if there are unionfs and mtime issues, so I can forward it to them?

[j0nnymoe]

It's just an example I experienced 8 or so years ago. I'd be surprised if that was the problem now.
Realistically though, I'm 99% confident that it's not an issue with our container as many users across many platforms use it (Unraid/Synology/QNAP/Debian etc) - we've never stumbled upon this internally with the systems we have access to.

Unfortunately no one within the team has a ugreen nas so it's not something we're able to test.

[MarkusMory]

Thank you again. I tried to check it with help of Gemini and it said to try the following

root@Nas2:~# mount | grep /volume1
/dev/mapper/ug_A9D812_1774988873_pool1-volume1 on /volume1 type ext4 (rw,nosuid,nodev,noatime,nobarrier,quota,usrquota,grpquota,prjquota)

==> The problem is the noatime which stops the parent folder from updating the time stamp.

[zhaoshouli]

I’ve confirmed with both inotifywait and stat that file changes are indeed being detected, but Plex still does not update automatically. Could you please let me know how Plex detects file changes internally, so I can perform more targeted testing on my side? I would greatly appreciate your help. Thank you very much.

[aptalca]

Could you please let me know how Plex detects file changes internally, so I can perform more targeted testing on my side?

That's a question for Plex