Rolled back to 20.3 thread

Advertisements

I've learned to just respect your stance on things (or sometimes just not to argue with them).

I'm more concerned about whether the person who had an "update" pending, who got stuck on the reboot, and seems content with accepting drive failure, actually has a failed drive.

Last time I pulled a Roamio from service, to see if why a perfectly good drive was failing most of the TiVo KS54 tests, I found it would fail the unused stock drive, as well (on all the specialized tests one expects not to work on a non-stock drive). The test that person loosely described, sounds to be one of the questionable specialized tests.

Not many, that have said anything, have even been in the KS menus of a Roamio, and even less of them have run the KS54 drive tests. I was pretty much told (by forum members), that any testing should be done by a PC using the drive manufacturer diags (and everything passed, repeatedly, and I put my upgrade drive back in). Once I quit questioning the matter, the discussion died. The overwhelming consensus was that I should just trust the PC-performed results, and ignore the TiVo-performed results.

That said, how can anybody be certain that the first person (that I can recall, or am aware of) to report that TiVo instructed them to use the KS54 tests, and had a failure result, actually has a failed drive? It might not be a bad/failed drive.

If they'd attached it to a PC and run manufacturer diags, resulting in a failure status, I'd 100% accept it was a bad drive, and nothing more.

I never meant to use your double-rollback experience as a means to an end, or to misrepresent anything, if you feel that I did. I just neglected to include (or reference) my concerns about the person who person who was bricked during an update process, and is pretty convinced it's a drive failure, without testing the drive outside of the TiVo.

Valid concerns, right?

 

Exactly. Mistakes happen and you roll with it. It's only a DVR people. Learn to get some perspective.

Enjoy the weekend!

 

They were meant as jokes. I read about this on Zatz twitter feed only to find out that only 13 boxes were affected. Perspective. Apple minor iOS updates have affected millions and no one says boo.

@nooneuknow Never has one said so little with so many words. Try to keep it pithy.

 

Keeping things short leads to misinterpretation of what I say, and many follow-up posts to clear such things up. If it bothers you so much, I invite you to add me to your ignore list. It would be an honor.

 

Advertisements

It is a very expensive DVR and TiVo has a history of blaming their end problems on everyone except themselves.
If a perfectly well running TiVo starts acting up or getting crazy after an update more then likely it's the update that's causing the problem.



Sent from my SPH-L720 using Tapatalk

 

I don't know about being expensive. If I had DVRs from Comcast or FiOS in my area. The cost to me over several years is easily on par or more than for the TiVos. Plus I wouldn't have the option to sell it when I'm finished with them further reducing the cost. The cable company DVRs are the ones that are expensive.

 

All of this is precisely why I found the prior "explanation" of what happened completely unsatisfactory. If we'd never again had this problem occur then it would still have been bad process with a fortunate outcome.

However, the problem not only recurred, but did so in troubling ways: we have people getting re-rolled back, and people getting rolled back for the first time. It reflects poorly on
Tivo, to out it mildly.

For my part, I can't get an eyeball in edgewise this morning bc my kids are gaming.