Our box rebooted last evening as well around 7 PM and again this morning about 7:30 AM. There seems to be no rhyme or reason behind these reboots. A couple of weeks ago, our box randomly rebooted 3 times between 5 and 5:30 PM. I cannot believe that all of these reboots are for updates!
It could be for a "patch" - not a full firmware update - they did bring in some recent features and these patches could correct problems with those features. One of my PVRs rebooted today around 4PM, but I hadn't noticed any other recent reboots.
Often, with the patches, I won't get a reboot but will lose the scheduling of a recording or the communication with the EHD. If I can't pause or rewind live TV or if the red light on the HD dock isn't flashing, it's a sure indication of something having been changed. I then check the scheduled recordings to see if any have been dropped.
Seems to have been happening quite often in the last ten days/two weeks or so. Sometimes all is well - sometimes not.
A reboot cures all.
I called to complain about lost recordings. They knew about the problem right away and they claim that this is their top priority. Naturally, after 8 months, I am very skeptical. The problem is with the 8300 and 8642 but apparently less so with the 8642. While they couldn't give me a timeline for a fix, the level 2 person claimed that they actually have "customers" testing a new version. I asked if I could test this version as well since I have nothing more to lose but was essentially told no.
Been thinking about just upgrading the internal drive but why should I have to? I hate dealing with Rogers. I got a small credit fairly easily though. If you're so inclined I would encourage you to at least get that if you're having problems.
I can't trust Rogers for anything anymore. They should've tested for all these things before they launched the 'broken' firmware back in October 2010. After almost 10 months of fumbles, inability to resolve the issue even with Rogers PVR Extender, I'm taking whatever statement from Roghers with a sackful (not a grain) of salt.
Had to reboot master bedroom PVR, no sound sound live or recored last night. Family room (with external) was fine luckily. I have only had one successful reboot down there without losing external recordings since this all started.
I was unable to find a thread covering HSUD on the Cisco 8642HD.
My Cisco 8642HD internal HDD is spinning up and down every few minutes.
Some background: I own two SA 8300HD PVRs and late last fall like most other people experience problems after the firmware update. I contacted Rogers a number of time and posted some of my experiences in this thread. Knowing that it was not a good idea to cycle the HHD on and off every few minutes, I when through all the steps I could to limit it (set startup timer, record music channel Ö). A total pain in the butt. My son who uses the second unit would not and after a couple of months his HDD failed. At that point I contacted Rogers total them that their faulty firmware was damaging my PVRs, that one had just failed and that I wanted a couple of free rentals until they fixed their problem. The CSR said that sounded reasonable to him and transferred me to someone who made the arrangements. At present I have replaced the HDD in my sons PVR, both 8300HD are still offline and we are using the rental 8642s.
Back to the 8642s: Right off the bat I noticed the 8642 having the same HSUD problem as the 8300 and reported it a couple of times to Rogers who told me they were aware of the 8300 issue but did not know of this issue on the 8642. The second or third time I called, I finally told them since it was their rental that they were damaging, I guess I really didnít care that much and havenít talked to anyone at Rogers since. Since the HDD in the 8642 is so much quieter, Iím assuming most people donít realize itís cycling and havenít called Rogers.
My problem now is a have a friend wanting to purchase a Rogers PVR. Iíve told them to wait until they are on sale and Rogers has fixed the HSUD issue.
Does anyone have any information on upcoming firmware changes for the 8642 to fix this issue?