Migrate from Windows to Docker on DS920+ now HDD constantly works

[LordReaper]

Server Version#: 1.30.0.6486
Player Version#: doenst matter

Hello together,
so i made a migration from a windows 10 desktop system to a ds920+. The migration was quite smooth. I copied the “plex media folder” contents to my nas in a mounted path for the plex docker and it was recognized. I then attached the new media files and i got the same state as i had on my windows system. The only difference is, that my nas always works on the hdd. So i turned on the logs to see what causes the activity but i am not sure why there is activity on my plex server. I tried to google the request but i did not find anything. Maybe someone got a clue what i missed or where this activity comes from.
It seems like someone tries to sign in or to use my login. So i logged out all clients to see if i can find the device that is causing the activity. But i cannot seem to find it. Here the logs:

Jan 14, 2023 17:33:44.202 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36656 (Loopback)] GET /identity (8 live) #1687e Signed-in
Jan 14, 2023 17:33:44.202 [0x7efe43216b38] Fehlersuche — Completed: [[::1]:36656] 200 GET /identity (8 live) 0ms 398 bytes (pipelined: 1)
Jan 14, 2023 17:33:49.442 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36658 (Loopback)] GET /identity (8 live) #16893 Signed-in
Jan 14, 2023 17:33:49.443 [0x7efe43419b38] Fehlersuche — Completed: [[::1]:36658] 200 GET /identity (8 live) 0ms 398 bytes (pipelined: 1)
Jan 14, 2023 17:33:54.710 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36660 (Loopback)] GET /identity (8 live) #1689a Signed-in
Jan 14, 2023 17:33:54.710 [0x7efe43419b38] Fehlersuche — Completed: [[::1]:36660] 200 GET /identity (8 live) 0ms 398 bytes (pipelined: 1)
Jan 14, 2023 17:33:59.977 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36662 (Loopback)] GET /identity (8 live) #168a1 Signed-in
Jan 14, 2023 17:33:59.977 [0x7efe43216b38] Fehlersuche — Completed: [[::1]:36662] 200 GET /identity (8 live) 0ms 398 bytes (pipelined: 1)
Jan 14, 2023 17:34:05.300 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36664 (Loopback)] GET /identity (8 live) #168a8 Signed-in
Jan 14, 2023 17:34:05.300 [0x7efe43216b38] Fehlersuche — Completed: [[::1]:36664] 200 GET /identity (8 live) 0ms 398 bytes (pipelined: 1)
Jan 14, 2023 17:34:10.705 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36668 (Loopback)] GET /identity (4 live) #168af Signed-in
Jan 14, 2023 17:34:10.705 [0x7efe43419b38] Fehlersuche — Completed: [[::1]:36668] 200 GET /identity (4 live) 0ms 398 bytes (pipelined: 1)
Jan 14, 2023 17:34:15.975 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36670 (Loopback)] GET /identity (4 live) #168ba Signed-in
Jan 14, 2023 17:34:15.976 [0x7efe43419b38] Fehlersuche — Completed: [[::1]:36670] 200 GET /identity (4 live) 0ms 398 bytes (pipelined: 1)
Jan 14, 2023 17:34:21.260 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36672 (Loopback)] GET /identity (4 live) #168c1 Signed-in
Jan 14, 2023 17:34:21.260 [0x7efe43419b38] Fehlersuche — Completed: [[::1]:36672] 200 GET /identity (4 live) 0ms 398 bytes (pipelined: 1)
Jan 14, 2023 17:34:26.517 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36674 (Loopback)] GET /identity (4 live) #168c8 Signed-in
Jan 14, 2023 17:34:26.517 [0x7efe43419b38] Fehlersuche — Completed: [[::1]:36674] 200 GET /identity (4 live) 0ms 398 bytes (pipelined: 1)
Jan 14, 2023 17:34:31.893 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36676 (Loopback)] GET /identity (4 live) #168cf Signed-in
Jan 14, 2023 17:34:31.893 [0x7efe43216b38] Fehlersuche — Completed: [[::1]:36676] 200 GET /identity (4 live) 0ms 398 bytes (pipelined: 1)
Jan 14, 2023 17:34:37.179 [0x7efe3ceedb38] Fehlersuche — Request: [[::1]:36678 (Loopback)] GET /identity (4 live) #168d6 Signed-in
Jan 14, 2023 17:34:37.179 [0x7efe43419b38] Fehlersuche — Completed: [[::1]:36678] 200 GET /identity (4 live) 0ms 398 bytes (pipelined: 1)

