This is a PMS issue. Hacking the DB won’t resolve the problem.
I’ve chatted with FordGuy who will take to Plex.
Notice the specific indexes which now show failed on 1.42.2
Checking the PMS databases
Check complete. PMS main database is OK.
Check complete. PMS blobs database is OK.
Checking FTS (Full-Text Search) indexes
DEBUG: Status = Error: stepping, database disk image is malformed (11)
FTS index 'fts4_metadata_titles' - DAMAGED
Error: Error: stepping, database disk image is malformed (11)
DEBUG: Status = Error: stepping, database disk image is malformed (11)
FTS index 'fts4_metadata_titles_icu' - DAMAGED
Error: Error: stepping, database disk image is malformed (11)
DEBUG: Status = Error: stepping, database disk image is malformed (11)
FTS index 'fts4_tag_titles' - DAMAGED
Error: Error: stepping, database disk image is malformed (11)
DEBUG: Status = Error: stepping, database disk image is malformed (11)
FTS index 'fts4_tag_titles_icu' - DAMAGED
Error: Error: stepping, database disk image is malformed (11)
FTS index 'fts4_metadata_titles' (blobs) - OK
FTS index 'fts4_metadata_titles_icu' (blobs) - OK
FTS index 'fts4_tag_titles' (blobs) - OK
FTS index 'fts4_tag_titles_icu' (blobs) - OK
FTS integrity check complete. One or more FTS indexes are DAMAGED.
Use 'reindex' command (option 6) or 'automatic' (option 2) to rebuild.
NOTE: FTS indexes are damaged but main database structure is OK.
Use 'reindex' (option 6) or 'automatic' (option 2) to rebuild.
Not sure that I’d call it hacking the Database by having the Plex Sqlite remove the “bad” FTS Tables and have Plex reload them.
DBRepair reports no errors now.
Seriously, what in what I posted do you see as hacking the db?
Delete the SHM / WAL. — which is anything not committed to the DB file
– you don’t know which records are in and which aren’t. Metadata can easy get ouit of sync
Please understand, my opinion doesn’t matter anymore.
If DBRepair is doing the wrong thing, I’ll fix what I can or just remove the FTS code entirely. It was added recently to address problems with Collections and Playlists. If it’s doing more harm then good — It’s outta there.
Your opinion DOES matter.
I knew when I first posted this issue that it was a Plex Issue (not DBRepair) and IIRC, said so. The FTL code is useful as it identified a PLEX problem in my database that I didn’t know existed, that you made the Plex Team aware of.
Deleting the SHM / WAL was not necessary for me as it’s “gone” with sudo systemctl stop plexmediaserver (I debated leaving that out of my write-up)
Having had a look at the sqlite3 docs a bit regarding how the integrity check of the FTS4 tables is being done in DBrepair.sh, I found this:
(See section 7.3)
That section outlines the means by which an integrity check is performed on a virtual table (e.g. the ‘fts4’ tables in the PMS DBs). The failure modes are described. The second one is:
Using the FTS4 content option and failing to manually keep the content in sync with the FTS4 inverted indices.
I’m guessing that’s the failure mode being triggered. I assume that the database is reindexed occasionally as part of normal PMS background maintenance activities, but there are times when the metadata_items (from which fts4_metadata_titles is created) and fts4_metadata_titles become out of sync.
Any failure of the table integrity check returns a SQLITE_CORRUPT error, regardless of the failure mode (even if the database isn’t really corrupt).
This is mostly supposition, based on the docs (and how the fts4 virtual tables are created).
It’s interesting reading. I’d recommend reading the intro to section 7, plus the sections for the ‘integrity-check’ and ‘rebuild’ commands, for anyone interested.
For what it’s worth, here’s how the fts4_metadata_titles table is created in the PMS DB schema:
CREATE VIRTUAL TABLE fts4_metadata_titles USING fts4(content=‘metadata_items’, title, title_sort, original_title)
So, it’s populated from the title, title_sort, and original_title columns of the metadata_items table.
While no errors yesterday (tested more than a few times), this morning the errors returned.
As @ChuckPa has said “This is a PMS issue. I’ve chatted with FordGuy who will take to Plex.” I’ll just have to wait and see if Plex fixes this issue.
Checking FTS (Full-Text Search) indexes
FTS index ‘fts4_metadata_titles_icu’ - DAMAGED
Error: Error: stepping, database disk image is malformed (11)
FTS index ‘fts4_tag_titles_icu’ - DAMAGED
Error: Error: stepping, database disk image is malformed (11)
FTS index ‘fts4_metadata_titles_icu’ (blobs) - OK
FTS index ‘fts4_tag_titles_icu’ (blobs) - OK
FTS integrity check complete. One or more FTS indexes are DAMAGED.
Use ‘reindex’ command (option 6) or ‘automatic’ (option 2) to rebuild.
No external dependencies (Runtime libraries - Static linked))
– It’ll run anywhere PMS can be installed
If it doesn’t look totally cheesy, it’ll have a TUI interface.
– Function key or Letter key input in interactive mode
– Popup windows in the main display area
For those of you who remember the old DOS days and “Norton SpeedDisk”,
It’ll look like that but the graphics characters are so much better now.
I’ll have the MacOS version first (ARMv8) then will do the CLANG cross-compile to other platforms. (CLANG21).
The source is much cleaner now. 3200 lines and counting but compiled is less than the 70 KB DBRepair.sh is.
I’ll keep everyone updated as I get closer to needing help testing.
I don’t know if it will cross-compile to Windows but if it will then. YES
NOTE:
Yes, Clang 21 will cross-compile to Windows 11. Clang/LLVM is designed as a native cross-compiler, meaning a single installation can target different operating systems and architectures (x86_64 or ARM64) by specifying the target triple.
[image]mcilloni.ovh +3
While earlier versions already supported this, Clang 21 will continue to support targeting Windows 11 (MSVC ABI) from host environments like Linux, macOS, or other Windows systems.
GitHub +1
I’ll only need pathname / configuration detection info so it knows where to look on a Windows machine.
DBRepair.sh seems to work fine in my environment (macOS 15.7.4, PMS 1.41.1.10611). I didn’t test all functions, but stop, start, check, automatic, status, and exit all work as expected.
Yes, but you’ll need to go old-school (using a symbolic link from the expected/normal location to the real location).
~/Library/Application Support/Plex Media Server —> /Volumes/DisposableSSD/Plex Media Server.
I actually did this for a while and it worked fine (I’ve not redirected my Plex data folder this way in a while though).
.
