What exactly do you mean with “PMS files”?
The executables of Plex server?
The Plex data folder?
The media files?
The data folder.
%LOCALAPPDATA%\Plex Media Server
I tried fix match and issue persists:
[Req#1c6] SQLITE3:0x27d46574, 267, statement aborts at 60: [insert into tags (parent_id,metadata_item_id,tag,key,tag_type,tag_value,user_thumb_url,user_art_url,user_music_url,created_at,updated_at,extra_data) values (:tags_parent_id,:tags_metad
[Req#1c6] Exception inside transaction (inside=1) (E:\jenkins\server\3582595338\Library\Tag.cpp:224): sqlite3_statement_backend::loadOne: database disk image is malformed
[Req#1c6] Exception inside transaction (inside=1) (E:\jenkins\server\3582595338\Library\MetadataItem.cpp:7525): sqlite3_statement_backend::loadOne: database disk image is malformed
[Req#1c6] Activity: Ended activity 8ff24abe-afe7-43b9-a865-3579c939cec6.
Thread: Uncaught exception running async task which was spawned by thread 10312: sqlite3_statement_backend::loadOne: database disk image is malformed
How do I proceed?
Note, PRAGMA integrity_check; didn’t show any problems.
I went ahead and tried VACUUM; to rebuild database structure. This didn’t fix.
I went ahead and tried REINDEX; to rebuild indexes. This also didn’t fix.
A VACUUM doesn’t rebuild the DB structure. All it does is actually freeing storage space that has previously been marked as “deleted”. (similarly to a hard disk defragmentation process)
Only the procedure that’s headlined as “Low-level database recovery” is able to (maybe) repair DB damage.
I did the low-level recovery, and the results are the same. database disk image is still malformed. Where do I go from here?
(Re windows crashing issue, I will advise if it happens again in the next few days)
Do the low level recovery with the database file com.plexapp.plugins.library.blobs.db as well.
If you have a DVR in Plex, delete the files which are named like
tv.plex.providers.epg.cloud-xxxxxxxx...
(with xxxxxx being some looong hexadecimal number)
I did that just now. Unfortunately fixing match is still causing errors indicating database disk image is still malformed.
What would you suggest I try next?
Then I’m afraid you need to pronounce the db file as un-fixable.
Which means starting over for the whole server.
Thanks for the prompt response. It is very unfortunate that I have had to start over my PMS server almost on a yearly basis, especially given the volume of content on it. It is quite a pain. What would you recommend that I can do to avoid potential issues like this?
With a very large server/collection
- use a dedicated hard drive/SSD for the Plex data folder
- give the server plenty of RAM
- use the 64 bit server edition which can help overcome restrictions which can occur with very large numbers of media
- secure the server machine and its data from mechanical shocks (i.e. use a proper case or maybe even a computer rack instead of open “workbench-style” machine
- use an over-dimensioned cooling solution. Take into account a large server load during the hottest days of the summer.
- put an uninterruptible power source (UPS) on your server (and NAS, if used) to prevent data corruption in case of a power interruption or “brown-out”
- monitor the free space on the volume with the plex data folder so it never runs out of space
(The last two points are the main source of database corruption.)
Thanks for the tips. Only thing I’m missing is a UPS.
Until early this year, I repeatedly ran PMS on Ubuntu, and decided to move to Windows for potentially more stability. Sad to see Windows somehow still failed.
Since I’ll have to start over, would you recommend Windows or ubuntu or something else?
I always recommend users to stick with the OS they are comfortable with.
Running Linux is of no use if you are not able to solve everyday issues, like mounting drives with the right permissions etc.
If you have plenty of Linux experience, by all means go with it. At least it allows you to run the server headless, with Plex running as a daemon and still be able to use hardware transcoding.
(which is not possible on Windows)
Done and sent!
Can you please tell us how to determine if we have a 32 bit or 64 bit server version installed?
@Explorer_200 Got the latest logs. I’m not seeing the memory error this time and the amount of memory used prior to the crash is very low so it might not be a memory issue.
Can you try upgrading to the latest beta 1.29.0? There is a fix related to accessing the database, which is needed when doing a clean bundle, so it might be related.
@Smokindog Couple of different ways.
- Check where PMS is installed. 32-bit goes into
Program Files (x86) - Task manager will show 32-bit or 64-bit
- first line of your server log
The 64-bit version is new an you will only have the 64-bit if you installed it manually.
Just upgraded to Version 1.29.0.6209 (beta)
Ran “Clean Bundles”
Crash…
New Logs attached:
Plex Media Server Logs_2022-09-15_11-02-57.zip (1.3 MB)
@Explorer_200 Thanks. Still not sure what’s going on. I’ll let you know if I need any more info.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
