Slugger
03-17-2011, 09:06 PM
Fiddling around in the office today and had to move one of my HD receivers, the one connected to my HDPVR. Tonight recordings start and all is good until 21:30 - the first scheduled recording on the HDPVR. Immediately the HDPVR fails and all hell breaks loose...
System messages popping up left and right about the HDPVR not producing output, reset attempts failed. Ok, but this also caused the Colossus to eventually fail shortly after (when it was recording fine). SageTV became non responsive and I eventually had to reboot the entire system.
As it turns out, it seems the problem is that while moving the one STB around today I accidentally unplugged one of the 3 component connections on the back so only two were connected. So when the HDPVR tried to start recording I'm guessing the signal was no good and Sage and/or the drivers didn't like the partial component connection. Once I fixed the connection and gave the server a reboot I seem to be back to normal operation (I'm obviously keeping a close eye on things this evening now).
My concerns: One failed tuner (the HDPVR) basically brought Sage to its knees. The failed HDPVR caused the Colossus to fail and made the Sage service hang to the point where I couldn't even kill it from task manager. Not sure where the problem lies (Sage, drivers, both?), but I'd like to think Sage could recover a little more gracefully from a failed tuner. I don't really expect it to reset the HDPVR (especially given this particular failure), but I would expect it to stop trying to use it and allow the other tuners to keep doing their thing (and certainly not make the system so unstable that the other tuner eventually fails as well).
I'm pretty sure I know how to reproduce this, but I have no intentions on doing it again. :) Basically configure a Colossus and an HDPVR. After you setup the sources, disconnect one of the 3 component cables from the HDPVR. First time Sage tries to record from HDPVR you should get this scenario.
System messages popping up left and right about the HDPVR not producing output, reset attempts failed. Ok, but this also caused the Colossus to eventually fail shortly after (when it was recording fine). SageTV became non responsive and I eventually had to reboot the entire system.
As it turns out, it seems the problem is that while moving the one STB around today I accidentally unplugged one of the 3 component connections on the back so only two were connected. So when the HDPVR tried to start recording I'm guessing the signal was no good and Sage and/or the drivers didn't like the partial component connection. Once I fixed the connection and gave the server a reboot I seem to be back to normal operation (I'm obviously keeping a close eye on things this evening now).
My concerns: One failed tuner (the HDPVR) basically brought Sage to its knees. The failed HDPVR caused the Colossus to fail and made the Sage service hang to the point where I couldn't even kill it from task manager. Not sure where the problem lies (Sage, drivers, both?), but I'd like to think Sage could recover a little more gracefully from a failed tuner. I don't really expect it to reset the HDPVR (especially given this particular failure), but I would expect it to stop trying to use it and allow the other tuners to keep doing their thing (and certainly not make the system so unstable that the other tuner eventually fails as well).
I'm pretty sure I know how to reproduce this, but I have no intentions on doing it again. :) Basically configure a Colossus and an HDPVR. After you setup the sources, disconnect one of the 3 component cables from the HDPVR. First time Sage tries to record from HDPVR you should get this scenario.