Docker Plex Server crashing on startup after WSL disk overflow

Plex Media Server Desktops & Laptops
1

Server Version#: 1.41.8.9834-071366d65

I’m currently running Plex Server using the linuxserver.io docker image on Windows via WSL2. A few days ago, the WSL2 disk ran out of space, causing processes to hang, and Plex to crash the docker container logs show:

2025-08-08T14:43:25.760441749Z Starting Plex Media Server. . . (you can ignore the libusb_init error)
2025-08-08T14:43:26.776573079Z Connection to localhost (::1) 32400 port [tcp/*] succeeded!
2025-08-08T14:43:27.907501409Z ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.8.9834-071366d65/PLEX MEDIA SERVER/63f3d9e6-afc8-426e-15c011bb-17630bbb.dmp
2025-08-08T14:43:28.386377890Z Starting Plex Media Server. . . (you can ignore the libusb_init error)
2025-08-08T14:43:29.403603802Z Connection to localhost (::1) 32400 port [tcp/*] succeeded!
2025-08-08T14:43:30.562835213Z ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.8.9834-071366d65/PLEX MEDIA SERVER/068a316d-7904-4b15-e38c9e80-31ede14f.dmp
2025-08-08T14:43:31.129276534Z Starting Plex Media Server. . . (you can ignore the libusb_init error)
2025-08-08T14:43:32.147093239Z Connection to localhost (::1) 32400 port [tcp/*] succeeded!
2025-08-08T14:43:33.288011254Z ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.8.9834-071366d65/PLEX MEDIA SERVER/0824e960-3e59-41f6-62858aaa-770ccfb3.dmp
2025-08-08T14:43:33.953371944Z Starting Plex Media Server. . . (you can ignore the libusb_init error)
2025-08-08T14:43:34.974080564Z Connection to localhost (::1) 32400 port [tcp/*] succeeded!
2025-08-08T14:43:36.254568151Z ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.8.9834-071366d65/PLEX MEDIA SERVER/783c9d82-da0c-49a7-ba680990-7b05e9e9.dmp
2025-08-08T14:43:36.637173609Z Starting Plex Media Server. . . (you can ignore the libusb_init error)
2025-08-08T14:43:37.654486051Z Connection to localhost (::1) 32400 port [tcp/*] succeeded!
2025-08-08T14:43:38.693646415Z ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.8.9834-071366d65/PLEX MEDIA SERVER/ef54d2e6-666c-4ceb-3e7a9b8e-9daa7d72.dmp
2025-08-08T14:43:39.049002996Z Starting Plex Media Server. . . (you can ignore the libusb_init error)
2025-08-08T14:43:40.066232335Z Connection to localhost (::1) 32400 port [tcp/*] succeeded!
2025-08-08T14:43:41.363708727Z ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.8.9834-071366d65/PLEX MEDIA SERVER/9faa081b-2cb4-4bae-f556f0a5-f8548ee4.dmp

Logs.zip (478.1 KB)

The disk space issues were resolved, and service started, however Plex now crashes on startup. Plex Media Server logs stopped at INFO - Running migrations. (EPG 0). Assuming a corrupt DB or configuration file, I have performed the following steps:

Replace DB with Plex-generated backups as per the documentation - No change using backups up to a week before the issue.

Attempted to rebuild the DB as per documentation - PRAGMA integrity_check returns no errors, VACUUM and REINDEX do not resolve the issue. Following the Low-Level Database Recovery succeeded in creating a new database which was ~1MB smaller than the original DB, however attempting to use this new db made no difference either.

Remove Preferences.xml to force recreation - No change.

Remove DB entirely, to force creation of an empty DB - New DB is generated, but Plex seems to crash during setup with the following:

Aug 08, 2025 15:43:33.275 [132407002307384] DEBUG - [JobRunner] Job running: /usr/lib/plexmediaserver/CrashUploader "--directory=/config/Library/Application Support/Plex Media Server/Crash Reports/1.41.8.9834-071366d65" --version=1.41.8.9834-071366d65 --platform=Linux --platformVersion=6.6.87.2-microsoft-standard-WSL2 --serverUuid=ae1ba955bb42c8d7aba2063cf463ae6af5977ad2 --userId=NOUSERID --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --vendor=Docker --model=x86_64 "--device=Docker Container (LinuxServer.io)"
Aug 08, 2025 15:43:33.275 [132407002307384] DEBUG - [JobRunner] Jobs: Starting child process with pid 412

Has anybody else experienced anything similar? I can recreate the container easily enough, but I’d rather not lose watch history etc. if at all possible.

Thanks in advance.

2

I think I already know the answer to this, but why in world are you running PMS under Docker on Windows?

3

Just ease in general. The rest of my self-hosted stack is deployed via docker, and managed through Portainer - I also have several additional VPS-hosted nodes for critical services that are also managed through Portainer to keep everything under one roof. The rest of my media stack (*arrs etc.) are deployed via docker, so it makes sense to include Plex in that for pure ease of management.

Docker also simplifies my setup for security, by using a reverse proxy, and KeyCloak for auth. Another setup that I’d rather not have to duplicate if at all possible.

I don’t have any objection to hosting in Windows directly, but it does complicate the setup somewhat, which I’d like to avoid if possible.

4

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