OK, Thought Id give it a go, so here is my problem, I can not give my logs for reasons below.
Loaded the new Update to give it a try, I’m On a Win 10 Pro. 64.B.
Waited for the full library to do its update did a reboot, and plex just pops on and then pops off, I can see it stay in the sys-tray for about 20 seconds before it goes offline, so I can’t access anything to even get a log file so there is nothing I can do other than go back to 7089 which seems to be the only Ver. that seems to work for me. any suggestions?
TIA.
Try the .bat file from this project: GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server databases
It will perform a thorough repair of your database file(s).
To do this, it needs plenty of free space on drive C: So verify, that there is.
After the repair was successful, try upgrading again. Keep in mind that it may need quite a while upon the first start.
(If you have FTP server or Torrent client apps on your computer, make sure they are not running when starting Plex server.)
I don’t run On :C I read the Thread you guys had with the other post, was long and tedious, I did get Ver. 7571 to load up and work when it didn’t work before, which that is a plus, I’ll try the DB repair but like the other guy I’m sitting on a half a petabyte of data as well, spread out over 25 drives, which I’m really not in the mood to redo my server anytime soon, I know the issue with not running on :C but with this big of a DB I don’t have the room on C to cover the NFO file this is why I changed to a standalone drive just for PMS, and I know how long it may take, I’ve waiting on shark to do data findings for 3 days so I’m patient.
I am not talking about the amount of media files, but only the amount of data in your plex data folder.
If you have moved that to another drive: good. It doesn’t change anything about the rest of my recommendations.
I am not sure what that means.
Wireshark, and yes my data folder is quite large, so it’ll take some time to scan/repair which I hope it will do. Thanks for the assist.
I don’t see how Wireshark would help in diagnosing a Plex DB issue.
No, it was in reference to patience lol, nothing to do with DB, I had a issue awhile back with a network problem had to run it for like 2 days to watch my network for some BS crap it was a nightmare, turned out to be bad cable lines…
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