[ChuckPa]

Docker 5 second health check . Address ::1 is IPv6 for 127.0.0.1

If you put PMS natively (an equally valid option), you won’ have that problem.

[LordReaper]

Hey @ChuckPa thank you for your hint. I disabled IPv6 but that did not stop the activity. I found that docker is running a healtcheck every few seconds and checks the state of a docker container. I am not sure how to get rid of that function. Is there a way to disable the healthcheck or to make it testing every few hours. I don’t need it testing itself every 5 seconds.
Thank you!

[ChuckPa]

@ChuckPa

Docker 5 second health check

That’s what I said.

You can’t get rid of it because that’s Docker,

You can switch from being in a Docker container to using the native PMS app on Synology (same functionality)

[Streamerx]

Hey,
And can he use the same db from the windows Pms for synology??
Just copy the complete windows pms data folder to the right pms folder on the synology nas?
I thought windows db is just a little bit different than when you install pms on synology?

[LordReaper]

@ChuckPa thank you. Actually i cannot get rid of it because i got some dockers running like unifi controller and other software. So this would not change much. I will see if i can get more information from docker or synology. There must be an option to set the healtcheck to a lower intervall.

@Streamerx i got no problem with plex as direct service or running in a docker environment. The database was read wonderful. Just watch out, that you dissable the setting for automatic deleting of trash and nothing will happen. Runs smooth on both.

[plex136]

I resolved this by adding the following parameter to my docker-compose. This disables the health check.

healthcheck:
disable: true

[ChuckPa]

@Streamerx

And can he use the same db from the windows Pms for synology??
Just copy the complete windows pms data folder to the right pms folder on the synology nas?

To migrate from Windows is very simple. I have written a FAQ about it.

The essence:

1. Install Plex (DSM 7)

2. Create a “Plex” shared folder if you don’t have one.

3. In it , create “Library / Application Support”

4. Copy the “Plex Media Server” folder (and everything below it) to “Application Support” on the Syno

5. Change the permissions (must be Full Control for PlexMediaServer) – see the FAQ

6. Uninstall the DSM 7 app – use the ERASE button (discard the empty DSM 7 server)

7. Install again.

8. It will automatically start migrating (importing) into the DSM 7 structure.
   – It will sit at “Installing” until done.

9. Open another tab.

10. In that tab, watch for then open “Migration.log”. This is where it’s at in the process of importing.

11. “Completed: Cleaning /volume1/Plex” is “all done”.

The PMS DSM 7 server will pick up right where the Windows server left off.

At this point, you only need grant permissions to “PlexMediaServer” on each shared folder.

Synology FAQ - Questions, Answers, and a few How-To's

FAQ 26 - Migrate from another OS → DSM 7 Migrating from another PMS installaton to Synology DSM 7 requires a little bit of up-front work. The basic procedure is: Prepare the existing installation for copying Create a “Plex” shared folder on DSM which will be the base share for importing. Create the folders “Plex/Library/Application Support” Copy the “Plex Media Server” folder and contents into “Application Support” Manually set permissions of the Plex share, and all files in the shared f…

Synology FAQ - Questions, Answers, and a few How-To's

FAQ 29 - DSM 7 - Give PlexMediaServer access to your media When you migrate to DSM 7, or are installing a server for the first time, folks forget to read the popup at the end of every installation which tells them about how to set permissions. This FAQ shows in detail how to do what those instructions state. When might you need to perform these steps? When upgrading, changing permissions from Plex to PlexMediaServer is overlooked. Installing Plex for the first time, new installation…

You can use Docker if you really really want but there is no advantage anymore.

Running docker containers along side PMS (like tautulli) works perfectly whether PMS is native app or container app.