PMS Constant Disk Activity

Plex Media Server
1

Server Version#: 1.20.4.3517 (latest at time of writting).
Player Version#: Unrelated
(File removed)

Hi
I’ve been having this issue since I started using Plex almost a year ago. I’m running the official docker for PMS on Unraid 6.8.3 (latest version). As this issue has been going on for the whole time, I don’t think its Plex/Unraid version dependent.

What I’m seeing is constant reading and writing to my array when the PMS docker image is on, it never stops. Its about 50kb/s, but it causes all disks in the array to be spun up, and the parity writing 24/7.

I’ve read other support queries about this, but I can’t kind a connection to my setup. I’m not transcoding, its not only when new files come in etc, its 24/7. I’ve tried turning all library scanning tasks completely off, but it didnt seem to change anything. I know its plex, as if I stop the docker image, the disk activity stops.

I’ve attached my logs, hopefully the correct type.

Thanks for any assistance anyone can offer!
Cheers
Ryan

2

Same problem on my QNAP NAS with PMS: constant 24/7 disk activity when PMS is on, with no apparent reason, no disk activity when PMS is off…

3

Hi
Can anyone offer any advice on this? I’ve been through the logs myself, but I can’t see anything. I’ve triple checked all background tasks are off.
Is there a proper support channel I can do through being a ‘plex pass’ subscriber?
Cheers
Ryan

4

Plex relies on a database (SQLITE). The nature of databases is such that it syncs memory to filesystem at regular intervals keeping your drives active. In addition, Plex will check status with any clients on the local network writing statistics to the database as well as updating the logs.

5

Thanks for the info @pl_5309, but I don’t think thats the issue. The ‘transcode’ and ‘data’ volumes are both on an ssd cache, I’m seeing continuous reads, then writes to the whole array, which are regular drives.
Besides, if no media is changed, and no client is playing from plex, why would it be hitting the sqlite db 24x7x365?
Cheers
Ryan

6

Don’t know what to say other than to look for yourself.

Tail the logs: https://support.plex.tv/articles/200250417-plex-media-server-log-files/

Watch the timestamp on the database directory.

cd $PLEX_HOME/Library/Application\ Support/Plex\ Media\ Server/Plug-in\ Support/Databases/
7

+1

I am a full “plex pass” subscriber as well.

On the logs I can see that MyPlex is constantly losing and recovering connectivity, I do not know whether it is linked but probbaly because all this connection/deconnection sequence is producing events that are probably written in the Plex db.

