Physical Drive Issue - Database wont copy - Restored database wont allow plex to load

[maxsteel]

Server Version#: 1.41.6.9606
Player Version#: n/a

Logs can be provided as needed.

So I have a problem

It appears that one of my databases is ‘broken’ and has been since Dec 25, 2024 (3.5 months ago). I know that it’s been broken since then, as that is the last time a successful backup was created for this file: com.plexapp.plugins.library.blobs.db-2024-12-25

I apparently have a physical drive issue, as in windows I cannot copy this file as it’ll stall and fail at the 84% mark. (This is the ONLY file that will not copy).

I am trying to move all plexdata to an SSD using the regedit trick which I did years ago and am just changing the drive value from M: to D:.

I have copied all files over with the exception of this one db: com.plexapp.plugins.library.blobs.db

Plex fails on start: Icon in systray, then gone.. some logs dumped,

I have tried to restore, manually, the older com.plexapp.plugins.library.blobs.db-2024-12-25 and rename it to com.plexapp.plugins.library.blobs.db in the new location.

Same deal plex fails on start.

The plex media server.log file contains:

Apr 08, 2025 14:30:09.782 [4592] INFO - Plex Media Server v1.41.6.9606-aa6577194 - System manufacturer System Product Name x64-x64 - build: windows-x86_64 windows - GMT -05:00
Apr 08, 2025 14:30:09.782 [4592] INFO - Windows version: 10.0 (Build 19045), language en-US
Apr 08, 2025 14:30:09.782 [4592] INFO - 8 3693 MHz processor(s): Architecture=9, Level=23, Revision=6145 Processor Identifier=AMD64 Family 23 Model 24 Stepping 1, AuthenticAMD
Apr 08, 2025 14:30:09.782 [4592] INFO - Compiler is - MSVC 1929
Apr 08, 2025 14:30:09.839 [24648] ERROR - SQLITE3:0x7ff689fa54a0, 11, database corruption at line 70168 of [a29f994989]
Apr 08, 2025 14:30:09.839 [24648] ERROR - SQLITE3:0x7ff689fa54a0, 11, database disk image is malformed in "PRAGMA cache_size=2048"
Apr 08, 2025 14:30:09.841 [24648] ERROR - Promise destroyed without handling exception: Promise fell out of scope without resolving or rejecting

the plex crash uploader.log has (I do not have any upload limits set, not sure why this happens)

Apr 08, 2025 14:30:09.988 [1604] INFO - Crash Uploader - Session Health - Status: crashed StartTime: 1744140609 Duration: 0 UserId: user Version: 1.41.6.9606-aa6577194
Apr 08, 2025 14:30:09.988 [1604] INFO - Crash Uploader - Platform: Windows ServerUUID: f2f80ca1580fb75c41105d75d2f92c8b4c359d5e UserId: user Version: 1.41.6.9606-aa6577194
Apr 08, 2025 14:30:09.988 [1604] INFO - Pre-processed minidump directory: d:\plex_media_server_appData\Plex Media Server\Crash Reports\1.41.6.9606-aa6577194
Apr 08, 2025 14:30:09.988 [1604] INFO - Post-processed minidump directory: C:\Users\user\AppData\Local\Temp
Apr 08, 2025 14:30:10.333 [4916] INFO - Successfully reported session health
Apr 08, 2025 14:30:10.346 [4916] INFO - Crashdump 3c1d3188-5c0c-4b73-a6b9-5fccb4d6815e not uploaded due to local rate limiting.
Apr 08, 2025 14:30:10.353 [4916] INFO - Crash Uploader - Processing Complete.

What is weird is that I have also tried to delete the corrupted DB and in the plex media server log I still get:

Apr 08, 2025 14:36:19.769 [26444] INFO - Plex Media Server v1.41.6.9606-aa6577194 - System manufacturer System Product Name x64-x64 - build: windows-x86_64 windows - GMT -05:00
Apr 08, 2025 14:36:19.769 [26444] INFO - Windows version: 10.0 (Build 19045), language en-US
Apr 08, 2025 14:36:19.769 [26444] INFO - 8 3693 MHz processor(s): Architecture=9, Level=23, Revision=6145 Processor Identifier=AMD64 Family 23 Model 24 Stepping 1, AuthenticAMD
Apr 08, 2025 14:36:19.770 [26444] INFO - Compiler is - MSVC 1929
Apr 08, 2025 14:36:19.869 [26156] ERROR - SQLITE3:0x7ff689fa54a0, 11, database corruption at line 70168 of [a29f994989]
Apr 08, 2025 14:36:19.869 [26156] ERROR - SQLITE3:0x7ff689fa54a0, 11, database disk image is malformed in "PRAGMA cache_size=2048"
Apr 08, 2025 14:36:19.870 [26156] ERROR - Promise destroyed without handling exception: Promise fell out of scope without resolving or rejecting

For the record plex starts and works fine on the ‘bad drive’, even with that bad db…

What can I do to get me back up and running without losing everything?

Thanks in advance.

[maxsteel]

I tried “.\DBRepair-Windows.ps1”: GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server databases
and it looks like it fixed the db issue, but totally decimated the com.plexapp.plugins.library.blobs.db file and upon deleting of this file, plex recreated a new one!

I was finally able to move the plex data location to the SSD drive.
everything in my plex looks fine so far…

After all this I’m just going to ask, what does the com.plexapp.plugins.library.blobs.db do exactly?

Gemini says:
com.plexapp.plugins.library.blobs.db:This specific file stores binary data (blobs) associated with your library, such as media artwork, posters, and other metadata.

Should I be concerned that it was recreated?
Will this need to be redone?
Will it do it automatically?

[maxsteel]

on a reddit forum i got an answer from Blind_Watcher:
“It mostly analysis data, which can be regenerated if needed (though it may take a while depending on the size of your library): Reddit - The heart of the internet”

[maxsteel]

in which i replied:
so fairly benign, i guess as i go along i’ll see what’s “missing”, but for the most part it looks just fine. Working a bit better on the SSD too, and no more corruption, which means backups will work again!
I’ll have to create a monitor to ensure that backups are actually being done.. if they aren’t that spells a problem! thanks!

[dbirch]

You need to replace your system drive, as it is going bad. I would not have reused any of the current databases or the files that wouldnt copy. Rather I would have fallen back on my older database backups and used one of those.

[maxsteel]

Yes, I know the drive needs swapping as I got an alarm for it. This was why I was trying to move the plex data off it. Restoring wasn’t an option, as the older DB’s did not work for whatever reason… I think it’s been solid since I kludged through it.