and am I right in saying that this has no real impact other than the confusing error message in the DVR Schedule ?
Yes so far, its just a confusing error. I haven’t noticed any issues as a result of it.
Its the OSX Plex app and Yes its in the DVR Schedule. Also web app shows the same thing.
Thank you. I see that it was a roku live tv session that stopped requesting segments at 21:24:05 and PMS timed it out as an idle session at 21:27:06 - 3 minutes after seeing the last request
Plex Media Server 1.18.6.2348 is now out as beta
It has fixes for the deletions of DVR recordings .grab directories by other servers sharing same media paths in libraries.
- (DVR) Fix for in-progress recordings being deleted by another server that records to the same directory. (#10929)
See release note for other changes
This should resolve the problem for most users. There are still other causes being investigated with diagnostics provided by @David-Plex-DiskStation
2 Likes
WooHoo! Looks like it’s working so far! Have library scans turned back on. Thanks @sa2000
1 Like
I believe in some cases, it doesn’t detect that a client has disconnected for whatever reason. Theres no session in the transcode directory for whatever it thinks its recording, which makes the error make sense, when it cant move recorded media to destination… Theres nothing to move. I don’t know what triggers PMS to finally realize that the client is long gone.
I am running 1.18.6.2348. I have turned off indexing on both Win10 computers and I am only trying to get recordings completed on the Diskstation. But I am still getting the Could not move Recorded Media to Destination error. I can restart the PMS service on the Diskstation and it will correct the problem for 8-12 hours. But it comes back and stays until I restart the service again. I will upload my logs.
1 Like
I’ve got the same issue on 1.18.6.2368 running on Synology DS418play. Installing the beta version seems to have made the problem worse with 11/12 recordings failing whereas before I was getting about 50-50.
1 Like
@sa2000 - Do you know if engineering is working on any update for this? I have just gotten in the routine of restarting the service before I go to bed and when I got home from work… but it is consistently failing.
The issue that you have is different from the one where other servers were deleting the recording files. So to progress from now on, I only need logs from the server itself that is doing the recordings
We still have a problem with the logs not showing the times when the recordings started.
The problem appears to be - double post processing. In fact there is evidence also of double recording of the same episode on two different tuners. We need to establish how that is arising. This means we need to see the logs before the recordings start and covering the time when the recordings do start and then later logs covering the failure
If you can predict a failure - you collect logs just after recordings actually start - say 5 minutes after start and then collect logs again when the comskip and post processing finishes and the error arises.
The logs at the moment are covering only 30 minutes - if the recording is of a 30 minute episode, the logs need to cover about an hour min to see the logs prior to the start of recording and afterwards the post processing
You could also increase the number of log files - say to 20 and then hopefully one set of logs would cover the start as well as the failure
See LogNumFiles advanced preference - https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/
See my response above Could Not move recorded media to destination - #195 by sa2000
For server logs
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Updating fixed mine, currently on 1.18.6.2368 for both of my servers. Thank you!
Server Version 1.18.7.2415
Just started getting this error on multiple recordings, different drives, all have plenty of space.
@sa2000,
I uploaded 5 sets of logs about every 35 minutes in a message to you
7:13 PM
7:51 PM
8:25 PM
Reset the PMS service on Diskstation
8:58 PM
9:30 PM
As usual, after the reset, the multi-tuner recordings stopped and the errors stopped. I will try and watch how long that lasts before it starts erroring again. If there is a positive, it only had one error every 6-8 recordings before I reset it.
I only have one server running. I updated to the new software yesterday 1.18.7.2434, i got the same issues as above. (The destination library or location does not exist) I had 3 x 1TB drives and i just bought an 8TB drive. I have moved everything over to the new 8TB drive. Deleted the DVR completely and reinstalled the DVR. I have a show recording tonight at 11:30 Central Time. I will see if it finds its way to the DVR recorded folder.
Just had this happen to me for the first time. I have locally mounted drives. Had set the destination of the recording to /mnt/a/tv. Received “could not move recorded media to destination”. Running server version 1.18.7.2415.
When you spot the source of errors, it’s really helpful to grab the PMS logs as soon as possible and post them here. Also posting the Plex media server version number is helpful.
Added the server version. I’ll grab the logs next time I see it.
1 Like
Things seem to be working well for me now days with the 2 server issue. I just wanted to say thank you to you and please pass along my thanks to the Plex team. It’s great software and it’s exciting to see it improve all the time.
Thanks again,
Wes
1 Like