Jan 12, 2021 09:40:32.518 [0x7f36968a9700] ERROR - getaddrinfo(192-168-17-25.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: -2

Jan 12, 2021 09:40:32.518 [0x7f36968a9700] DEBUG - Network: 192-168-17-25.abcdefghijklmnopqrstuvwxyz012345.plex.direct failed to resolve to 192.168.17.25 but instead yielded “”

Jan 12, 2021 09:40:32.518 [0x7f36968a9700] DEBUG - PublicAddressManager: Obtaining public address and mapping port.

Jan 12, 2021 09:40:32.518 [0x7f36968a9700] DEBUG - MyPlex: async reachability check - current mapped state: ‘Mapped - Not Published’.

Jan 12, 2021 09:40:32.518 [0x7f36968a9700] WARN - MyPlex: we have an existing connectivity refresh request for async identifier 9c54442b-2b06-4af9-84f0-d35ea9950ace, but it has expired so we will try again.

Jan 12, 2021 09:40:32.518 [0x7f36968a9700] DEBUG - MyPlex: Requesting reachability check.

Jan 12, 2021 09:40:32.518 [0x7f3617a23700] DEBUG - NAT: UPnP, attempting port mapping.

Jan 12, 2021 09:40:32.518 [0x7f3665fc5700] DEBUG - PublicAddressManager: Obtaining public IP.

Jan 12, 2021 09:40:32.518 [0x7f3665fc5700] DEBUG - HTTP requesting GET http://plex.tv/pms/:/ip

Jan 12, 2021 09:40:32.518 [0x7f36968a9700] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/e5f7503f2aa48c87a2bab3e782e5193cdb262747/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=d9ea4bea-7cb3-4cc9-bcba-e0d7266b037f

Jan 12, 2021 09:40:32.606 [0x7f3665fc5700] DEBUG - HTTP 200 response from GET http://plex.tv/pms/:/ip

Jan 12, 2021 09:40:32.606 [0x7f3665fc5700] DEBUG - PublicAddressManager: Got public IP from http://plex.tv: 86.77.88.38

Jan 12, 2021 09:40:32.685 [0x7f36968a9700] DEBUG - HTTP 200 response from PUT https://plex.tv/api/servers/e5f7503f2aa48c87a2bab3e782e5193cdb262747/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=d9ea4bea-7cb3-4cc9-bcba-e0d7266b037f

Jan 12, 2021 09:40:32.686 [0x7f36968a9700] DEBUG - EventSource: Successfully connected to 178.79.145.139.

Jan 12, 2021 09:40:32.686 [0x7f36968a9700] DEBUG - EventSource: Failure in IdleTimeout (0 - Success).

Jan 12, 2021 09:40:32.686 [0x7f36968a9700] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.

Jan 12, 2021 09:40:32.686 [0x7f36968a9700] ERROR - EventSource: Retrying in 15 seconds.

Jan 12, 2021 09:40:36.523 [0x7f3665fc5700] DEBUG - NAT: UPnP, found device http://192.168.17.1:80/RootDevice.xml with private address <192.168.17.25>

Jan 12, 2021 09:40:36.529 [0x7f3617a23700] DEBUG - NAT: UPnP, found device http://192.168.17.1:80/RootDevice.xml with private address <192.168.17.25>

Jan 12, 2021 09:40:36.558 [0x7f3665fc5700] DEBUG - NAT: UPnP, usable device http://192.168.17.1:80/RootDevice.xml with private address <192.168.17.25>.

Jan 12, 2021 09:40:36.568 [0x7f3617a23700] DEBUG - NAT: UPnP, usable device http://192.168.17.1:80/RootDevice.xml with private address <192.168.17.25>.

Jan 12, 2021 09:40:36.578 [0x7f3665fc5700] DEBUG - NAT: UPnP, public address is 86.77.88.38

Jan 12, 2021 09:40:36.613 [0x7f3617a23700] DEBUG - NAT: UPnP, mapped port 20281 to 192.168.17.25:32400.

Jan 12, 2021 09:40:36.626 [0x7f3665fc5700] DEBUG - HTTP requesting GET https://86-77-88-38.705242c7a4de42e9ab82a5dc8dcb246c.plex.direct:20281/identity

Jan 12, 2021 09:40:36.650 [0x7f3617d11700] DEBUG - Request: [86.77.88.38:53214 (WAN)] GET /identity (2 live) TLS GZIP Signed-in

Jan 12, 2021 09:40:36.692 [0x7f3665fc5700] DEBUG - HTTP 200 response from GET https://86-77-88-38.705242c7a4de42e9ab82a5dc8dcb246c.plex.direct:20281/identity

Jan 12, 2021 09:40:36.693 [0x7f3617a23700] DEBUG - PublicAddressManager: Mapping succeeded for 192.168.17.25:20281.

Jan 12, 2021 09:40:36.693 [0x7f36965bb700] DEBUG - Completed: [86.77.88.38:53214] 200 GET /identity (2 live) TLS GZIP 43ms 451 bytes

Jan 12, 2021 09:40:36.694 [0x7f3665fc5700] DEBUG - MyPlex: mapping state set to ‘Mapped - Not Published’.

Jan 12, 2021 09:40:36.696 [0x7f3617a23700] DEBUG - MyPlex: mapping state set to ‘Mapped - Not Published’.

Jan 12, 2021 09:40:36.698 [0x7f3617a23700] DEBUG - MyPlex: Updating device connections (from timer: 0)

Jan 12, 2021 09:40:36.698 [0x7f3617a23700] DEBUG - HTTP requesting PUT https://plex.tv/devices/e5f7503f2aa48c87a2bab3e782e5193cdb262747?Connection[][uri]=http://192.168.17.25:32400&httpsEnabled=1&httpsRequired=0&dnsRebindingProtection=1&natLoopbackSupported=1&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx

Jan 12, 2021 09:40:36.884 [0x7f3617a23700] DEBUG - HTTP 200 response from PUT https://plex.tv/devices/e5f7503f2aa48c87a2bab3e782e5193cdb262747?Connection[][uri]=http://192.168.17.25:32400&httpsEnabled=1&httpsRequired=0&dnsRebindingProtection=1&natLoopbackSupported=1&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx

Jan 12, 2021 09:40:36.885 [0x7f3665fc5700] DEBUG - MyPlex: Last published value didn’t change, we’re done.

Jan 12, 2021 09:40:47.686 [0x7f36968a9700] DEBUG - EventSource: Resolving 178.79.145.139 port 443

Jan 12, 2021 09:40:47.686 [0x7f36968a9700] DEBUG - EventSource: Resolved 178.79.145.139 to 178.79.145.139

Jan 12, 2021 09:40:47.765 [0x7f36965bb700] DEBUG - EventSource: Connected in 52 ms.

Jan 12, 2021 09:40:47.765 [0x7f36965bb700] DEBUG - EventSource: Wrote data, reading reply.

Jan 12, 2021 09:40:47.843 [0x7f36968a9700] DEBUG - EventSource: Read HTTP reply header.

Jan 12, 2021 09:40:47.843 [0x7f36968a9700] DEBUG - MyPlex: We appear to have regained Internet connectivity.

8

Hi
Thought I better post, as I hate finding threads with new resolution by the original poster. I’ve been running PMS on Unraid, always stable versions, never RC, beta. Today I was doing some cleanup and maintainence, and stopped the PMS docker and saw disk activity mostly stop as expected. I then stopped the docker service on unraid.

After doing the maintenance, I re-enabled the docker service, and got a strange error, that I had to ‘recreate my docker image file’. I let it do this, then I had to readd my docker containers, but the data was still on unraid. Now PMS no longer constantly fires up the disks. The issue was with Unraid. Not sure how I got this bug, or how long it goes back, but I found this: https://forums.unraid.net/topic/75771-need-to-recreate-docker-image-how/
Like I said, and the poster in that forum, I’d never run a beta version of unraid, so its very strange.

Hope this helps someone.
Cheers

9

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