Skip to content

Menu: Check

ChuckPa edited this page Oct 16, 2026 · 1 revision
  • CHECk - (Option 3): Check Both Databases to Determine Current Status and Repairs/Optimizations Needed, If Any
    • Overview: Diagnoses the health of the main and blobs databases without modifying anything. A check covers several independent conditions:

      • Structural damage — SQLite-level integrity failures or missing schema objects (tables/indexes/triggers DBRepair can later recreate)
      • Abandoned recovery tables — tables left behind by an earlier SQLite .recover attempt made outside DBRepair. Check reports how many it found and marks the database damaged. DBRepair cleans up these residual structures and then repairs the database(s) (see Repair).
      • Search index damage — the FTS (Full-Text Search) indexes can become corrupted even when the database otherwise passes a basic integrity check, which can surface as "database disk image is malformed" errors when adding items to collections, updating metadata, or text searches fail. If this is reported, use Repair (see Repair) or Automatic (see Automatic); both rebuild the search indexes and repopulate them.
      • Fragmentation — the ratio of free (unused) pages to total pages in the file; over roughly 3% is flagged as fragmented.
      • Bloat — an accumulation of orphaned statistics_bandwidth rows in the main database (see Deflate). PMS databases perform the best under 3% fragmentation.
      • Unrecoverable damage — SQLite internal data tables are unreadable. This is the one condition Repair cannot fix; DBRepair will tell you to use Replace instead.
    • Availability: Runs only when Plex Media Server is stopped.

    • Safety status: Safe — read-only.


Back

Clone this wiki locally