oh but it is, when I do a properties on it I normally stop it after it’s still rolling at 700, no lie, it’s annoying, I have way to much crap. I’m a Movie and TV horder!
When it comes down to it, It’ll be something real stupid on my part, that’ll be over looked and staring me right in the crack! and it’ll knock me after all this time, I’ve grown to have a lot of patience when working with it just on waiting for things to complete due to the size of the data, so a bit more time won’t hurt. and I do thank everyone for the assist.
Thanks for sharing the log files. I did not see any major problems that would stop you from updating PMS.
When you get your new glasses, please provide a directory listing of your db files. That will show their size.
Also, the next time you restart PMS, please download a new set of log files after Plex fully starts. They will have the Plex’s startup sequence.
Plex Media Server had a problem with the Windows 64-bit version not respecting custom paths when auto updating. I do not know when it first appeared, but it was fixed in 1.40.2. That might have something to do with you having to manually update Plex Media Server.
1.40.2.8273 Release Notes Fixes:
- (Auto Update) Custom install paths are not respected when auto-updating on 64 bit Windows. (PM-1143)
will do thanks
Thanks for the log files. I do not see anything that would prevent updating Plex Media Server.
Some questions/requests:
Please provide a directory listing, including file sizes, of N:\Plex-Back-up\Plex Media Server\Plex Media Server\Plug-in Support\Databases.
Is N:\ a local or network drive? If local, is it a hard drive or SSD? Is it internal or USB attached?
When you moved the Plex Data Folder from C:\ to N:\, did you follow this procedure, including making the Windows registry changes? [HowTo] An extended guide on how to move the Plex data folder on Windows
The next step is to run the DBRepair utility.
Download the utility from github: PlexDBRepair/Windows/DBRepair-Windows.bat at master · ChuckPa/PlexDBRepair · GitHub
To download, click on the button with the downward pointing arrow on the right.
Stop Plex Media Server, then, run it from a c:\ prompt. Do not double click on it.
It will create a PlexDBRepair.log file in the same directory as the database files.
Upload that log file to the thread.
Here’s an example of the output. The database files on my PC are very small, so the file runs very quickly. It will take longer on your system.
c:\Temp>DBRepair-Windows.bat
NOTE: This script is being replaced with the PowerShell script DBRepair-Windows.ps1,
which aims to better emulate DBRepair.sh (more options, interative mode, etc).
Consider moving over to the new script.
14:52:20.07 -- ====== Session begins. (Thu 09/12/2024) ======
14:52:20.29 -- Exporting Main DB
14:52:20.45 -- Exporting Blobs DB
14:52:20.50 -- Exporting Complete.
14:52:20.50 -- Creating Main DB
14:52:20.72 -- Verifying Main DB
14:52:20.78 -- Main DB verification check is: ok
14:52:20.78 -- Main DB verification successful.
14:52:20.79 -- Creating Blobs DB
14:52:20.85 -- Verifying Blobs DB
14:52:20.89 -- Blobs DB verification check is: ok
14:52:20.89 -- Blobs DB verification successful.
14:52:20.89 -- Import and verification complete.
14:52:20.90 -- Reindexing Main DB
14:52:21.07 -- Reindexing Blobs DB
14:52:21.11 -- Reindexing complete.
14:52:21.11 -- Moving current DBs to DBTMP and making new databases active
1 file(s) moved.
1 file(s) moved.
1 file(s) moved.
1 file(s) moved.
14:52:21.13 -- Database repair/rebuild/reindex completed.
14:52:21.13 -- ====== Session completed. ======
I’ve Dl’d it and ran it already, as you can see I have it in N: and I did run it through cmd, it took i think 4 hours, it didn’t accomplish anything. I’ll try it again, I did do a few repairs since then. I’ll get back to you with the Logs. I can’t find the logs, I do know it completed. maybe it error-ed out is the problem.
The log file (just one) will be in the same folder as the database files.
It has the same info that is displayed in the CMD window while running the utility.
It is OK, even better, if it does not find any problems.
The goal is to optimize the database and DBRepair does a better job than choosing “Optimize” in Plex Media Server.
Next question: Do you have Microsoft PowerShell installed?
If not, please install it.
See Installing PowerShell on Windows - PowerShell | Microsoft Learn.
I used the “winget” steps to install it on my Win10 PC.
This will let you view the Plex log files in real time (mentioned in an earlier post above).
i’m working on it, it’s currently giving me an issue atm,
I’m in my Dir. and everything I do is giving me “is not recognized as an internal or external command”
Do you have something like a snapshot of your PLEX database around the time you first installed Version 1.32.7.7571? If so take a current snapshot (or windows backup), then revert to the earliest snapshot for v1.32.7.7571 and try to upgrade that to version 1.40.1.8227 (which makes changes to the database). Haven’t looked at the logs but seems your database is the issue even though you ran DBrepair. If the upgrade works than you can make the hard choice of deciding if the tradeoff is worth it (since you will have lost likely months worth of data from your database, but still better than starting from scratch).
Actually I do, I have logs for days
NVM … i got it done myself… 
How did it turn out? And have you began the upgrade process?
The next step, after running DBRepair and installing PowerShell, is to update Plex Media Server.
Plex will make a lot of database changes which will take some time, possibly hours, to finish, and Plex Media Server will be offline while the database updates.
Also, there is no progress indicator for the migration.
Many people think something has gone wrong and stop Plex before the migration has finished. When Plex is restarted, it starts the migration again from the beginning.
You can use the get-content command in PowerShell to watch the activity in Plex Media Server.log.
If you see activity in the log file, then the migration is still occurring.
It is a substitute for lack of a progress indicator.
1 Like
PlexDBRepair.log (884 Bytes)
Not long at all this time
i’m going to try and see if the update prior to the current will work 1st now
Update… Big Negative, Still unable to open Library Error,
I’ll reboot the system and see if it’ll make a difference.
Rats.
Did you choose the Download Updates button in Settings → General or did you download the installer from plex.tv and run it manually?
If you used the Download Updates button, try the manual installation.
If it still fails, upload the log files. Let’s see if they show anything.
I always DL it and do a Manual install.
