Yes and Yes.
I will need to see the client app logs ā but this really isnāt the appropriate place to resolve.
It really sounds like you have a problem with the phone app
Iām the server guy. (Linux).
I will try but this is purely hit or miss.
Because this isnāt reallly a server problem, Would you mind creating a new thread, more appropriately titled, and then ping me ? ( @ChuckPa ) so I will be notified?
Weāll continue there.
Did it take a while for your server to be reachable again? I updated earlier and my server wasnāt reachable so I went back to previous version and after a few minutes the server appeared again.
I decided to try the upgrade again and be a bit more patient but itās been nearly half an hour now and itās still unreachable. DSM says Plex is running, but when I try and open Plex from within Package Manager, it says itās unable to connect. My NAS is a DS213j so not the fastest and sometimes my server is unreachable when itās doing things like scanning the library. Could it be doing something like that with this new update and I just need to be patient or might something have broken?
EDIT: Ok, itās now appeared but that took more than half an hour. Worth knowing if anyone else finds themselves waiting a while.
It took me 2-5 minutes to reach the server.
@timtoo440 As stated in the upgrade documentation it can take a few minutes for the library to upgrade. I think it also depends on how big your library is and how fast your NAS is. For me it only took 2 minutes at most. Glad it works now!
To all here:
Please note that due to some particularly large database migrations, your first time starting up the server with this release may take an unusually long time, depending on library size, disk speed, and CPU performance. This is normal.
I have an i7-7700 w/ 64GB of RAM and 27,000 items indexed.
It required almost 4 minutes to complete the migrations.
Thanks, everyone. I should read the release notes!
And it might be time to update my NASā¦
Hi, today I have a notification with new release (iām on āPublicā channel since DSM7) named : PlexMediaServer-1.22.1.4228-724c56e62-x86_64_DSM7
On the thread for DSM7 latest version is : PlexMediaServer-1.22.0.4163-d8c4875dd-x86_64_DSM7
Can I install the one released by Plex or not ? iām running 1.22.0.4163-7000
There are problems with HW transcoding and PMS 1.22.1.4228
You might be better served staying where youāre at for the interrim.
Iām advising the Linux users to step back until it is (if their PMS is critical path)
Piping in late, I know, but I just want to add my BIG THANK YOU to @ChuckPa and everyone else who got Plex under DSM7 beta working straight out of the downloads page!
You rock
guys ![]()
As we get closer to archiving this phase of the effort,
Iād like to ask one thing:
Howās the multi-language support ?
Iāve had feedback from a few but curious about the others.
I have a couple of movies with multiple audio selectable tracks, no issue when playing back either track. Thanks for all the work everyone put in. I have a DS216+ & it is running flawlessly with v .4163. Am looking forward to updating again to latest version later tonight. TV shows, Music & Movies all great.
When you upgrade to 4264, be aware the database schema will change.
Depending on the type of media you have indexed, it may take longer to migrate than normal.
For some users, myself included, several minutes might be required.
Do no panic. Let it finish normally.
PMS will start responding normally when the CPU time returns to its normal near-idle level.
Side Note:
Iāve started writing Backup & Restore.
I have one word to say at this point: āOUCH!ā ![]()
I am currently having problems with my hard drives and would like to back up Plex as I may have to reset the entire system.
how do i proceed?
Given I have not completed the Backup/Restore yet, you will need a scheduled task to do this:
- Type: User script
- Run as: root
- Assume: you still have the Plex shared folder (but can edit appropriately)
- Required: Plex installed but stopped
- Advised: Have it send you notification when complete if a large library
Script contents
#!/bin/sh
#
# Destination (set accordingly)
Destination="/volume1/Plex"
# Backup Plex (DSM 7)
cd /var/packages/PlexMediaServer/home
# Do it
tar cf "$Destination/PlexMediaServer-Backup.tar" ./*
The problem is, the disks are write-protected.
So can i export the files to another Location in the Network?
I also got no rights to the /home folder and canāt change them because the write-protection.
Mount the remote location
change āDestinationā to point to that remote mount point
Iāve got it now. How exactly do I have to proceed if I have re-installed the Nas and want to install Plex?
What part of that did not work?
What Iāve provided works at the Linux level (below DSM)
What did it report in the job output?
If you are comfortable at the command line, you can also
- SSH into the Synoogy
-
sudo -su root(elevated the shell to higher thanadmin) - Now start typing
Example:
# mount 192.168.0.10:/export/some/place/safe /mnt
# cd /var/packages/PlexMediaServer/home
# tar cf /mnt/PlexBackup.tar ./*