On disk, the files are getting stuck in the .grab folder:
$ -> ls -R .grab
2db440a361ae7c32dfa9622c491cb7242f953f23 97a4d0c96408ae830b1ab29fec5555271114b6ce
95ceb2ff9655372680aa10b30fd93ecad1aaa3ba
.grab/2db440a361ae7c32dfa9622c491cb7242f953f23:
Splash and Bubbles (2016) - S01E22 - Partner Pals; Ultimate Hide and Seek.ts
.grab/95ceb2ff9655372680aa10b30fd93ecad1aaa3ba:
Odd Squad (2014) - S01E03 - My Better Half; The Confalones.ts
.grab/97a4d0c96408ae830b1ab29fec5555271114b6ce:
Daniel Tiger’s Neighborhood (2012) - S03E12 - Daniel Takes His Time; Sometimes It’s Good to Go Slow.ts
I’ve tried restarting the server, which seems to make the next few recordings work, but then it reverts to this behavior. Restarting also has the side-effect of deleting everything in .grab.
I think this is a common problem? Tips on best workaround would be helpful.
I haven’t seen this issue at all. You mention that it has been happening for several weeks, so this was happening also to the ~.mkv files in the .grab folder also?
Have you checked the log file to see if it is throwing any errors.
Are you using a post-processing script?
I saw something like this when. 1.7.x was released. Some would eventually complete but all of the recordings that did this were garbage. You are probably experiencing the same thing many people are complaining about were for some reason the transcoder is having issues with some recordings with the final remux step.
@dansmith21 said:
[Running Plex Media Server 1.7.6 on Drobo]
Starting a couple of weeks ago, I’m seeing frequent failures (>50%) of my recordings.
The Recording Schedule shows the recordings stuck in a completed-but-not-ready state (see screenshot).
I think this is a common problem? Tips on best workaround would be helpful.
I am having the exact same issue OP… Just popped on this forum specifically to ask about it, glad (sort of) to see someone else already has, hope we get a fix Edit; Don’t think HDHomeRun EXTEND is the issue as im having the same issue without having this functionality.
Logs: attached (recording from 4:30-5:00 failed, logs generated at 5:28)
Your logs show the last recording was an episode of Wild Kratts from 3:30 to 4:00, which worked properly and then the logs end at about 4:28. If this really was for 4:30-5:00 and you grabbed the logs at 5:28, maybe the clock on your server is wrong.
@MovieFan.Plex said:
Your logs show the last recording was an episode of Wild Kratts from 3:30 to 4:00, which worked properly and then the logs end at about 4:28. If this really was for 4:30-5:00 and you grabbed the logs at 5:28, maybe the clock on your server is wrong.
Yes, Drobo seems to be on PDT, while my local time is MDT. Not sure this is something I can control (don’t see a setting in Drobo Dashboard…). But, anyway, that 3:30 to 4:00 PDT recording is the one I was referring to.
To be clear: the Wild Kratts recording did not actually “work properly”—it ended up stuck on a red circle with a junk file in .grab.
Your logs show the last recording was an episode of Wild Kratts from 3:30 to 4:00, which worked properly and then the logs end at about 4:28. If this really was for 4:30-5:00 and you grabbed the logs at 5:28, maybe the clock on your server is wrong.
I take that back. Rechecking your logs I do see it failed to record. There are a couple of odd things. I’ll need to check with the devs.
Same issue, just recorded a show from 8pm-9pm…at 9:30pm it still had the “full circle” indicating the recording completed…but never moved from the .grab folder. The recording itself, despite saying “complete” was in fact, only the first 20 min of the show, left in the .grab folder.
This is with version 1.7.6.4058 of Plex running in a Windows environment. The machine is fairly powerful, with a Xeon E5, and 16GB of RAM, so performance of the system should really not be an issue.
The primary boot drive where Plex and Windows 10 is installed is a SATA SSD, but the place TV is stored is a SATA 1TB 7200RPM rotational drive. The 1TB drive is used for nothing else but recording Plex created TV…
Is there ANY chance this split storage arrangement is causing any kind of trouble?
As a test, I’m adjusting the normal power management setting of “Turn off hard drive after 5 minutes” to zero minutes…JUST in case it is the local hard drive power up/power down time that is causing an issue…would that be a problem if the OS shut off the drive from a lack of use, and the time to spin up again is causing an issue? (It’s just a guess at this point).
I’d be curious if other people having this kind of recording issue on a Windows system have a single drive system that is always running the one primary drive…or a multi drive system, where the drive containing the OS and Plex are busy, but the secondary drive for programs is only busy if someone is viewing them, or if the Plex Server is recording…if all the problems are on multi drive systems, it would indicate that configuration may be causing some issues…
@“rbkirk.Plex” I doubt that the split drive configuration is your issue. I am running windows with Plex installed on a C: drive, Plex user data is stored on D drive, recordings are all done on a SSD that was replaced with current C: drive. After recordings are done mcebuddy processes the recording on the SSD and it is moved to a 4TB HDD for permanent storage.
I’d be curious if other people having this kind of recording issue on a Windows system have a single drive system that is always running the one primary drive…or a multi drive system, where the drive containing the OS and Plex are busy, but the secondary drive for programs is only busy if someone is viewing them, or if the Plex Server is recording…if all the problems are on multi drive systems, it would indicate that configuration may be causing some issues…
I experienced similar on Windows 10 - incomplete recordings stuck in grab folder… This is on 1.7.5. I switched over to a second (Synology) server running 1.5.7 for DVR Recordings and all is well with that version.
johnm_ColaSC , just curious…with your setup, are the recordings also getting “stuck”? Yours would be different in that what you describe sounds like all real processing…recording and transcoding…occur on the super fast SSD (compared to a rotational drive)…then a mere copy operation of the completed recording is moved over to the rotational drive.
My situation has the .grab folder on the rotational drive…so I’m wondering if that small initial startup…when the drive turns on after idle, and needs to spin up…is what may be causing me some lost recordings.
I’ll find out after more testing, now that the drive never stops spinning…if everything suddenly becomes more reliable with this version, then I’m going to say it’s the drive arrangement and power management that was killing it.
I have seen a few issues with other versions of 1.7.x but after updating from 1.6.1 to 1.7.6 I have not seen any hung recordings. I only had a couple, 2 or 3 max, recordings that “hung” while on other 1.7.x versions. The other issue I had with other versions of 1.7.x was not utilizing all available tuners. I could only record 2 shows at the same time on one of my Connects. I have not seen that issue with 1.7.6 either, although others on the forum are apparently still having that issue as well.
I was having the same issue. Probably 90% of my recordings were showing still recording. I deleted everything inside the grab folder and restarted plex and so far it seems to be working.
Edit; Don’t think HDHomeRun EXTEND is the issue as im having the same issue without having this functionality.