Confusing results with .PS1 windows build
Closed this issue · 6 comments
A user in the Plex forums
Ref: https://forums.plex.tv/t/plexdbrepair-development/822684/476
Reports he has corrupt databases but DBRepair returns clean
ALSO, "4" is not a command ?
User logs:
2024-06-14 22.02.27 -- ============================================================
2024-06-14 22.02.27 -- Session start: Host is Windows 10 (Build 19045)
2024-06-14 22.02.37 -- Stop - START
2024-06-14 22.02.41 -- Auto - START
2024-06-14 22.24.33 -- Repair - Export databases - PASS
2024-06-14 22.27.31 -- Repair - Import - PASS
2024-06-14 22.27.38 -- Repair - Verify main database - PASS
2024-06-14 22.27.38 -- Repair - Verify blobs database - PASS
2024-06-14 22.27.38 -- Reindexing Main DB
2024-06-14 22.27.41 -- Reindexing Blobs DB
2024-06-14 22.27.41 -- Reindexing complete.
2024-06-14 22.27.41 -- Moving current DBs to DBTMP and making new databases active
2024-06-14 22.27.41 -- Auto - PASS
2024-06-14 22.30.49 -- Exit - Retain temp files.
2024-06-14 22.30.49 -- Session end. 06/14/2024 22:30:49
2024-06-14 22.30.49 -- ============================================================
2024-06-14 22.32.38 -- ============================================================
2024-06-14 22.32.38 -- Session start: Host is Windows 10 (Build 19045)
2024-06-14 22.32.41 -- Stop - START
2024-06-14 22.32.59 -- Auto - START
2024-06-14 22.33.23 -- Repair - Export databases - PASS
2024-06-14 22.33.36 -- Repair - Import - PASS
2024-06-14 22.33.40 -- Repair - Verify main database - PASS
2024-06-14 22.33.40 -- Repair - Verify blobs database - PASS
2024-06-14 22.33.40 -- Reindexing Main DB
2024-06-14 22.33.43 -- Reindexing Blobs DB
2024-06-14 22.33.43 -- Reindexing complete.
2024-06-14 22.33.43 -- Moving current DBs to DBTMP and making new databases active
2024-06-14 22.33.43 -- Auto - PASS
2024-06-14 22.35.18 -- Start - START
2024-06-14 22.35.18 -- Start - PASS
2024-06-14 22.37.23 -- Unknown command: '4'
2024-06-14 22.38.11 -- Auto - START
2024-06-14 22.38.36 -- Repair - Export databases - PASS
2024-06-14 22.38.50 -- Repair - Import - PASS
2024-06-14 22.38.54 -- Repair - Verify main database - PASS
2024-06-14 22.38.54 -- Repair - Verify blobs database - PASS
2024-06-14 22.38.54 -- Reindexing Main DB
2024-06-14 22.38.57 -- Reindexing Blobs DB
2024-06-14 22.38.57 -- Reindexing complete.
2024-06-14 22.38.57 -- Moving current DBs to DBTMP and making new databases active
2024-06-14 22.38.57 -- Auto - PASS
2024-06-14 22.39.10 -- Exit - Retain temp files.
2024-06-14 22.39.10 -- Session end. 06/14/2024 22:39:10
2024-06-14 22.39.10 -- ============================================================
Might you consider jumping into the forum and grabbing that?
I'm out of town and mobile-only for the next few days, but I should be able to take a look early next week. As for, "unknown command 4", the Powershell script currently only supports a small subset of commands (start/stop, auto, and prune IIRC), so '4' isn't supported right now. I want to extend the functionality at some point, but don't know when I'll have enough free cycles to take a look.
Sorry, this completely fell off my radar. I've reached out to the forum user via PM to see if they're still having issues.
@ChuckPa - I haven't heard anything back from the user (and from the forum thread, it sounds like their initial issue isn't something that DBRepair can fix). If the ask here is to implement more individual options like '4', I can look into that, but I can't promise any timelines.
Given no feedback from the user, I suspect it's now OBE?
On that basis, closing this unless a reason to reopen
If you get a chance, might you look into option 4 when time is available?
Thanks.