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?