Hi All

I cannot post in the docker support page however I just updated my Unraid to 7.3.4 and now my plex docker has broken, I think it has something to do with using Nvidia for transcoding, not 100% sure. however I am getting this error in the Logs for plex If i try and view the web UI i get this message also:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

<Response code="503" title="Maintenance" status="Plex Media Server is currently running database migrations."/>

Error: Unable to set up server: std::exception (N2DB9ExceptionE)

2026-11-05 22:12:55,797 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23323333749552 for <Subprocess at 23323334165840 with name start-script in state RUNNING> (stdout)>

2026-11-05 22:12:55,797 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23323333749328 for <Subprocess at 23323334165840 with name start-script in state RUNNING> (stderr)>

2026-11-05 22:12:55,797 WARN exited: start-script (exit status 255; not expected)

2026-11-05 22:12:55,797 DEBG received SIGCHLD indicating a child quit

2026-11-05 22:12:56,800 INFO spawned: 'start-script' with pid 2335

2026-11-05 22:12:56,808 DEBG 'start-script' stdout output:

[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process.

[INFO] Removing any existing Plex Media Server PID...

2026-11-05 22:12:56,809 DEBG 'start-script' stdout output:

[INFO] Ensure encoder binaries are executable...

2026-11-05 22:12:56,811 DEBG 'start-script' stdout output:

[info] Starting Plex Media Server...

2026-11-05 22:12:57,812 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2026-11-05 22:12:58,085 DEBG 'start-script' stdout output:

It has been running fine for years "binhead-lexpass" however im at a complete loss on how to fix this. I downloaded Plex DB Repair but that wont start either.

Any advice very welcome here.

That error isn't related to the NVIDIA transcoding. The container is starting and Plex itself is running. It's failing while upgrading its library database: the 503 "running database migrations" page together with N2DB9ExceptionE means the database migration step is failing, which usually happens because the Plex version changed (the container was likely updated at around the same time as Unraid).

First, please post the diagnostics zip (Tools > Diagnostics) taken while the problem is happening, so we can confirm that the pool or disk holding appdata has free space and isn't read-only or showing filesystem errors.

If the storage looks fine, the problem is most likely the Plex database itself:

1. Look at the last lines of Plex Media Server.log, in the Logs folder inside your Plex appdata. It should show the exact error behind the failed migration.

2. Plex keeps automatic database backups in Plug-in Support/Databases, named like com.plexapp.plugins.library.db-YYYY-MM-DD. With the container stopped, make a copy of the whole Databases folder first, then restore the most recent backup from before the update, following Plex's guide:

https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

3. Plex also has a repair guide: https://support.plex.tv/articles/repair-a-corrupted-database/

For questions about the container itself, the binhex support thread (or the Plex forums) is the best place, since they know the app much better.

2 hours ago, JorgeB said:

That error isn't related to the NVIDIA transcoding. The container is starting and Plex itself is running. It's failing while upgrading its library database: the 503 "running database migrations" page together with N2DB9ExceptionE means the database migration step is failing, which usually happens because the Plex version changed (the container was likely updated at around the same time as Unraid).

First, please post the diagnostics zip (Tools > Diagnostics) taken while the problem is happening, so we can confirm that the pool or disk holding appdata has free space and isn't read-only or showing filesystem errors.

If the storage looks fine, the problem is most likely the Plex database itself:

1. Look at the last lines of Plex Media Server.log, in the Logs folder inside your Plex appdata. It should show the exact error behind the failed migration.

2. Plex keeps automatic database backups in Plug-in Support/Databases, named like com.plexapp.plugins.library.db-YYYY-MM-DD. With the container stopped, make a copy of the whole Databases folder first, then restore the most recent backup from before the update, following Plex's guide:

https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

3. Plex also has a repair guide: https://support.plex.tv/articles/repair-a-corrupted-database/

For questions about the container itself, the binhex support thread (or the Plex forums) is the best place, since they know the app much better.

Hiya Jorge

Thank you for taking the time to help, Please find the attached ZIP hopefully I can figure this out with some help. Im a hardware fixer not a software fixer ;-(

Here is the plexmediaserver.log text

Nov 06, 2026 09:48:36.048 [22664859077432] INFO - Plex Media Server v1.43.5.11079-b3b13e506 - unknown LENOVO ThinkServer TS140 unknown - build: linux-x86_64 redhat - GMT 00:00

Nov 06, 2026 09:48:36.048 [22664859077432] INFO - Linux version: 6.18.58-Unraid (#2 SMP PREEMPT_DYNAMIC Wed Oct 21 15:43:26 PDT 2026), language: en-US

Nov 06, 2026 09:48:36.048 [22664859077432] INFO - Processor: 4-core Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz

Nov 06, 2026 09:48:36.048 [22664859077432] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)

Nov 06, 2026 09:48:36.048 [22664859077432] INFO - /usr/lib/plexmediaserver/Plex Media Server

Nov 06, 2026 09:48:36.045 [22664966253200] DEBUG - BPQ: [Idle] -> [Starting]

Nov 06, 2026 09:48:36.047 [22664966253200] DEBUG - FeatureManager: Using cached data for features list

Nov 06, 2026 09:48:36.052 [22664966253200] DEBUG - MyPlex: mapping state set to 'Unknown'.

Nov 06, 2026 09:48:36.053 [22664966253200] DEBUG - Relay: read 107 cached entries from hosts file

Nov 06, 2026 09:48:36.054 [22664966253200] DEBUG - Opening 20 database sessions to library (com.plexapp.plugins.library), SQLite 3.53.3, threadsafe=1

Nov 06, 2026 09:48:36.181 [22664966253200] DEBUG - MyPlex: using cached data for request for https://servers.plex.tv/api/v2/server/users/features?filterFeatures[]=b83c8dc9-5a01-4b7a-a7c9-5870c8a6e21b&filterFeatures[]=926bc176-58ca-47da-b8e3-080ed14ea6ba&filterFeatures[]=ea791163-c28d-4b7c-af88-bcc9553b206d&filterFeatures[]=6ab6677b-ad9b-444f-9ca1-b8027d05b3e1&filterFeatures[]=56cd352b-0d47-436d-aced-f20db3508de5

Nov 06, 2026 09:48:36.206 [22664966253200] DEBUG - [CERT] Subject name is /CN=*.22b09d623898424d97e0574b71e91ef8.plex.direct

Nov 06, 2026 09:48:36.206 [22664966253200] DEBUG - [CERT] Installed certificate with fingerprint fb:7c:17:15:d2:dd:aa:2d:2e:93:0b:d2:29:8c:bc:fa:89:1a:fb:c3.

Nov 06, 2026 09:48:36.206 [22664966253200] DEBUG - [CERT/OCSP] no URL available

Nov 06, 2026 09:48:36.206 [22664966253200] WARN - [CERT/OCSP] getCertInfo failed; skipping stapling

Nov 06, 2026 09:48:36.206 [22664966253200] DEBUG - HttpServer: Listening on IPv6 as well as IPv4.

Nov 06, 2026 09:48:36.206 [22664966253200] DEBUG - HttpServer: Listening on port 32400.

Nov 06, 2026 09:48:36.207 [22664966253200] DEBUG - HttpServer: Listening on port 32401.

Nov 06, 2026 09:48:36.207 [22664966253200] DEBUG - Running server...

Nov 06, 2026 09:48:36.207 [22664846424888] DEBUG - HttpServer: Set up a thread pool with 2 threads.

Nov 06, 2026 09:48:36.207 [22664966253200] INFO - Running migrations. (EPG 0)

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 0.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 1.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 2.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 3.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 4.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 5.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 6.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 7.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 8.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 9.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 10.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 11.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 12.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 13.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 14.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 15.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 16.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 17.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 18.

Nov 06, 2026 09:48:36.208 [22664966253200] DEBUG - Captured session 19.

Nov 06, 2026 09:48:36.520 [22664966253200] DEBUG - ChangestampAllocator: initialized to 297314229

Nov 06, 2026 09:48:37.319 [22664966253200] ERROR - SQLITE3:0x80000001, 11, database corruption at line 99871 of [d4c0e51e4a]

Nov 06, 2026 09:48:37.319 [22664966253200] ERROR - SQLITE3:0x80000001, 11, statement aborts at 5: database disk image is malformed; [UPDATE activities SET finished_at=started_at WHERE finished_at IS NULL]

Nov 06, 2026 09:48:37.319 [22664966253200] ERROR - Error: Unable to set up server: std::exception (N2DB9ExceptionE)

Nov 06, 2026 09:48:37.319 [22664966253200] DEBUG - [JobRunner] Job running: /usr/lib/plexmediaserver/CrashUploader --sessionStatus=abnormal --sessionStart=1793958516 --sessionDuration=1 --version=1.43.5.11079-b3b13e506 --[email protected] --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Nov 06, 2026 09:48:37.320 [22664966253200] DEBUG - [JobRunner] Jobs: Starting child process with pid 1513

tower-diagnostics-20261106-0945.zip

Edited 10 hours ago10 hr by Randall8686

The storage side is fine: your appdata is on the cache pool, which has plenty of free space and no filesystem errors. The Plex log shows the actual cause:

database disk image is malformed

This means the Plex library database file itself is corrupt. The damage was most likely already there before the update, and the new Plex version only found it when it tried to upgrade that part of the database. It isn't caused by Unraid or NVIDIA.

The easiest fix is to restore one of Plex's automatic backups:

1. Stop the Plex container.

2. Go to your Plex appdata, then Plex Media Server/Plug-in Support/Databases, and copy the whole Databases folder somewhere safe first.

3. In that folder, delete (or rename) com.plexapp.plugins.library.db and any com.plexapp.plugins.library.db-wal / -shm files next to it.

4. Take the newest backup, named like com.plexapp.plugins.library.db-2026-MM-DD, and rename a copy of it to com.plexapp.plugins.library.db. If there is a com.plexapp.plugins.library.blobs.db backup with the same date, do the same for that file.

5. Start the container and check the log. If the newest backup also shows "malformed", stop the container and try the next older one.

Plex's guide for this: https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

You will lose only the changes since that backup (watch status, recently added items). Plex adds those again on the next library scan.

If none of the backups work, the next step is Plex's repair procedure: https://support.plex.tv/articles/repair-a-corrupted-database/. For help with that, the binhex Plex support thread or the Plex forums are the best place.

Not related to this, but you still have the old "Unraid-Nvidia" plugin from 2019 installed next to the current "nvidia-driver" plugin. You can remove the old one from the Plugins page.

2 hours ago, JorgeB said:

The storage side is fine: your appdata is on the cache pool, which has plenty of free space and no filesystem errors. The Plex log shows the actual cause:

database disk image is malformed

This means the Plex library database file itself is corrupt. The damage was most likely already there before the update, and the new Plex version only found it when it tried to upgrade that part of the database. It isn't caused by Unraid or NVIDIA.

The easiest fix is to restore one of Plex's automatic backups:

1. Stop the Plex container.

2. Go to your Plex appdata, then Plex Media Server/Plug-in Support/Databases, and copy the whole Databases folder somewhere safe first.

3. In that folder, delete (or rename) com.plexapp.plugins.library.db and any com.plexapp.plugins.library.db-wal / -shm files next to it.

4. Take the newest backup, named like com.plexapp.plugins.library.db-2026-MM-DD, and rename a copy of it to com.plexapp.plugins.library.db. If there is a com.plexapp.plugins.library.blobs.db backup with the same date, do the same for that file.

5. Start the container and check the log. If the newest backup also shows "malformed", stop the container and try the next older one.

Plex's guide for this: https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

You will lose only the changes since that backup (watch status, recently added items). Plex adds those again on the next library scan.

If none of the backups work, the next step is Plex's repair procedure: https://support.plex.tv/articles/repair-a-corrupted-database/. For help with that, the binhex Plex support thread or the Plex forums are the best place.

Not related to this, but you still have the old "Unraid-Nvidia" plugin from 2019 installed next to the current "nvidia-driver" plugin. You can remove the old one from the Plugins page.

Thank you for this information. I will give this a go later and report back :)

3 hours ago, JorgeB said:

The storage side is fine: your appdata is on the cache pool, which has plenty of free space and no filesystem errors. The Plex log shows the actual cause:

database disk image is malformed

This means the Plex library database file itself is corrupt. The damage was most likely already there before the update, and the new Plex version only found it when it tried to upgrade that part of the database. It isn't caused by Unraid or NVIDIA.

The easiest fix is to restore one of Plex's automatic backups:

1. Stop the Plex container.

2. Go to your Plex appdata, then Plex Media Server/Plug-in Support/Databases, and copy the whole Databases folder somewhere safe first.

3. In that folder, delete (or rename) com.plexapp.plugins.library.db and any com.plexapp.plugins.library.db-wal / -shm files next to it.

4. Take the newest backup, named like com.plexapp.plugins.library.db-2026-MM-DD, and rename a copy of it to com.plexapp.plugins.library.db. If there is a com.plexapp.plugins.library.blobs.db backup with the same date, do the same for that file.

5. Start the container and check the log. If the newest backup also shows "malformed", stop the container and try the next older one.

Plex's guide for this: https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

You will lose only the changes since that backup (watch status, recently added items). Plex adds those again on the next library scan.

If none of the backups work, the next step is Plex's repair procedure: https://support.plex.tv/articles/repair-a-corrupted-database/. For help with that, the binhex Plex support thread or the Plex forums are the best place.

Not related to this, but you still have the old "Unraid-Nvidia" plugin from 2019 installed next to the current "nvidia-driver" plugin. You can remove the old one from the Plugins page.

two points, my last backups are from 2019 (not a huge issue but annoying) I guess i have something turned off so its not backing up

It seems to have "loaded" this time however I cannot reach the server and when i use any devices it says the server is offline

___. .__ .__

\_ |__ |__| ____ | |__ ____ ___ ___

| __ \| |/ \| | \_/ __ \\ \/ /

| \_\ \ | | \ Y \ ___/ > <

|___ /__|___| /___| /\___ >__/\_ \

\/ \/ \/ \/ \/

https://hub.docker.com/u/binhex/

2026-11-06 13:04:51.970194 [info] Host is running unRAID

2026-11-06 13:04:51.992129 [info] System information: Linux Tower 6.18.58-Unraid #2 SMP PREEMPT_DYNAMIC Wed Oct 21 15:43:26 PDT 2026 x86_64 GNU/Linux

2026-11-06 13:04:52.013632 [info] Image architecture: 'amd64'

2026-11-06 13:04:52.036404 [info] Application name: 'plexpass'

2026-11-06 13:04:52.059780 [info] Base image release tag: '2026092801'

2026-11-06 13:04:52.082302 [info] Application image release tag: '1.43.5.11079-1-01'

2026-11-06 13:04:52.106240 [info] PUID defined as '99'

2026-11-06 13:04:52.128720 [info] User 'nobody' already has UID '99', skipping usermod

2026-11-06 13:04:52.152597 [info] PGID defined as '100'

2026-11-06 13:04:52.178806 [info] Group 'users' already has GID '100', skipping groupmod

2026-11-06 13:04:52.200450 [info] UMASK defined as '000'

2026-11-06 13:04:52.224362 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'

2026-11-06 13:04:52.253564 [info] Deleting files in /tmp (non recursive)...

2026-11-06 13:04:52.281272 [info] TRANS_DIR defined as '/config/transcode'

2026-11-06 13:04:52.310867 [info] Starting Supervisor...

2026-11-06 13:04:52,419 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing

2026-11-06 13:04:52,419 INFO Set uid to user 0 succeeded

2026-11-06 13:04:52,422 INFO RPC interface 'supervisor' initialized

2026-11-06 13:04:52,422 INFO supervisord started with pid 7

2026-11-06 13:04:53,427 INFO spawned: 'claim-script' with pid 69

2026-11-06 13:04:53,429 INFO spawned: 'start-script' with pid 70

2026-11-06 13:04:53,429 INFO reaped unknown pid 8 (exit status 0)

2026-11-06 13:04:53,432 DEBG 'claim-script' stdout output:

[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping claim process.

2026-11-06 13:04:53,433 INFO success: claim-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2026-11-06 13:04:53,433 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23040280417952 for <Subprocess at 23040281689264 with name claim-script in state RUNNING> (stdout)>

2026-11-06 13:04:53,433 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23040280303952 for <Subprocess at 23040281689264 with name claim-script in state RUNNING> (stderr)>

2026-11-06 13:04:53,433 INFO exited: claim-script (exit status 0; expected)

2026-11-06 13:04:53,433 DEBG received SIGCHLD indicating a child quit

2026-11-06 13:04:53,434 DEBG 'start-script' stdout output:

[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process.

[INFO] Removing any existing Plex Media Server PID...

2026-11-06 13:04:53,435 DEBG 'start-script' stdout output:

[INFO] Ensure encoder binaries are executable...

2026-11-06 13:04:53,438 DEBG 'start-script' stdout output:

[info] Starting Plex Media Server...

2026-11-06 13:04:54,441 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Updates its come alive, It just updating libraries at the moment as there is obviously a lot of added media since the backup of 2019. I will figure out how to set these to back up as its obviously not doing library back ups.

I may try and repair my old library files if it possible then replace them back again.

Edited 6 hours ago6 hr by Randall8686