Plex Causing Network Error to Seagate NAS Device

Server Version#: 1.40.0.7998, Windows 10 Home 22H2 19045.4046, Dell XPS 8700, x64, i7-4790 @3.60GHz
Player Version#: N/A
NAS: Seagate PersonalCloud 6TB

I’ve been using Plex for years. A couple of months ago Plex (v1.32) could no longer access media stored on my NAS.

The NAS was up and available via the PersonalCloud web interface. I could not access the folders via file explorer or command prompt but I could download files from the web interface.

Restarting the NAS would allow connections & access for a short period of time and then it would fail as before.

I connected to the NAS via ssh (a little out of my comfort zone) and saw that there was no space left in /tmp.

There were many ‘core.####’ files in /tmp which showed 0% free space. Deleting all the core dump files fixed the issue temporarily. Restarting the NAS cleared out the core dump files. When I start Plex I can see the core dump files begin to accumulate.

When /tmp got to 0% space free is when the connection got lost.

This came out of nowhere. I can’t think of anything out of the ordinary on the server that would have triggered something like to start happening.

Hopefully someone smarter than I am can point me to alleviate the problem

Can you post your server logs?

Here are the logs

Thanks @dbirch

Plex Media Server Logs_2024-03-03_08-55-20.zip (2.1 MB)

Just to show the behavior I ran this from ssh

[cpmfinster@PersonalCloud tmp]$ clear;pwd;df -h .;ll -t core.*;sleep 300;df -h .;ll -t core.*

/tmp
Filesystem                Size      Used Available Use% Mounted on
none                    249.9M    768.0K    249.2M   0% /tmp
ls: core.*: No such file or directory

[started Plex]

Filesystem                Size      Used Available Use% Mounted on
none                    249.9M      9.6M    240.4M   4% /tmp
-rw-------    1 root     root       1216512 Mar  3 14:48 core.8679
-rw-------    1 root     root       1216512 Mar  3 14:48 core.8674
-rw-------    1 root     root       1216512 Mar  3 14:48 core.8371
-rw-------    1 root     root       1216512 Mar  3 14:47 core.8330
-rw-------    1 root     root       1216512 Mar  3 14:46 core.7702
-rw-------    1 root     root       1216512 Mar  3 14:46 core.7355
-rw-------    1 root     root       1216512 Mar  3 14:46 core.7348
-rw-------    1 root     root       1216512 Mar  3 14:46 core.6695
-rw-------    1 root     root       1216512 Mar  3 14:44 core.4323
[cpmfinster@PersonalCloud tmp]$

@cpmfinster unfortunately you disabled debug logs so most of the useful data is not in your logs, but I would check to see if you have a corrupt database per GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server databases

Re-enable debug, not verbose, server logs, then restart Plex Media Server.
Recreate the problem, then pull and post a new set of log files.
You don’t have to wait until /tmp is full, but make sure there are several of the core.#### files.

Settings → Server_Name → General + Show Advanced

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