9.1 Bugs

Discussion in 'TiVo Coffee House - TiVo Discussion' started by RoyK, Oct 2, 2007.

  1. richsadams

    richsadams Well-Known Member

    9,078
    69
    Jan 4, 2003

    Advertisements

    No arguing that. It has to be frustrating. I think in all of that time we've been lucky enough to experience only a couple of issues that were eventually fixed by the following update.
     
  2. ZeoTiVo

    ZeoTiVo I can't explain

    25,527
    2
    Jan 2, 2004
    Probably not many users do bulk transfers like that. My typicla use is a show at a time. I did do a couple of 4 show transfers recently (all SD) and those wnet through. Maybe the new release will tweak MRV and help with your specific issue. They had in the last release overhauled MRV to get S2 -- S3 MRV going. Stands to reason hey would be looking to clean it up some more
     
  3. TivoZorro

    TivoZorro New Member

    1,448
    0
    Jul 16, 2000
    Pinehurst,...
    Yeah, its the nature of my schedule. Just got home from being away for ten days. My shows build up on the 80 hour so I have to get them on the 700 Hour. Its not uncommon for me to transfer 20 to 25 shows at one time. Always worked before Version 9 but since then its been problematic. Sounds like I may have to back off on the number I do at one time until this is fixed.
     
  4. RoyK

    RoyK New Member

    2,935
    1
    Oct 22, 2004
    SW VA
    I've had it happen more than a few times with two - one transferring and one queued. The second refuses to transfer until reboot - sometimes.
     
  5. RoyK

    RoyK New Member

    2,935
    1
    Oct 22, 2004
    SW VA

    Advertisements

    Today marks 21 weeks of unfixed 9.1
     
  6. jlb

    jlb Go Pats!

    9,468
    422
    Dec 13, 2001
    Burlington, VT
    I have not had any kind of pixelization issues on my HD. What has been happening lately is response to remote commands. It seems....er..........slow. I have fresh batteries in, I know my Xantech distribution hub is ok since my unsubbed AT&TiVo flies with commands. And I checked the IR emitter on my HD it it has not moved. I do need to check to see if I have it in the best location, but I am pretty sure.

    Nothing that completely bothers me, but I have had a number of overruns when FFF and the IRing. Usually need a few REPLAY presses to get it right on.

    My hope is that the reason it seems like forever for an update is they are trying resolve as many of the reported issues as possible.
     
  7. miadlor

    miadlor Member

    396
    9
    Sep 4, 2003
    Rhode Island
    One of my three dvrs has this mrv problem.
    All the others, including the pc can see the one.
    The one with the problem can connect to the network and use all network features just fine, but most of the time does not show the other dvrs for mrv.

    I've found by going to change the network settings, but backing out before making any changes, temporally fixes the problem for about 10-15 mins. Transferring is fine once started (even if it doesn't show again). I think the bug is just the ability to display the other dvrs in the now playing.
     
  8. Mar 4, 2008 #688 of 754
    RoyK

    RoyK New Member

    2,935
    1
    Oct 22, 2004
    SW VA
    Today marks 22 weeks (5 MONTHS!) of unfixed 9.1 bugs
     
  9. Mar 4, 2008 #689 of 754
    Phantom Gremlin

    Phantom Gremlin Active Member

    1,579
    5
    Jun 20, 2002
    Tualatin,...
    Don't worry, TiVo's ace technical team is struggling diligently to fix the problems.
     
  10. Mar 4, 2008 #690 of 754
    richsadams

    richsadams Well-Known Member

    9,078
    69
    Jan 4, 2003
    ROFLMAO :D
     
  11. Mar 5, 2008 #691 of 754
    gijoecam

    gijoecam GIJoeCam

    57
    0
    Sep 18, 2006
    Near the...
    It's not a hardware issue, plain and simple. Take two perfectly functioning* TiVos (*perfectly with respect to MRV), upgrade the software and the MRV crapps-out, and people honestly believe it could be a hardware issue? Gimme a freakin' break!! So, say you install a new program on your PC, and you get the BSOD. Do you say, 'Oops, must be a bad motherboard'??? I don't think so... You remove the offensive software FIRST, then see if it'll boot. Unfortunately, TiVo doesn't give us that option. They ram-rod software updates down the end user's throat and then disavow any knowledge of the issues, blaming it on hardware issues.

    Well, here's one up the ole' tush, TiVo. I replaced my TiVo with the supposed bad hard drive after my MRV started giving me fits. MRV worked FABULOUSLY when I first activated the TiVo... Fast transfers, quick remote response time, etc. It had version 8.5 IIRC, and the MRV worked AWESOME. Then, 'Congratulations!!' it updated on January 25th to 9.1 with the fall service update. Well, there goes my MRV right down the crapper. Admittedly it hasn't hung at the end of a transfer like the other TiVo did, but it's still slower to respond to the remote than the second coming of Christ, and transfers take for bloody ever!!

    Hardware problem my achin' arse....
    ________________________________________________________________

    My latest rant to TiVo:

    TiVo, you SUCK!! You took the best software interface in the market and flushed it right down the toilet with this update, and then are taking your old sweet time sucking the subscription fees without providing the service you promised us. Take your smiley box on legs and cram it!! I'm going to the cable company's DVR as soon as I can.
     
  12. Mar 5, 2008 #692 of 754
    greg_burns

    greg_burns Now in HD

    6,392
    2
    May 21, 2004
    Slower...
    I see where you are coming from, but you are completely dismissing the whole idea of how Tivo installs updates. It installs them to a different partition from the one you had been running the OS on prior to the update. If you have disk problems in that partition you are going to see weirdness after the update. Not nessarily software related.

    I AM NOT SAYING that is what is going on in your case. But IT IS THE CASE for a lot of people's problems after getting a Tivo update. Don't be so fast to dismiss it.
     
  13. Mar 5, 2008 #693 of 754
    Expat

    Expat Member

    168
    10
    Nov 19, 2004
    Spotsylvania VA
     
  14. Mar 5, 2008 #694 of 754
    gijoecam

    gijoecam GIJoeCam

    57
    0
    Sep 18, 2006
    Near the...
    No, I'm not dismissing that any more than TiVo is dismissing the possibility of a crappy software release. If, in fact, there was a bad sector on the hard drive of the first 40 hr TiVo, sure, that's a possibility. However, a kick-start didn't fix the problem either, and that *should* have moved the OS to a new sector, right? So I suppose that means I had TWO consecutive bad sectors, right? Possible? Yes. Likely? Not really.

    So, I go and buy a brand spankin' new 80 hr unit. At the first update, it starts giving me the exact same issues the 3 year old 40 hour unit gave me. Bad sector you say? Possibly, but what are the odds of two separate units with two separate hard drives built three years apart having the exact same set of issues with one particular version of the software on each of their respective hard drives? I think the odd are a lot more slim than the odds of both units getting a software download that causes the issues.

    With that in mind, what are the odds that literally thousands of users with countless different combinations of models, hard drives, routers, networks, and numbers of TiVo units in those networks experience the exact same set of glitches ONLY after the troubled download??? About a google to one if you ask me.

    So, the default response is that everyone's got a bad sector on their hard drives.... Riiiight.... And I got a bridge to sell ya' real cheap. I think that TiVo's die-hards honestly believe that if they keep saying it enough, it'll actually be true.
     
  15. Mar 5, 2008 #695 of 754
    RoyK

    RoyK New Member

    2,935
    1
    Oct 22, 2004
    SW VA
    I've seen this before and in my humble opinion it's a myth in 99% of the cases. If the user has a newer box that is working well and after the update it isn't then the problem was that the previously unused partition that the update was written to had a problem? Not very likely.

    On the other hand if its an older system and it has an older version on the partition 2 generations back that worked ok that is overwritten with a new update then the partition that was working fine before no longer is?

    Sorry, doesn't make a bit of sense to me.
     
  16. Mar 5, 2008 #696 of 754
    greg_burns

    greg_burns Now in HD

    6,392
    2
    May 21, 2004
    Slower...
    Yes it does appear to be unlikely, but why does installing a new harddrive fix a majority of the cases? Heck, I advocate reinstalling a fresh image with InstantCake first before buying another drive (after verfiying the drive tests good using testing software like Hitachi Drive Fitness Test).

    I am not talking about the MRV problem mentioned, but rather the random lockup/reboot/pixelation problem seen by lots of people. Put in a new drive, with a fresh image, problems disappear. I've seen this pattern repeat over and over on this board.

    Drives fail all the time, old and new. Just today somebody brought their laptop into work that Windows would boot the whole way anymore. Ran Hitachi on the drive, guess what? Another bad drive. See them all the time.

    Even if the root problem isn't hardware, then reimage the drive and start fresh. Either it will fix the problem or it won't.
     
  17. Mar 5, 2008 #697 of 754
    RoyK

    RoyK New Member

    2,935
    1
    Oct 22, 2004
    SW VA
    Sure drives fail. But I'd be willing to bet that a large percentage of boxes that are 'fixed' after an upgrade by replacing the drive suffered from a corrupt installation of the upgrade, not from a drive defect.

    I would argue that a corrupt installation and the failure to check for same is a software issue.

    Your suggestion of reimaging is a good one. That would result in a reinstallation of the upgrade and another chance at it working. Unfortunately that isn't a realistic option for John and Mary Public.
     
  18. Mar 6, 2008 #698 of 754
    gijoecam

    gijoecam GIJoeCam

    57
    0
    Sep 18, 2006
    Near the...

    I meant to mention that too... The second TiVo was a new unit still in the box. If the 'new' sector of the hard drive it wrote the update to was corrupted, then either that sector was corrupted from the factory, or TiVo's lousy flawed update caused the problem. Again, what are the odds of two tivo boxes built three years apart experiencing the exact same issues with the same software version? Now, what are the odd of BOTH of those failures being caused by bad hard drives? Not very good, IMHO...
     
  19. Mar 6, 2008 #699 of 754
    rainwater

    rainwater Active Member

    7,066
    5
    Sep 21, 2004
    I don't think it is a either or situation. It is very common for a new drive to have bad sectors. In fact, I wouldn't bet on the drives always being new. I think the other issue is the TiVo software updates aren't able to handle situations where a partition has bad sectors. They could certainly improve their fault tolerance so they can get around some of these situations. I think one issue is the OS is more susceptible to these issues than the data partitions. The data partitions having drive problems might cause random glitches or crashes but not complete failure. But the OS partition is a different story.
     
  20. Mar 6, 2008 #700 of 754
    richsadams

    richsadams Well-Known Member

    9,078
    69
    Jan 4, 2003
    All true. :up:

    One other variable that TiVo has no control over is the delivery of the update itself. With tens of thousands of bits of data in tens of thousands of packets being passed through multiple networks, there is always the opportunity for corruption. If it's being delivered by a phone line, no one has to stretch their imagination too far to know that they weren't designed for high-volume data transmission and are often called upon to pass much more information than they were ever designed for. If by broadband there are tremendous opportunities for data corruption and add even more failure points if wireless broadband is employed.

    Update failure more than once on one box and or again on a new box wouldn't be surprising if the delivery system to the TiVo itself were the problem.

    That's not to say that the update itself, the boxes or any number of variables aren't the culprit. But one has to consider how many data corruption points there are and not all of them are in TiVo's domain.
     

Share This Page

spam firewall

Advertisements