server 2022 (VM)
redirected plex data to d:
ran PlexMediaServer-1.28.1.6018-c1f308c6a-x86_64. this removed the x32 and installed x64 as expected but it wont launch with corrupt database message.
plex media server was unable to open its media database.
will roll back to 32bit now to see if resolved.
- Roll back
- repair database Repair a Corrupted Database | Plex Support
(alternatively, restore a backup and then repair it anyway Restore a Database Backed Up via 'Scheduled Tasks' | Plex Support ) - repeat the 64 bit installation but give it plenty of time upon first startup to perform any database conversions
Thanks. None worked unfortunately.
Restored database from local and remote backup, multiple versions still the same corrupt message. Might have to try server restore.
Fresh profile did work with x64 so is running fine, just something with my data and relocating appdata to another disk it seems. Will keep digging.
Hello,
Will the 64bit updated server version be located on the downloads page with the 32bit version or will it only be located in the forums? Sometimes Plex Server updates and sometimes I have to manually update to the latest version. I donāt mind manually updating if I can find the latest 64bit version.
This is a preview version. Thatās why it is currently only available here.
Once it has been tested enough to be deemed āstableā, it will be available via the Download links below, just like all other downloads.
1 Like
Unless Iāve been hamstringing myself by doing in-place upgrades for years, my Plex metadata directory is now well over 1m files, many of them incredibly small in size. If I do a file backup it takes well over 24hrs to enumerate and compress all the files, and this is from RAIDed SSDs in my home server, not to mention the space wastage due to sector sizes. Once you get to that many files it becomes quite substantial. The thought was all such data being put into blob storage would be nearly as quick, or quicker, RAM allowing, while saving space. It would also streamline backups.
Again, presuming this isnāt all just my own fault.
Just FYI, this is not normal. I run this PowerShell backup script which 7zips all of my Plex stuff in roughly 30 minutes. I just checked and itās a bit short of a million files, but even if you doubled it thatās still only an hour.
Editā¦ I Figured out the issue. I had updated to the latest Intel driver the one Intel recommended. I reverted back to the one MSI recommended and it is working again.
Has anyone else had an issue where no media will HW transcode for more than about 10 seconds before reverting back to CPU transcoding. Running WIN11 Plex 64 version1.28.1.6041. on a I7-12700K . HW transcoding was perfect on the x86 Plex but daily crashes. No crashes on this new x64 but will not HW transcode.
Plex Media Server Logs_2022-08-10_16-05-26.zip (989.3 KB)
Just wondering what the minimum requirements are for the x64 bit version going forward will be. When trying to upgrade pms to 1.25.1.6041 on a server 2008r2 system, I received this message.
Thanks,
Michael
From your log.
Aug 10, 2022 16:04:52.487 [8356] ERROR - [Req#2bd/Transcode/b3b4367b92e46313-com-plexapp-android/012aeaa6-55c0-4482-b87c-e59637d653a7] [h264_qsv @ 0000025c17bd4040] Error during encoding: device failed (-17)
So the hardware is failing for some reason. This is quicksync so maybe still a driver issue.
What Windows are you running?
Edit: Found some info on this. Please see the bottom of the OP.
Edit 2: Just noticed you said Server 2008r2. That is based on Windows 7, which is why you cannot install this.
Thanks for the info, I will be upgrading my system in the near future.
Michael
Iāll take a look, thanks. Really, I only run a manual/zip backup once in a blue moon, only when I might be doing something stupid, or Iām migrating to another box or something. The whole server is backed up if I need an emergency recovery.
Solving a super-long backup time is a good thing, but still; a million files for one app? I still think there are better ways of storing data.
1 Like
Is there a download link for the latest 64 bit build? I clicked skip this version accidentally in Plex Web on the update screen.
The link for Version 1.28.1.6018 is in the first postā¦
I have that as latest x64 version - nothing newerā¦
1.25.1.6041 Is current.
For the 32 Bit yesā¦
I didnāt get any offer to download that version for 64 Bit yet so I donāt think itās out yetā¦
We will see if anyone from Plex can tell us thatā¦
I went to the page within Plex and checked for any updates and still getting the message that Iām using the current oneā¦
I constructed me the link myself
https://artifacts.plex.tv/plex-media-server-beta/1.28.1.6041-738907df3/windows/PlexMediaServer-1.28.1.6041-738907df3-x86_64.exe
And seems that you are right - this can be downloadedā¦
I updated to Version 1.28.1.6041 and I am now experiencing remote access failures on the standard port (32400) . It is acting like a double NAT or perhaps firewall blockage. Investigating
Edit: Not a NAT problem, and the port is allowed through McAfee firewall. When remote access is enabled it will fail between 0 seconds and to this point 10 minutes. This is with the port automatically assigned. Next step is testing the manually specified port port setting. The automatic setting DID NOT correctly set the public port.
Edit 2: The manually specified port port setting did not resolve the remote access problem. Remote access is failing between 1 - 4 minutes.
The varying time of the failures belies saying its firewall shortfalls it would be more regular if it was. Remote access times remain, but every time I go to Settings>>General>> and check for updates it almost immediately fails.
Edit 3: Both the automatic and manually specified public port setting fail from 1-4 minutes and checking for updates causes it to immediately fail (1-10 seconds). Frustrating.
Side Note: It appears PLEX is now continually scanning my photo library. It is not a scheduled task, nor have there been changes. (a restart of the server corrected this)
Final Edit: Shut down the server, went to task manager (WIN 11) and killed all the PLEX services and processes. Restarted the server and remote access has been stable for the last 20 minutes or so. If the problems reemerge Iāll place it in a separate comment
Iām getting some weird ram issues with this build.
It goes from a few hundred MBs of ram use to fully maxing out my serverās ram(12GB) then goes back down to a few hundred MBs. Repeat cycle.
Is this an expected behaviour?
