6.3c coming?? Still getting lock-ups...

Advertisements

OK, thanks for all the help. I have the WD diagnostics boot floppy, and ready to go. But, my unit is still (18+ hours) running the clear and delete. Can I just unplug it?

 

Well, there is not much on TV these days anyway, so I am filling my time playing with linux and prepping the computer for my TIVO hdd. I am hoping that the C&D (programs & ToDo) will finish on its own, but at 36 hours, hope is giving way to reason. If it doesn't happen soon, I guess I am going to have to pull the plug.

 

Exactly! Maybe it is Tivo's way of trying to get folks to "forklift" upgrade units... Oh yeah I forgot, only Directv is evil and calculating...

 

I have now rebooted twice with 6.3 in about 10 days.

Maldini

 

Advertisements

I doubt that C&DE actually fixes things permently... one of my boxes has a brand-new copy of 6.3a in it from a drive replacement with 3.1.5f where it had to be C&DE'd (the drive was from another HR10 when an upgrade failed), and then it got 6.3a over the phone line (!).

After all that, that box has had several reboots, one while it was playing a DHD show.

On both of boxes (both on 6.3a), I often find that one or the other has rebooted overnight for no reason. (No new software, and they are on UPSs; 30 sec skip missing to indicate reboot).

I'm glad I have an IC3.1.5f CD to use if I need to.

 

I completely gave up and went the IC way. At first, I tried it on my old drive. It sort of works. Meaning, it powers up and gets to the TIVO menu, but the bootup process takes 3-4 hours.

I figger'd that maybe the drive was the source of all the problems, so I replaced it with another WD2500 and IC'd it. I am 20 minutes into the booting of that IC version, and still at the gray "powering up" screen. It looks like a repeat of the above, so I am expecting no joy.

Is it a known issue that a new IC'd drive takes this long to boot?

FWIW, I never am able to actually watch TV. After a laborously long Guided Setup, the end result is that it does not recognize the Access Card. I doubt my same old access card and access card reader are suddenly failing after 2.5 years. So, something else is going on.

 

I used IC for my hr10-250 and it took a few minuted for my tivo to come up, not 20 minutes, maybe something is up with the image you are loading. Take the IC image you are using and add it do the zipper tool directory then create the zipper iso image.

 

What Sk33t3r said..... any new drive takes a little longer at the 'Powering up' screen the first time only. I seem to recall on a new drive it's checking the partitions or something? I just upgraded one of mine from a single 250 to a single 500 and it took *just* long enough for you to start going uh-oh... but nothing like 20 mins. Perhaps 2 minutes max. It *feels* like 20 minutes.

You may want to report those symptoms in the Upgrade forum.

 

The record light should come on for a few seconds and then go off
But as Lee said, it waits just long enough for you to doubt yourself and then the almost their screen comes up.

 

Woudl manually forcing the scheduled calls daily resolve this until a fix is in place?

 

Are you upgrading to 6.3a/b during the guided setup process? You need to make sure you disconnect your cable immediately after the activating the DVR call so you don't get the upgrade. I was gettin gthe invalid access card message with 6.3.a and have not had it since I went back to 3.1.5f, also I found that despite what the IC tell you, you must do a clear and delete everything after imaging the drive (before you go through a guided setup).

 

+1

I imaged two brand new drives with 3.1.5f and upgraded to 6.3a and a CDE, both worked ok but then rebooted pretty regularly after awhile.

 

For a month I had no lockups after allowing 6.3a to download, but starting three days ago the HR10-250 rebooted itself once a day, then yesterday it rebooted three times in an hour.

Plus one lockup where the frozen picture stayed on the screen but none of the remotes could control anything, like changing channels, FF, or Power on/off.

Unplugged the HR10, let it sit a few minutes. Powered back up and its been fine for about 12 hours.

Reading these posts, I don't expect much improvement from 6.3b.

Leaving the phone line unplugged and keeping 3.1.5f would have been better. Oh well.

 

I wish I'd left my phone unplugged. I have 1 unit at 6.3a that is rebooting every once in a while but experiences the Audio drops. The other unit has 6.3b. It had started rebooting under 6.3a and 6.3b has not cured that. In fact, I feel like its gotten worse. I might place another call to Level 2 support just to let them hear from me since 6.3 was installed.

Reverting to 3.1f is not an option for me. I only have a small laptop (Sony Vaio) so there's no way for me to connect the Tivo drives, without buying casings, drive cables, etc.

 

WTF is going on here. 6.3a was fine on my machine for a month, and now reboots once/week (or more often). From what I read 6.3b doesn't fix it either. Is it really the bad guide data? Or is there some bug that requires a "6.3c" to come out?

I'm going to be really, really pissed off if this is now the new "norm" (reboots fairly often) with the HR10. Judging from the HR20 forums, things are likely no better if you switch to that box (and possibly quite worse).

I don't know what I'll do if this continues. Quit DirecTV and go to Comcast?

 

I timed the welcome grey-screen and it was up for 47 minutes! When I first tried the InstantCake image, it was on the original HDD and I could reasonably understand that maybe disk errors had it going through a constant read retry cycle that caused the time. But, I am now using a new drive that passed WD's extensive diagnostic test with flying colors. Same result. Other routine tasks in guided setup also take beaucoup time.

Not sure what you are saying. Could you elaborate?

Actually, these are two other problems. I am still at 3.1.5f (pure IC image). I really think that disk corruption from 6.3a or bad guide data was the original cause of my issues, but despite that, I thought that upgrading to 6.3 (a or b) might be a way of solving my currentboot and other performance issues. So, I have tried to force a phone call (not to further complicate things, but I have Vonage and an external modem - using a dial prefix of ,#319 or ,#396 and *99 which worked great for me for the last year). The phone call never dials the modem and the Tivo stays in "dialing" mode literally forever. The only way out is a power-cord reboot, which of course takes me full cycle to the problems above.

Back to the access card.... I cleaned the card and gently blew the dust away from the reader contacts, which did not immediately help. But, after several pull/insert cylces and some wiggling, it did recognize my card and give me real live TV. Hooray! But, after several hours of just being on, it stops recognizing the card. Usually a re-insert will start it up again. But, this is no way to run a DVR. The fact that I had zero access card issues for the past 2.5 years and the random timing of the current "no access card" detection and that a simple re-insert fixes it, all tells me that this is - hard to believe - a software issue and not a card or card reader issue.

At some point, I did do an C&DE, but I can' t remember when - it was probably on the first IC image (original HDD). That is just about the only thing left to try. Do I need to re-do the IC imaging and Guided Setup and C&DE, or can I just do the C&DE from where I am now?

 

Has anyone confirmed that the "faulty" guide data is at fault for /var filling up? Or that forcing a daily call to rebuild the data cleans out /var preventing the reboots? I can handle this workaround for a little while if it's what's required, but not forever.

If so, wouldn't the reboots stop when the "faulty" guide data stream is fixed? Any news on that front?

Anyone? Bueller? Bueller?

 

I've had two lock-ups with the record light on and no signal from the HDMI. A power-cord reboot fixes things.

Does this sound like the issues you guys are seeing? VERY frustrating.