Recently, after a server reboot of my Plex system, it seems that the tuners are not discovered at first start of Plex. Inevitably, I notice then when a recording that I expect to have taken place isn’t recorded. At that point, a simple stop/start of Plex resolves the issue, and recordings (or tuning of LiveTV) will work.
This problem has only surfaced (relatively) recently (i.e. over the last 3-4 updates, maybe). Is anyone else experiencing anything similar? I’m unclear why the tuners wouldn’t be found initially after system reboot (usually due to Windows patches scheduled to reboot in the middle of the night), and how a simple Plex restart would resolve. Love to figure out what’s going on, as I hate missing recordings that I’ve schedule when I don’t realize that the server rebooted overnight, since all other Plex functionality works just fine, up until LiveTV tuning or a recording that needs access to the tuners.
Server Version#: 1.21.0.3711
Tuner Make/Model: 3 X HDHomeRun Dual (6 tuners total)
I am having the same problem as the user above, and I’m able to fix it by also rebooting plex. Is there any fix for this so the tuner will work after a system reboot?
Have you installed either Plex Media Server 1.21.1.3759 or Plex Media Server 1.21.1.3766 that have the fix @OttoKerner mentioned above from the Release Announcements link?
I’ve not yet, as I’ve made a conscious decision to move to the Public Server Update channel, after way too many things had been breaking in the Beta channel. Apparently even the Public channel is not fully immune to this.
The Public channel is the same releases that are in beta. The release will eventually leave beta and be available to everyone. But thought I was replying to @rdburk though.
I am now running 1.21.1.3766 and I still needed to exit and restart Plex after a system reboot, it does not appear this release fixed the problem I am having.
Yes, fully agree that they’re the same releases, though I thought that not every Beta made it to Public (i.e. multiple fixes that are in addressed in several interim Betas would eventually get swept up in a “blessed” Public release). Is that still the case?
Correct, not every beta makes it to Public availability. You can always install a beta and if you have a problem uninstall it and reinstall the last Public release. I reinstall releases fairly often as I test Alphas normally, at the moment an experimental build, on one of my servers.
Thanks, John. I recall some time back that there had been some database structure changes that made it a challenge at the time to go backwards, so after that, I just stuck with Publics to hopefully avoid such challenges. It’s good to hear that’s no longer a concern.
I concur. I just updated to .3766 as it made it to the public channel. Unfortunately, I too, after a system reboot, had to again recycle Plex to be able to get my tuners to work. When initially trying to tune a channel, I get the generic “Could not tune channel. Please check your tuner or antenna.”
Then, simply stopping and restarting the Plex service (using Plex Media Server Service 1.1.7.0), all works as expected. The only challenge is that you have to be aware of server reboots and then cycle Plex. There’s nothing wrong with the tuners or antenna, but more with Plex and somehow the HDHomeruns (in my case) not being discovered or something at initial Plex startup, but which is perfectly fine 30 seconds later when cycling the service.
If there’s any way I can provide logs, etc. to help debug, please let me know what’s needed.
Just updated to .3830 beta and still having same issue with the restart of plex fixing it. I agree, if I can provide any logs to assist, please let me know.
Same. I’ve set up a task that will notify me when the server reboots so that I can go restart Plex manually. It’d be nice if this would actually get fixed. Seems a timing/race condition/ordering condition as I’d think that a start of Plex at time of system boot is pretty similar to a restart of Plex, yet one can’t find tuners, and the other can.
