6.2 Causing Random Reboots?

[CTBrian]

We got the 6.2 upgrade as scheduled on both of our HDVR2 units, and one of them has decided to randomly reboot at various times. One night, during a recording of ER and 2 other nights while we were simply watching TV. It goes thru the whole reboot sequence including acquiring data from the satellite. Has anybody else had this happen or know a way to fix the issue?

[skinnyjm]

Don't have that problem here.

50% 6.2..., HNS Yes, RCA No.

[itgirl]

HDVR2s are the worst DVRs ever made. They are going to have problems. Buy a new one.

[bengalfreak]

HDVR2s are the worst DVRs ever made. They are going to have problems. Buy a new one.


Don't be silly. HDVR2's are identical to the Phillips DSR7000 and RCA DVR39. They all came off the same assembly line. The only difference between any of the units is the faceplate.

[beanpoppa]

Most likely is that you have some errors on your drive. They are on your active partition, which, until the upgrade, was inactive.

We got the 6.2 upgrade as scheduled on both of our HDVR2 units, and one of them has decided to randomly reboot at various times. One night, during a recording of ER and 2 other nights while we were simply watching TV. It goes thru the whole reboot sequence including acquiring data from the satellite. Has anybody else had this happen or know a way to fix the issue?

[TivoGuy30]

The random rebooots could be a problem with the 6.2 software. my hughes dvr-40 randomly rebooted with the 6.0 Beta software, and was updated to 6.1 and the reboots stoppped. so it could be a problem that wasnt fixed for other units.

[dtremain]

The random rebooots could be a problem with the 6.2 software. my hughes dvr-40 randomly rebooted with the 6.0 Beta software, and was updated to 6.1 and the reboots stoppped. so it could be a problem that wasnt fixed for other units.See Beanpoppa's post immediately above your own. It applies to your situation as well as the op's.

[rminsk]

The random rebooots could be a problem with the 6.2 software. my hughes dvr-40 randomly rebooted with the 6.0 Beta software, and was updated to 6.1 and the reboots stoppped. so it could be a problem that wasnt fixed for other units.6.1 does not work on a dvr-40. 6.1 was for the R10 only.

[fides7]

i've had the same thing happen to me 3 times....i just got off the phone w/ tech rep...he told me to reboot, wait a few days...if it does it again, then reset and re-install 6.2. If random reboots still occur, then it will be replaced. BTW, I have Phillips DSR7000.

[shaady]

I've had two reboots (while I was watching TV) in the past two days. Perhaps more while I was not watching TV (not sure). Exact same as you described with the loading software, long delay, blah, blah, blah...

I've had 6.2 since Thur 5/19.

[aristoBrat]

FWIW, 3 HDVR2s running 6.2 for over a month with zero unexpected reboots.

[Mikegia5]

I got 6.2 today and it rebooted for the first time a few minutes ago. We've had this HDVR2 for probably two years now and it's never rebooted before. If it happens again, I'll be calling the tech rep. Luckily I've got the extended service plan and they should replace it for free.
Mike in Phoenix, Arizona

[rogue5]

I have one of the hughes units and mine started to reboot at random also. Not only that but I haven't been able to get through to the daily call. I ran a test call and after 2 tries in connected but I couldn't do the daily call. The last good call was when it DL the 6.2 upgrade. How do I manually reload 6.2 (if possible), I have tried rebooting at least twice (not counting the random reboots). It has done the random reboot at least 3 times since sunday morning, after the update. I hope my DVR isn't corupted, I will be pissed if it was.

[captenblack]

My DirecTV Tivo receiver is also rebooting at random times since Saturday when the 6.2 upgrade occurred.

Thus far I've noticed it happening once each evening.

[itgirl]

Don't be silly. HDVR2's are identical to the Phillips DSR7000 and RCA DVR39. They all came off the same assembly line. The only difference between any of the units is the faceplate.
and those models suck too.

[itsmeitsmeitsme]

itgirl..........what is your problem????? you go from thread to thread spreading such joy.....and since all these models suck then what do you reccomend? (can't wait to hear this one)

[happyharry]

Used to reboot maybe once a month and the reboot was quick.
Last 2 nights my HDVR2 has died every evening. Reboot seems to take more than an hour - can that be.
What do I do?
Is my HDVR2 dying and this is just making it worse or???

[Gunnyman]

2 units HDVR2 and a DVR40.
Neither one has had any reboot issues. When I was running 4.01b on my HDVR2 it would reboot once in a while. 6.2 seems to be very solid.

[rminsk]

New software releases tend to expose more dying hard drives. The TiVo has two different boot partitions, an active partition and a non-active partition. When new software is installed it is installed on the in-active partition. The TiVo than swaps the boot partition making the in-active the active partition and vise-versa. Then the machine reboots using the new software. If your drive has a flaw in the previously in-active partition then you may get reboots.

I am not saying this explains all the reboots but it could explain some. It seems with every software release there are a few machines that suffer reboot problems.

[bengalfreak]

and those models suck too.

Nope, I've had HDVR2's and DSR7000's for over two years and haven't had the first problem with any of them. Series 2 is the way to go. Maximum upgradeability coupled with maximum hackability. The best of both worlds.

[itgirl]

I'm sorry if I am blunt. I don't mean to be, I just call it like I see it. I work with this stuff every day, day in and day out for quite some time now. So I kinda know which receivers work fairly well, and which don't. All DVRs have the same interface, but those aforementioned are virtual dinosaurs at this point and continually have problems. Of course, all models have had some issues so I couldn't tell you a specific model that is guaranteed to work, that is just not realistic. I'm sorry if I offended you, I really didn't mean to I just tend to be very blunt.

[happyharry]

Talked to tech rep at D yesterday. Checked with database and others and then said there are no problems with 6.2 that they know of or that would cause reboots. I guess we are all "wrong". Their suggestion to me was try a complete reset (lose everything) and if that doesn't help - buy a new DVR - mine is dying.
Since most of my season pass stuff is done for the year - I'm trying the full reset. Really not losing a lot and I can't continue. Rebooted twice during 2 hour period yesterday.
Reset took a lot longer than the hour it said it would and haven't had chance to resetup everything yet. Hope this fixes it.

[aristoBrat]

I'm sorry if I offended you, I really didn't mean to I just tend to be very blunt.
IMO,

Being blunt = "those aforementioned are virtual dinosaurs at this point and continually have problems" :up:

Being [rude, condescending] = "and those models suck too" :down:

:D

[aristoBrat]

Talked to tech rep at D yesterday. Checked with database and others and then said there are no problems with 6.2 that they know of or that would cause reboots. I guess we are all "wrong".
Well, I guess from their point-of-view, a hard drive failing isn't technically a 6.2 specific issue. If the partition that your 6.2 installed on is really on a bad part of the disk, any version update that installed there would probably have reboot problems. :confused:

FWIW, I'm not sure how good your computer skills are, but it might be less expensive to buy a new, larger hard drive for your current DTiVo vs. buying a totally new DTiVo. I'm guessing that it's out-of-warranty if you mentioned having to buy a new one...

[rminsk]

All DVRs have the same interface, but those aforementioned are virtual dinosaurs at this point and continually have problems.They are all the same and are not dinosaurs at this point and do not continually have problems. All of my machines are series 1 (which are getting to be dinosaurs) or series 2 (non-R10) and have been rock solid. Most people on these groups will report the same. The only problem people have with them is the disk drive dying which happens on all DVR reguardless of make, model, or series.

[makeen]

My DVR started rebooting this morning at a rate of about every 35 minutes. Then it started getting farther apart. At least 8 reboots so far. This has never happened before. I too talked to directv tech support and they said I should unplug it and wait 15 seconds and see if that works. Well it rebooted about 40 minutes after that.

Did I mention that this is the first problem I've encountered with this DVR

I have 6.2 but I don't know exactly when it upgraded to that possibly 2:36am this morning.

I've had this unit since Dec2003 Model Samsung SIR-S4120R.

:confused:

[shaady]

Did I mention that this is the first problem I've encountered with this DVR That's a good point that I forgot to make, makeen. This rebooting is the very first problem I've had with this unit (series2, for 2+ years). I had many other problems with my first TiVo (series1, for 2+ yrs also), stuttering, freezing, skipping, sound droppin out...etc.

[tonering]

My Hughes HDVR2 started rebooting just after 9 pm this past Monday. Sometimes it reboots during the "Almost there, just a few more minutes" screen. Once in about every dozen reboots it gets to the "acquiring information from the satellite" screen, then reboots. I found that if I disconnected the cables from the dish, I can get into Tivo Central and gain access to my recorded programs. However, as soon as I reconnect the cables to the dish, the receiver reboots.

I called DTV tech support yesterday afternoon and explained the problem and what had been done so far. The csr then transferred me to an upper level technician. We tried a couple of things, but he didn't request that I run a bunch of silly tests or a full reset. Much to my surprise, he decided to send me a new DVR. He said they want to look at my old receiver to see if they can isolate the issue, and understand why some receivers apparently have problems with the 6.2 software install.

I am very pleased with the total tech support experience, and should have the new D*Tivo by this coming Monday. (They are even paying the shipping to return the defective box.) In the meantime, I am transferring the "now showing" programs to a Pioneer DVR-510H recorder.

[apollo8fan]

I got my upgrade on Monday, everything was going smoothly, then yesterday afternoon, the HDVR2 just decided to reboot and locked-up during the reboot while my wife was watching a pre-recorded. When I got home from work, my wife said it sat at the "powering up...." screen for a "long time". I let it sit there for another 10 minutes without any progress. I pulled the plug and it restarted without a hitch.

Weird.

[hokiepolk]

Received 6.2 late last night and mine has rebooted twice in the past three hours (HDVR2). If it happens again, guess I'll call D*.

That, and the goofy remote control issues :(

[soccergrunt]

New software releases tend to expose more dying hard drives. The TiVo has two different boot partitions, an active partition and a non-active partition. When new software is installed it is installed on the in-active partition. The TiVo than swaps the boot partition making the in-active the active partition and vise-versa. Then the machine reboots using the new software. If your drive has a flaw in the previously in-active partition then you may get reboots.

I am not saying this explains all the reboots but it could explain some. It seems with every software release there are a few machines that suffer reboot problems.


Apparently 6.2 exposed my bad hard drive on my Philips DSR708. I received the upgrade last Sunday afternoon. Everything looked fine until Monday morning when the video froze while watching a recorded program. After performing a reset, it looked fine again for about 20 minutes. Same thing. After about three more resets, the unit froze on the Welcome...Powering Up screen. Monday night, I called D* CSR. They promptly moved me on to tech support. Tech told me to wait out the night and see if it would correct itself. After I chuckled, I went ahead and left it at that and called the next morning.

On Tuesday, called D* tech and it took me about 10 minutes to convince them it was a bad unit. This unit is 4 months old and just out of the initial warranty period. They offered to replace with no fee and paid shipping on the return unit without me asking. New unit is due tomorrow. The interesting comment by the tech was that he has taken several calls from customers with the same drive failures after upgrading to 6.2 on units less than 90 days old.

[happyharry]

Did the full reset as directed. Takes a while!. Hasn't rebooted since but it is too early to determine. I find it interesting that this reboot seems to be a "recent" problem - did the version of 6.2 change. Just a little code that won't hurt anything. Heard that before.

[rogue5]

Well I got home this afternoon and my hughes started to reboot every 5 minutes, I amin the process of clearing the thumbs suggestions and then I will see what happens. I also am scratching my head about the change in the remote button assignment? I hadn't had any problems with mine, and I have had it 2+ years. I am glad I have the Tivo insurance so D* will just have to give me a new one for screwing the one I had. At least I will recoop some of my insurance money :D ! Has anyone seen or heard elsewhere about this problem and a possible solution?

[Breezy]

I got 6.2 last week sometime and I've been experiencing problems w/ my
DVD recorder remote controlling my TiVo.
When I record something from the Tivo to my dvd recorder and then insert
chapter titles, it does things to my tivo. Like deletes, records, set season passes, etc. I can't see what is happening because the screen is on, the screen for the dvd recorder is on showing me what chapter I'm making. Every time I press a letter on my dvd recorder remote, it's doing things to my Tivo.
I called Directv the other day and they transferred me to Tivo and I thought they were very helpful and fixed the problem. She had me readdress my tivo remote control. Well, that seemed to work for about 2 hrs., now I'm back to where I started from.
I tried resetting it, that didn't work.
Any ideas?

[makeen]

Has anyone tried clearing out all the data, recordings, etc. to see if this helps. I am trying to save some of my programs before I do that. I was hoping to see if someone has already tried that.

That is what diretv tsr is recommending I do next.

[rminsk]

Has anyone tried clearing out all the data, recordings, etc. to see if this helps. I am trying to save some of my programs before I do that. I was hoping to see if someone has already tried that.

That is what diretv tsr is recommending I do next.If it is a failing harddrive that will only postpone the problem. Eventually it will try to write data again to the bad spot on the disk. DirecTVs responce to any problem on the DirecTiVo is do a clear and delete everything.

It seems the DirecTV guide for diagnosing problems on the TiVo:
1. Listen to users problem
2. Say "I have never heard of anyone else having <problem>"
3. Do a "Clear and Delete Everything"

[captenblack]

Called tech support late last night, the lady who helped me said she's gotten tons of calls about problems with the 6.2 software, and she's just sending people new units right and left. Before I could even finish explaining the problem with my system rebooting every once in a while, she said, "ok, I'm sending you a new unit". I had the Hughes SD-dvr40 and will probably get the R10. Problem is, I bought the dvr40 as an upgraded unit from weaknees. I tried to explain that to her, she didn't seem to care. I guess I simply upgrade the R10 on my own? Does anybody have suggestions on how to handle this? I don't mind doing it on my own.

[newswatcher]

I'm sorry if I am blunt. I don't mean to be, I just call it like I see it. I work with this stuff every day, day in and day out for quite some time now. So I kinda know which receivers work fairly well, and which don't. All DVRs have the same interface, but those aforementioned are virtual dinosaurs at this point and continually have problems. Of course, all models have had some issues so I couldn't tell you a specific model that is guaranteed to work, that is just not realistic. I'm sorry if I offended you, I really didn't mean to I just tend to be very blunt.

So, you recommend (fill in the blank) instead of the other DVR?

[dressiv]

Good to hear Im not the only one with this problem....I got the 6.2 upgrade sunday and my Hughes has just started rebooting at random

[Dkerr24]

My RCA unit isn't rebooting, it's simply freezing while recording a program. The 120gb drive is about 6 months old. I bought the drive online from Tiger electronics, and it was packaged for shipment very poorly. I suspect the drive may have taken quite a beating just getting shipped here.

However, these problems began after the 6.2 upgrade. I'm doing a "Clear and Delete" everything to see if that clears it up.

[happyharry]

After doing the complete reset Tues night / Wed morning I have not noticed any reboots. Watched all last evening and it ran fine which is first time since 6.2 upgrade it has run more than a couple of hours of watching without reboot. Hated to lose stuff although not a lot and the time was a pain but if it delays a purchase until I'm ready for HD - this is fine with me.
There has to be something in this latest 6.2 code that is causing these issues.

[makeen]

I haven't cleared out everything yet but I am experiencing a lot less reboots. It is now friday 5:30pm and I haven't had a reboot since Thursday 9:30pm.

Are you all seeing improvements also?

[CTBrian]

Since I began this thread, our HDVR2 had been behaving...of course I probably just jinxed it. I'll keep my eye on it and see if DTV needs to send me a new unit - we've got the insurance too. Thanks everyone for your responses so far....hopefully it's an issue that will be addressed quickly!

[alan]

My SAMSUNG SIR-S4120R got the 6.2 version on Monday and has been rebooting about 4-5 times a day since. Tried to call tech support on Wednesday, but it was around Midnight on the east coast and they take the database down (or at least that's what the CSR told me) so the CSR couldn't do anything that night.

I just got off the phone with another CSR and he told me that they haven't seen this problem with 6.2 yet. I think that's a standard response.

He had me remove the two sat-inputs and pull the power plug and then put it all back together. It booted up and he basically told me that if it happens again that I would have to do an ERASE ALL and see if that cleared up the problem. If not, then they'll ship a replacement unit.

They asked a lot of questions about the UPS that I have the TiVo plugged into. I think they were hoping that it was just a loose power cord. The guy told me that unplugging the SAT-Inputs and the power cord was good to do just to make sure they are reseated.

He told me that I should watch all those programs that I've recorded so that I would be ready to do the ERASE ALL if it came to that. Needless to say, I probably won't be calling them back anytime soon.

I do have to say that the 6.2 menus are blazingly fast in this version and I haven't seen the menus freeze for several minutes like I did in the last version. Seems like the User Interface in 6.2 is so much better than it was.

If they would fix the reboot problem and the Lifetime TiVo stuff that I paid $249 for then I'd be a happy man.

SAMSUNG SIR S4120R (not hacked)
Version: 6.2-01-2-381
Uptime: about 50 minutes
71 Season Passes and Auto Record Wishlists

Sony SAT-T60 (Hacked)
Version: 3.1.0c2-01-1-011
Uptime: 59d 10h 00m 15s
57 Season Passes and Auto Record Wishlists

[rogue5]

Well I have somewhat good news, since I deleted all the thumb suggestions (kept my recorded stuff and passes) I have not had any problems. I also made a call after that also, hopefully the combination of all that stuff and maybe D* dropping a hot fix without saying anything will fix it. I would rather not have to replace it untill the new stuff comes out for the MPEG4 transmissions. :cool:

[Dkerr24]

To followup my earlier post, doing the "Clear and Delete Everything" seems to have cleared up the daily freezes on my RCA unit.

I was also sucessful in restoring my backup image of my Samsung using a LBA48 boot disk. The DTivo now reports 144 hours of recording time instead of the 120 hours.

[Galley_SimRacer]

I have had the 6.2 update for several days now. I came home from shopping to watch the Indy 500 and my HDVR2 is stuck in a reboot loop! I have unplugged the power cable and the satellite cable, and that has had no effect. Aaargh! :mad:

[makeen]

The reboots have increased a lot today. Some days they are much better though. I find improvement when I delete some of my recordings. It also improves after a forced call. I don't want to do a total clear because I can't part with some of the recordings and it is so difficult to save to VCR when it keeps rebooting several times during the save.

I thought my reboots had stopped a few days ago, but when I vacuumed the back of the unit after seeing a lot of dust there the reboots came back with a vengeance.

[Galley_SimRacer]

I called tech support and they said my hard drive had most likely died. They are sending a replacement for my two year old HDVR2 for $50. If only I had $700, I would've just bought the Hi-Def unit instead.
Edit: I don't suppose they sell me one for $50/month, would they? ;)

[stevel]

I have 6.2 on a brand new drive, and it has been rebooting rather frequently. A check of the log does show what could be disk problems, so I will pull the drive for some diagnostics and see what I get.

[shplatt]

I'm wondering if the reboot problem might be related to boxes w/ expanded hard drives. Particularly, as in my case, HDs > 137 Gb. I have a 704 w/ two 160 Gb drives. I have not upgraded it to 6.2 yet, because I'm waiting to see how other people's upgrades go. I read a post about 6.2 supporting LBA48 (my first post, so I can't link yet). I have not substantiated this. However, if this is true, perhaps there could be an issue with a DTiVo that has been using 137 Gb of a 160 Gb drive one day and then attempts to use the entire drive the next.

For those who have been having reboot problems: what size/number of drives are you using?

[rminsk]

However, if this is true, perhaps there could be an issue with a DTiVo that has been using 137 Gb of a 160 Gb drive one day and then attempts to use the entire drive the next.This is not possible without adding partitions to the drive.

[mphare]

I have a stock 704 that is less than a year old. Never had a problem with the unit before. I got 6.2 on the box late last week. I had my first and only reboot (that I've seen) today. I've asked my wife to monitor it as she's home with the kids and uses it more than I do.
If it goes cronic I'll notify DTV and see what they say about it.

[john-duncan-yoyo]

Called tech support late last night, the lady who helped me said she's gotten tons of calls about problems with the 6.2 software, and she's just sending people new units right and left. Before I could even finish explaining the problem with my system rebooting every once in a while, she said, "ok, I'm sending you a new unit". I had the Hughes SD-dvr40 and will probably get the R10. Problem is, I bought the dvr40 as an upgraded unit from weaknees. I tried to explain that to her, she didn't seem to care. I guess I simply upgrade the R10 on my own? Does anybody have suggestions on how to handle this? I don't mind doing it on my own.

First off- If they don't care don't bother them with the details.

Weaknees has a guide for the R10 upgrade but the twinbreeze bracket is different for the R10 and may not be compatible with the one for the Hughes SD DVR-40.

It was pretty painless when upgraded my Hughes SD DVR-40. There isn't much difference from the pictures. Take your time, ground yourself and make sure all the cables are in place.

Are you planning on salvageing your second hard drive from the Hughes?

[stevel]

Grumble - full diagnostics gave the drive a clean bill of health. Think I'll start over and see what happens...

[captenblack]

First off- If they don't care don't bother them with the details.

Weaknees has a guide for the R10 upgrade but the twinbreeze bracket is different for the R10 and may not be compatible with the one for the Hughes SD DVR-40.

It was pretty painless when upgraded my Hughes SD DVR-40. There isn't much difference from the pictures. Take your time, ground yourself and make sure all the cables are in place.

Are you planning on salvageing your second hard drive from the Hughes?



Thanks for this advice, had a good conversation with DirecTV support earlier today. You're right, they don't seem to care about what you send back and basically said they've been sending a ton of replacement DVRs the past week or so. I asked why they were so quick to offer me a replacement (without even troubleshooting my reboot problem), and she just said as a good standing customer its easier to just request a replacement, especially since there has been widespread problems with the software upgrade.

So, I got the replacement DVR and its a Philips DSR708! I find it odd they didn't send the R10 since (I thought) it was the current model. I assume the Philips is basically the same thing as the Hughes I'm sending back!

I do not have a second hard drive in my Hughes, just a single 160gb. However, I had a 40gb lying around and I was successful with my first Tivo hardware adjustment. I switched it out so I can put the 160 in the new Philips. Worked perfectly, used the Hinsdale instructions. I was most worried about doing the linux commands correctly based on my situation, but it worked out fine and now I feel comfortable playing around with this stuff more in the future.

I assume I'll get the 6.2 upgrade again with the Philips... Question: When I go to upgrade the philips (probably will do in a couple weeks) will I be able to use the full 160gb now with the 6.2 software? Should I be using the special BootCD with large drive support that Hinsdale's instructions mention?

I'm hoping this summer to finally pick up the HD tivo receiver.

[stevel]

Yes, 6.2 can use the full 160GB. Yes, you should use the special boot CD with large drive support.

[rmassey]

I noticed a reboot today while watching a pre-recorded show. Boom , there it went to "powering up" My DTivo is a Hughes HDVR2 and I have a single 120 HD (Samsung 5400) which replaced the stock 40gb HD.

I find it hard to believe we all have bad hard drives. This seems like a 6.2 bug IMO. I really hate to do a clear and reset and loose all my recordings. So if I call and they offer a replacment, I'll have to put the stock 40 back in and it doesn't have 6.2 on it. Do they still ship out HDVR2s or will I get an R10 or philips or ???.

If this gets cronic, I will prob put the 40 back in, let it upgrade to 6.2 and see if the problem persists. If it does, I can swap it out with Direct for a new unit.

BTW, I also have a five year extended Warr with Circuit City. I already used it once when I got hit by lightning and it took out the Tivo. I wonder if CC will be able to provide an HDVR2 (my preference)?

[rminsk]

This seems like a 6.2 bug IMO.Every release there are complaints that "this new software killed my TiVo". In only one case has it been a bug with the software, 3.1.1d. There may be a problem with this release but so far it seems about the average number of complaints.

Your machine has rebooted once. I would not worry unless you start to see slow downs or more reboots.

[rmassey]

Every release there are complaints that "this new software killed my TiVo". In only one case has it been a bug with the software, 3.1.1d. There may be a problem with this release but so far it seems about the average number of complaints.

Your machine has rebooted once. I would not worry unless you start to see slow downs or more reboots.

Well, It has happened more than once on my machine. I only actually saw it happen once. I have noticed that I've lost the 30 sec skip a few times since the 6.2 upgrade, which indicates it has reboot.

Just becuase you may not have seen this problem on you DTivo, doesn't mean it isn't a bug affecting other users. Since many of us have reported the same exact problem just after 6.2 is released is a very clear sign of a sw bug.

[rminsk]

Just becuase you may not have seen this problem on you DTivo, doesn't mean it isn't a bug affecting other users. Since many of us have reported the same exact problem just after 6.2 is released is a very clear sign of a sw bug.I'm not saying that I have not seen it. Just from experience, we have this exact same thread every software release... even back in the 2.5.2 days. It is usually not a software bug... most of the time it is a bad hard drive. When new software gets installed the TiVo switches boot partitions. But it could be another problem...

[aristoBrat]

Since many of us have reported the same exact problem just after 6.2 is released is a very clear sign of a sw bug.
Maybe it is, maybe it isn't (although the only difference between our machines is the hardware -- the 6.2 software is the same on all of our machines), but I'm going to have to agree with rminsk that after every upgrade that DTV's done, there's been threads like this. <shrug>

[Stephen M. Smith]

I had this same reboot problem right after the 6.2 upgrade. My Tivo is un-modified except for a 120GB hd replacement. After 6.2, I had probably 8 or 9 spontaneous reboots over the next 2 days, but luckily, it stopped after that.

[shaady]

That's a good point that I forgot to make, makeen. This rebooting is the very first problem I've had with this unit (series2, for 2+ years). I had many other problems with my first TiVo (series1, for 2+ yrs also), stuttering, freezing, skipping, sound droppin out...etc.OK, no reboots in about a week. I hesitated in even posting this so as not to jinx myself.

We'll see... *fingers crossed*

[Abiding Dude]

I am getting the random reboot problem now too. It's rebooted 3 times since getting the 6.2 upgrade. I also have a Samsung 120gb drive in there. I wonder if the problem is related to this particular drive?

[Scott D]

My HDVR2 rebooted twice but I think it has to do with transferring a particular program. It seemed to have a glitch in that program whereas all other transfers worked just fine. No other notable times of reboot I know of unless they have logs of such an event.

[llurgy]

I witnessed a random reboot on my HDVR2 unit this AM at 1.30. I have had 6.2 on this unit since around the 21st of May and not seen any reboots until the early hours of this morning. It could have done it before then but I havent witnessed it doing so.
My Directivo has an upgraded 120 gig drive in it on which until this point has had nothing wrong with it whatsoever.

I cant bring myself to believe that it is a bad partion that is causing all of these reboots......just doesnt seem plausible that all these hard drives that have worked near perfectly until 6.2 are suddenly showing bad partitions....I mean, how likely is that? Really??
Sorry, just dont buy it!

What I do buy however is that there is some inconsistency in the 6.2 software that is causing these reboots.

Up until yesterday I was one of those people that could say that they had no problems with 6.2, after this AM I am now a person that IS having some sort of problem and for all I know my system could have been rebooting itself every morning at 1.30 since it got the software, I dont know, I am asleep at that time usually and I dont record at that time in the morning either.

What I do know is that until the reboot I considered my HDVR2 to be in perfect working order with no problems, no stuttering or clicking with all recorded programs playing back without incident or artifacts (except in thunderstorms).

Mandy

[aristoBrat]

120gb drives are apparently evil.

[rogue5]

Well, while trying not to jinx myself I have been reboot free since I erased my thumb recomendations and did a call in. That was about 3 days after I got 6.2 and 2 days after the reboots started, but the unit hasn't completed a call since, and it was hard before I made the call on the 24th of may. I keep getting service not answering as the error for the failure, I have tried a few of my numbers without any luck. I can do the test call but that is it. My HDTivo isn't having any problems calling so I don't know what it is...

[shaady]

OK, no reboots in about a week. I hesitated in even posting this so as not to jinx myself.

We'll see... *fingers crossed*Spoke too soon....another reboot last night...

[rmassey]

Maybe it is, maybe it isn't (although the only difference between our machines is the hardware -- the 6.2 software is the same on all of our machines), but I'm going to have to agree with rminsk that after every upgrade that DTV's done, there's been threads like this. <shrug>

OK, so if this is correct (bad partition causing reboots) and I want to fix this, what is the preferred plan of attack.

For both of my HDVR2s, I have the original 40 GB drives with 3.xxx on them from 2002. Should I try -

1) clear and restore the existing 120 GB drive - will this help at all or will I just see the problem again later on?

2) Replace the 120 with the original 40 GB, force a call, update it to 6.2.

3) clear and restore this 40 GB

4) reImage the 120 from the newly updated 40 GB with 6.2.

Will any of this get me past the bad spot on the new boot partition? I'm getting tired of random reboots and lack of relibility. I am willing to swap drive, reimage, clear/Restore, but I am not going to buy new 120 GB drives and I'd really not like to just go back to the stock 40 GB drives for any length of time.

[rmassey]

bumpola - anyone ?

[Abiding Dude]

I haven't had any issues since I last posted (several days back). I wonder if there are some house-keeping chores that need to be performed after the upgrade takes place that may interrupt the normal operation of the unit. I will keep my fingers crossed and hope it was just a fluke :)

[stevel]

I too haven't seen any spontaneous reboots in the past few days. In addition to running diagnostics on the disk, I forced an MFS check just for good measure. (Was amused to get the "installing new software" screen instead of the usual GSOD for this.) I have no idea if this made a difference or not.

[swkenney]

I have a Hughes SD-DVR120 100 hour DTV. It started rebooting after 6.2 was installed. Service tech had me force a call to perhaps complete the installation. It has not rebooted since.

Actually, I had already forced a call once after the install, so I don't know why the second call would do anything.

[rogue5]

I think the call did have something to do with mine cause since the call I ahve been good to go. Although now I have had to force the last two calls cause my system kept gettting failed calls each time it tried, not sure if it was just that the phone number was busy or if it was a problem with my unit. Oh and I have a hughes sd-40 (non-tampered) and I never had a problem with it until I got the download. Knock on wood I won't have anymore problems!

[jfuredy]

I too am now experiencing the random reboot problem on my unit that received 6.2 from satellite, but my reboot is accompanied by video stuttering and pixelating prior to the reboot.

I am willing to consider the possibility that the "new" boot partitions could have bad sectors in them. Does the TiVo software repair identified bad sectors on the hard drive each time it reboots? I am thinking that this would be the only way that the problem would just "go away" all by itself.

Does anyone have any knowledge of what the TiVo does during the reboot?
Joe Furedy
Hughes SD-DVR40 running 6.2 (from AlphaWolf's 62small.mfs) on 200GB with HMO (no problems yet...)
Hughes SD-DVR40 running 6.2 (from satellite) on 40GB + 137GB (video problems with reboots)

[Dan Collins]

IMO,

Being blunt = "those aforementioned are virtual dinosaurs at this point and continually have problems" :up:

Being [rude, condescending] = "and those models suck too" :down:

:D
And both comments contributed soooo much to the advancement of the OP's problem. :rolleyes:

That is the real problem itgirl, you bomb in with sarcastic and/or rude comments that are pointless, and contribute nothing to the process. There are a half dozen DirecTV CSRs that post regularly on my board and they are generally helpful and friendly. You have been neither in any thread in which I have seen you post. If the attitude you present here carries over into your work, I sure hope I never have to talk to you.

[stevel]

Yes, the TiVo does try to do some disk structure repair during a boot - you can see this if you have access to the kernel log or have hacked to enable a serial console output.

Try this. Reboot the TiVo and wait for the green power light to change to yellow (it will be a minute or so before it does this.) At that time, press Pause on the remote and the record light will also change to yellow. Now press 58 on the remote. You SHOULD get either a "green screen of death" (misnamed), or perhaps a message that new software is being installed. Let it sit for a while - this may take 20 minutes or several hours. What you have done is request a check and repair of the MFS partitions. It will resume normally when it is done.

[Human123]

Yes, the TiVo does try to do some disk structure repair during a boot - you can see this if you have access to the kernel log or have hacked to enable a serial console output.

Try this. Reboot the TiVo and wait for the green power light to change to yellow (it will be a minute or so before it does this.) At that time, press Pause on the remote and the record light will also change to yellow. Now press 58 on the remote. You SHOULD get either a "green screen of death" (misnamed), or perhaps a message that new software is being installed. Let it sit for a while - this may take 20 minutes or several hours. What you have done is request a check and repair of the MFS partitions. It will resume normally when it is done.

My Tivo is 6.2 with ftp and telnet enabled. It is rebooting randomly at night and leaving partial recordings. This seems to happen 2 to 3 times a night.

I am considering doing the above, but first I am wondering if I can be pointed toward logs files to look at and how do I look at them. Can you look at them while on the Tivo without Tivoweb?

Thanks for any help with viewing log files

[stevel]

Sure. Ftp to the TiVo and copy file /var/log/kernel (in ASCII mode) back to your PC and peruse it there.

[Human123]

In the kernel log I keep seeing this line and then the date reverts to Jan 2 then goes through some more logging lines and sets the system time back (Reboot?)

Jun 9 16:28:08 (none) kernel: Tmk Fatal Error: Thread HandleDataChanged <7716>: unexpected signal 10
Jan 2 00:00:15 (none) kernel: klogd 1.3-3, log source = /proc/kmsg started.

Any advice? Or can I provide better info from other log files?
Thanks


Edit

This appears to be a complete log of an event

Jun 9 16:28:08 (none) kernel: emulate_load_store_insn: sending signal 10 to myworld(7716)
Jun 9 16:28:08 (none) kernel: $0 : 00000000 fefefeff 00c74774 00000000 deadbeef 5ed2d21c 5ed23814 00000000
Jun 9 16:28:08 (none) kernel: $8 : 00000000 00000000 2ae421cc 00000002 00000000 ee6b2800 3e164e81 fa860000
Jun 9 16:28:08 (none) kernel: $16: deadbeef deadbeef 5ed2d21c 5ed3ebc8 00000004 100d4f00 00000001 5ed2d21c
Jun 9 16:28:08 (none) kernel: $24: 00000000 00cd8ab0 1006d910 7b5ff150 00030021 00c747b8
Jun 9 16:28:08 (none) kernel: Hi : ecbba7e2
Jun 9 16:28:08 (none) kernel: Lo : ec074567
Jun 9 16:28:08 (none) kernel: epc : 00cd8ad8 Not tainted
Jun 9 16:28:08 (none) kernel: Status: 8001bc13
Jun 9 16:28:08 (none) kernel: Cause : 00000010
Jun 9 16:28:08 (none) kernel: 8001e9fc 8001eac0 80022bb4 800215b4 8001d6b8 00cd8ad8
Jun 9 16:28:08 (none) kernel: 00cd8ad8 00c747b8 00c39e24 013bbbc0 013bb1b8 00c388c0 00c398d0 00c350e0
Jun 9 16:28:08 (none) kernel: 00c3105c 00c30f6c 00c22898 00c337f0 00c70e0c 00c70910 00c72040 00c71714
Jun 9 16:28:08 (none) kernel: 00c70bc4 00c6ffcc 00c62d54 00c5a634 00c613bc 00c6ced0 00c6c97c 00c6c418
Jun 9 16:28:08 (none) kernel: 00c6b940 00c6b790 0123e850 013a706c 013ce190
Jun 9 16:28:08 (none) kernel: Tmk Fatal Error: Thread HandleDataChanged <7716> strayed!
Jun 9 16:28:08 (none) kernel: pc 0xcd8adc status 0x8001bc13 cause 0x000010 bva 0xdeadbeef hi 0xecbba7e2 lo 0xec074567
Jun 9 16:28:08 (none) kernel: R00 0x00000000 R01 0xfefefeff R02 0x00c74774 R03 0x00000000
Jun 9 16:28:08 (none) kernel: R04 0xdeadbeef R05 0x5ed2d21c R06 0x5ed23814 R07 0x00000000
Jun 9 16:28:08 (none) kernel: R08 0x00000000 R09 0x00000000 R10 0x2ae421cc R11 0x00000002
Jun 9 16:28:08 (none) kernel: R12 0x00000000 R13 0xee6b2800 R14 0x3e164e81 R15 0xfa860000
Jun 9 16:28:08 (none) kernel: R16 0xdeadbeef R17 0xdeadbeef R18 0x5ed2d21c R19 0x5ed3ebc8
Jun 9 16:28:08 (none) kernel: R20 0x00000004 R21 0x100d4f00 R22 0x00000001 R23 0x5ed2d21c
Jun 9 16:28:08 (none) kernel: R24 0x00000000 R25 0x00cd8ab0 R26 0x0001a338 R27 0x00000000
Jun 9 16:28:08 (none) kernel: R28 0x1006d910 R29 0x7b5ff150 R30 0x00030021 R31 0x00c747b8
Jun 9 16:28:08 (none) kernel: Paste the following into a shell to get a backtrace...
Jun 9 16:28:08 (none) kernel:
Jun 9 16:28:08 (none) kernel: bt -t /tvbin/tivoapp <<END_OF_BT
Jun 9 16:28:08 (none) kernel: read 0x2aaa8000 /lib/ld.so.1
Jun 9 16:28:08 (none) kernel: read 0x2ab04000 /lib/libutil.so.1
Jun 9 16:28:08 (none) kernel: read 0x2ab48000 /lib/libdl.so.2
Jun 9 16:28:08 (none) kernel: read 0x2ab8c000 /lib/libpthread.so.0
Jun 9 16:28:08 (none) kernel: read 0x2abe8000 /lib/libm.so.6
Jun 9 16:28:08 (none) kernel: read 0x2acb0000 /lib/libc.so.6
Jun 9 16:28:08 (none) kernel: 0x00cd8adc 0x00c747b8 0x00c39e24 0x013bbbc0 0x013bb1b8 0x00c388c0 0x00c398d0
Jun 9 16:28:08 (none) kernel: 0x00c350e0 0x00c3105c 0x00c30f6c 0x00c22898 0x00c337f0 0x00c70e0c 0x00c70910
Jun 9 16:28:08 (none) kernel: 0x00c72040 0x00c71714 0x00c70bc4 0x00c6ffcc 0x00c62d54 0x00c5a634 0x00c613bc
Jun 9 16:28:08 (none) kernel: 0x00c6ced0 0x00c6c97c 0x00c6c418 0x00c6b940 0x00c6b790 0x0123e850 0x013a706c
Jun 9 16:28:08 (none) kernel: 0x013ce190
Jun 9 16:28:08 (none) kernel: END_OF_BT
Jun 9 16:28:08 (none) kernel:
Jun 9 16:28:08 (none) kernel: Tmk Fatal Error: Thread HandleDataChanged <7716>: unexpected signal 10
Jan 2 00:00:15 (none) kernel: klogd 1.3-3, log source = /proc/kmsg started.
Jan 2 00:00:15 (none) kernel: Cannot find map file.

[stevel]

I have found that my 6.2 system is stable if I don't "play" with it through TWP. But if I do something such as try to add a season pass through TWP, I can crash it readily. Which I did last night - sigh. It had been up for five days (since I had deliberately rebooted it) up until then.

[rmassey]

Yes, the TiVo does try to do some disk structure repair during a boot - you can see this if you have access to the kernel log or have hacked to enable a serial console output.

Try this. Reboot the TiVo and wait for the green power light to change to yellow (it will be a minute or so before it does this.) At that time, press Pause on the remote and the record light will also change to yellow. Now press 58 on the remote. You SHOULD get either a "green screen of death" (misnamed), or perhaps a message that new software is being installed. Let it sit for a while - this may take 20 minutes or several hours. What you have done is request a check and repair of the MFS partitions. It will resume normally when it is done.

Thanks Steve, I am trying this right now (pause, 58). I also reinstalled the original 40 gb, forced a few calls and got it upgraded to 6.2. if the check and repair doesn't do the trick, I will reimage the Samsung 120 from the updated 40 and see if this fixes the problem. I'm hoping the check and repair works, as I'd rather not loose my recordings, season passes, etc.

Thanks for the tip.

[NatasNJ]

Add me to the list of my first random reboot with my HDVR2 unit about 2-3 weeks after my 6.2 upgrade.

Only one so far. Will monitor closely.

[rmassey]

Thanks Steve, I am trying this right now (pause, 58). I also reinstalled the original 40 gb, forced a few calls and got it upgraded to 6.2. if the check and repair doesn't do the trick, I will reimage the Samsung 120 from the updated 40 and see if this fixes the problem. I'm hoping the check and repair works, as I'd rather not loose my recordings, season passes, etc.

Thanks for the tip.

No luck, I tried a pause/58, it began the "loading new sw" routine, but I am still getting the reboots. I've done this about three times so far.

I'm gonna pull the 120 drive, run spinrite on it and reimage it, and see if this cures my ills.

[Dan Collins]

I'm wondering if the bitmap tree for a 120GB drive is taking up more memory than is available under 6.2? This would be particularly true if the original unit had a 40GB drive, and so those partitions have a 1MB allocation size.

[stevel]

Well, I have a 300GB drive that is running fine (if left to its own devices) under 6.2.

[Dan Collins]

And I have a 250Gb and a 120GB, but I ran mfsadd -x -r 3 /dev/hdX...which set my allocation size to 8Mb. The mfsadd default is 4MB for expansion partitions, but I don't think it changes the origianl partitions.

Just a thought....

[makeen]

No reboots for about a week now after 3 weeks of on and off frequent and infrequent reboots. I think the problem seems to go away for at least some of us.

Good luck to all.


I've had this unit since Dec2003 Model Samsung SIR-S4120R never upgraded or hacked.

[spartanstew]

I've had 6.2 for about 2 weeks and today I started getting reboots. My unit is unmodified. It rebooted late this afternoon (3PM) while my wife was watching a recorded show. About 30 minutes ago (7PM) it did it again while we were watching live TV (yes, we do that occasionally). I guess I'll call DirecTV tomorrow and see what the odds are of getting a new unit (maybe an R10 to match my other one).



Stew

[Abiding Dude]

Darn-it, after 2 weeks without a reboot I started getting them again. I thought maybe it was just a once-in-a-couple-weeks thing, but I got another one this afternoon. In checking the System Information screen, I see that the reboots seem to appear around the time that there is Indexing activity going on (although I'm not sure what that is). I keep hoping that the problem will somehow magically resolve itself :).

[alan]

I deleted all my Thumbs Ratings and I haven't had a problem since that time. It was rebooting several times per day. It's not rebooting anymore.

[rogue5]

Did the same thing as Alan, and have been reboot free for over a month. I posted this earlier but i don't know if anyone tried it then.

[skinnyjm]

5 weeks now with 6.2 on both, things seem to be going well.
Only had to reboot once since 6.2 installation. (KNOCK on wood) :D
I would suggestion a reboot to anyone having issues,
but you all knew that already. :up:
:)

[alan]

Did the same thing as Alan, and have been reboot free for over a month. I posted this earlier but i don't know if anyone tried it then.
Rogue5, your post right after mine a long time ago that suggested this is the reason that I tried it. So I have to say thank you for your suggestion. I thought I'd wait to see if it worked, but when it did wait so long I forgot to come back and say so.

(Here's my "Debugging the black box" take on the situation) My wild a** guess is that the thumbs data objects for the new version is kept in a different format or something and the new version should have had a method for converting the old thumbs data to the new format. Just a guess, since zapping the thumb ratings seemed to fix the reboot problem.

An interesting test would be to see if someone that got the new version and hasn't had a problem has the suggestions turned off. If they turn suggestions on, I wonder if they would start having a problem? Of course, why would they read this thread and try it? :rolleyes:

I guess the other way around would be an interesting test too. What if someone that has reboot problems turns suggestions off, I wonder if it would stop the rebooting. It would be an interesting test. Of course it might not be a valid test, but maybe it would mean something. (Like stop trying to debug a black box). :)

Oh well, rogue5's suggestion of deleting the thumbs ratings seemed to work for me. So, Thanks rogue5! :up:

[SteveInNC]

I'm not sure this exactly what you mean, but I have a Hughes and have had suggestions turned off for at least six months if not a year. Since 6.2, I get random hangs as described elsewhere. One of the stronger opinions is that this is a function of the upgrade causing the DVR to use a new area on the disk which may have bad blocks. I'm still running with the original 40 hr disk, so this is sufficient motivation for me to upgrade now. Unfortunately, all of the Best Buys around here are sold out of the WD 160s that were on sale.

[alan]

I'm not sure this exactly what you mean, but I have a Hughes and have had suggestions turned off for at least six months if not a year. Since 6.2, I get random hangs as described elsewhere. One of the stronger opinions is that this is a function of the upgrade causing the DVR to use a new area on the disk which may have bad blocks. I'm still running with the original 40 hr disk, so this is sufficient motivation for me to upgrade now. Unfortunately, all of the Best Buys around here are sold out of the WD 160s that were on sale.
Even though you don't use suggestions, have you tried dumping the thumbs data (ratings and suggestions) on your TiVo? If you just turned off Thumbs data, you might still have some. My guess would be that the thumbs data gets generated anyway even though suggestions are off.

If you really think it's a disk problem, you could also try the suggestion above by stevel that's quoted below. Have you tried that?

Yes, the TiVo does try to do some disk structure repair during a boot - you can see this if you have access to the kernel log or have hacked to enable a serial console output.

Try this. Reboot the TiVo and wait for the green power light to change to yellow (it will be a minute or so before it does this.) At that time, press Pause on the remote and the record light will also change to yellow. Now press 58 on the remote. You SHOULD get either a "green screen of death" (misnamed), or perhaps a message that new software is being installed. Let it sit for a while - this may take 20 minutes or several hours. What you have done is request a check and repair of the MFS partitions. It will resume normally when it is done.

[rogue5]

Thanks for the pat on the head Alan ! :) I am not to familiar with the inter workings of the TIVO software so I can't weigh in on your theory. I think it my be a combination of your theory and the harddrive bad sections only because not everyone is getting the exact same symptoms. Some are getting random reboot while others are getting hangs or complete crashes which leads me to beleive that there might be multiple issues. Again this is just my speculation cause I am not a software guy. :D Well my suggestions for anyone else having this problem is to delete the thumb rating completely regardless of wheather they are on or not. If the problem countiues then looking into the HD or a possible bad load of the 6.2 software. Just on a side note I also forced a call after I deleted the thumb rating, I don't know if you did the same or not Alan but that is all I did and haven't had a problem since!

[Declan]

I would like to put my 2 cents in. I have never had the suggestions turned on the life of my Series 2. I learned with my Series 1 that I didn't like the auto record stuff. Mine not only locks up on occasion but also reboots.
I find that if I keep very little recorded then it doesnt happen often. I work in the Computer field and yes I know that a lot of people say that and I know it means nothing to anyone but I belive it is hard drive related. I bought Series 2 from Weaknees already upgraded with a 120gb drive. I have since bought another drive and I am waiting to swap the drive.

Any comments.

Declan
:eek: :eek: :eek:

[rogue5]

Well D,

I didn't have the auto record set on mine either, I have a series 2 by the way, but I did have the thumb ratings on. Like I said earlier, once I cleared that and made a new call I have been good to go. The more I read here the more I feel there are multiple issues causing this reboot problem, at least IMHO.

[theCheese]

Checking in...
HDVR2 w a WD120 for 2+ yrs.
Never a problem, but getting 2-3 reboots a day since 6.2.
Will no longer connect on a forced call either.
Suggestions always turned off.

Clearing thumbs data now to see if it fixes it.
I'll report back in a week or so on sucess/failure.

[mzgig]

Well, I'm not getting random reboots like everyone else, but I can't connect since the 6.2 software. DTV claims they've had "no problems" with the new software. I guess I should insist they send me a new receiver, based on what I've read above. But I've only had my new hard drive since August and I upgraded to the larger one. I'm sure they will send me the standard 40-hour drive. :(

[rogue5]

mzgig,

Try clearing the thumbs, I couldn't get a call through till I cleared the thumbs. It took me a little while and a few change of numbers till I got a call through but once I did I haven't had any issues (looks for some real wood to knock on). You can try that before having to scrap the whole TIVO. I have seen that some people have gotten replacements for this issue futher up the thread but I would remove the new HDD and update the old one prior to returning it. :D

[fishboy]

Wow. I really wish I had seen this suggestion about clearing the "thumbs" data before mine crashed and I got a new one. Now Im in another 1 year contract for another unit. At least I didn't have to pay for it... But now I've lose any leverage in getting any additional upgrades to my account for another year.

[austin_g]

Here is the answer to the rebooting problem.............
...
....
.....
.....wait for it....

Ok here it is. Do a hard reset. This is done by disconnecting the satalite in cable from the back of the receiver. Then unplug the receiver from the power outlet. Wait 15 seconds. this part is very important. wait a full 15 second and then plug only the power cord back into the outlet, not the sat cable quite yet. The receiver will now reset. Now wait another 15 seconds while the receiver resets and then reconnect the satalite in cable to the receiver. Now after the receiver aquires all the gude data, run a clear and delete everything. This could take several hours. This will now solve the issue of the receiver resetting itself. Of course you will lose everything you have on it but it WILL solve the issue.

[greg99]

This evening I noticed that I no longer had access to HBO/Showtime/Cinemax. I had an x721 error, so I tried to go to the messages to see if I had received any communications.

The machine hung for several minutes simply showing the background but no messages. I had to unplug the (Philips) unit. When it finished rebooting, I had my channels back but attempting to review messages resulted in another hang.

I've had issues with it hanging in the menus a number of times since 6.2 was d/led.

Despite everything they did, 6.2 was clearly not ready for prime time.

Greg

[MighTiVo]

Mine has also been rebooting, probably twice a day. I finally decided to visit the forum to see if others had the problem.

Anybody call DTV? What was their response.

I have too much recorded on this DVR to clear and delete everything.
Too bad MRV isn't available so I could simply transfer to another DVR!

EDIT:
OK, after 3 reboots in one hour, I called DirectTV and they suggested clear and delete everything. I said I wasn't willing to do that because I would lose all my programming. To that they offered sending a replacement unit. How does that help I still lose the programs!
I suggested that ideally the system would support MRV so I could transfer the programs and although the lady is probably misrepresenting the facts she did say they were working on getting the TiVo upgrade out that alows you to transfer programs to the computer. Note I didn't say anything about transferring to the computer, she volunteered that on her own.

Still no help for me now, although she did note my account and said I could call in for a replacement later if I decided to. Perhaps I will try for a HD DVR as a trade in next time I call...

[MighTiVo]

Try this. Reboot the TiVo and wait for the green power light to change to yellow (it will be a minute or so before it does this.) At that time, press Pause on the remote and the record light will also change to yellow. Now press 58 on the remote. You SHOULD get either a "green screen of death" (misnamed), or perhaps a message that new software is being installed. Let it sit for a while - this may take 20 minutes or several hours. What you have done is request a check and repair of the MFS partitions. It will resume normally when it is done.


If I understand correctly that should not delete any recordings, right?

[jfuredy]

If I understand correctly that (the procedure originally posted by stevel) should not delete any recordings, right?

That is correct, the "Pause 58" procedure will not delete anything from your TiVo. I did do this procedure on my Hughes DVR-40 and it definitely helped. I have not checked the log, or whatever other method you guys are using to determine when you get reboots, but my shows are no longer interrupted by reboots.

Thanks for the advice stevel!
Joe

[MikeHerbst]

I deleted all my Thumbs Ratings and I haven't had a problem since that time. It was rebooting several times per day. It's not rebooting anymore.

Seen several people who've reported success with this, so I'd love to try it. One question: HOW DO YOU DO IT!?!?!

Is this only for people who are getting to a prompt somewhere, or can a "regular" user do this too? Searched through every menu I could think of and the only thing I can find is the "Record Suggestions On/Off" screen, but nothing about deleting the thumb data, etc...

Help!

[llurgy]

Mine is still randomly rebooting - Just had another one this past hour. I think that my receiver is mainly doing it's reboots in the middle of the night a 5 times to date I have sat down to watch a program that I left in the middle and it has gone all the way back to the beginning again, so I can tell it has had a reboot.

Up to now I havent lost any recordings but it is bound to happen sooner or later.

Mandy

[MighTiVo]

Seen several people who've reported success with this, so I'd love to try it. One question: HOW DO YOU DO IT!?!?!

Is this only for people who are getting to a prompt somewhere, or can a "regular" user do this too? Searched through every menu I could think of and the only thing I can find is the "Record Suggestions On/Off" screen, but nothing about deleting the thumb data, etc...

Help!


Go to Messages & Settings, Restart Recorder, Clear Thumbs.

I did the pause 58 last night, didn't get the GSOD, instead got installing new software.
Still rebooting...

Will try clearing thumbs today.

[BigBadBob]

Clearing thumbs didn't help me. Every indication is that there is a sw bug causing some process to consume CPU time to the exclusion of others. Video stops and starts, it takes forever to go through menus, etc. Also, experience tells me it is extremely unlikely that there is a sudden rash of disk problems even if the update accesses different partitions. Disks just don't work like that.

Possible cause might be problems created when I upgraded to the larger disk back when.

I'll try various other resets but I'll probably have to put in the original disk and let it upgrade and see what happens.

DTV really knows how to make friends! :mad:

Edit: The pause 58 procedure isn't for the faint of heart. I did it and it went through a screen saying it was installing a software update, rebooted, got to the "aquiring information from satelites", crashed, rebooted, and now I'm at what I guess is the "green screen of death" where it says "a severe error has occurred" and tells me not to touch ANYTHING while it tries to repair itself. We'll see. :eek:

And now it is in a loop of reboot--almost there--GSOD--repeat. :( I'm supposed to give it three hours of this, but I'm not sanguine that anything good will come of this.

Update: According to CSR, I was supposed to give it 24 hours of this then reboot and it would all be fine. Of course it isn't. Unit is toast. Don't recommend pause 58 procedure. Still trying to find the old HD from a couple of years ago. May end up just buying a new unit. Booooooo! :mad: :mad: :mad:

[spartanstew]

Here is the answer to the rebooting problem.............
...
....
.....
.....wait for it....

Ok here it is. Do a hard reset. This is done by disconnecting the satalite in cable from the back of the receiver. Then unplug the receiver from the power outlet. Wait 15 seconds. this part is very important. wait a full 15 second and then plug only the power cord back into the outlet, not the sat cable quite yet. The receiver will now reset. Now wait another 15 seconds while the receiver resets and then reconnect the satalite in cable to the receiver. Now after the receiver aquires all the gude data, run a clear and delete everything. This could take several hours. This will now solve the issue of the receiver resetting itself. Of course you will lose everything you have on it but it WILL solve the issue.


This has been mentioned already in this thread. It doesn't seem to work. It's one of the first things I tried.

I finally called Directv and told them about the problem. They sent me through a few hoops (try this, try that) and then she told me she's send me a new unit. 2 days later a brand new Philips 70 hour unit was sitting on my door step. I packed up my 35 hour HDVR2 and sent it back. That was about 2 weeks ago and I haven't had any reboots with the new unit and doubled my storage capacity for free. Thanks D*



Stew

[theCheese]

Update ... Checking in....
Cleared Thumbs and still have reboots 2-3 times a day.
(Thumbs took about an hour to clear.)

[brad639]

I was getting constant pauses/hangs and reboots for the past week,

So on friday I ventured to try the pause 58,

Well over the weekend, NOT ONE pause, hang, or reboot,

Before the pause 58 My tivo would not read Messages, it would just hang and not do anything,

when the pause 58 was done, messages could be read, and everything else worked fine,

Hopefully this will last....

[MighTiVo]

I was getting constant pauses/hangs and reboots for the past week,

So on friday I ventured to try the pause 58,

Well over the weekend, NOT ONE pause, hang, or reboot,

Before the pause 58 My tivo would not read Messages, it would just hang and not do anything,

when the pause 58 was done, messages could be read, and everything else worked fine,

Hopefully this will last....

Although my reboots continued for a while after the clearing and the pause 58 they seem to have stopped.
I hadn't tried messages again until I saw your message.

Nope, still locked up!

Any other ideas for messages?
Not that I want to read them, but I would like to remove the need to reboot in case of accidental selection.

[richierich]

Here is the answer to the rebooting problem.............
...
....
.....
.....wait for it....

Ok here it is. Do a hard reset. This is done by disconnecting the satalite in cable from the back of the receiver. Then unplug the receiver from the power outlet. Wait 15 seconds. this part is very important. wait a full 15 second and then plug only the power cord back into the outlet, not the sat cable quite yet. The receiver will now reset. Now wait another 15 seconds while the receiver resets and then reconnect the satalite in cable to the receiver. Now after the receiver aquires all the gude data, run a clear and delete everything. This could take several hours. This will now solve the issue of the receiver resetting itself. Of course you will lose everything you have on it but it WILL solve the issue.

It is interesting that you just became and member and have only had 4 posts and you are so knowldegeable about doing a hard reset for this unit. Where did you learn this technique? Do you work for Tivo or Directv?

[su_A_ve]

FYI,

An HDVR2 with a 120 GB (no other mods). Got 6.2 over a month ago.

I had one reboot (out of the blue) serveral months ago.

This past Sunday, it was at 'Almost there'. A few hours later was at the same place. Unplugged/waited/replugged and was fine since.

Hope drive is not starting to go, though I'll be pulling stuff out of it soon...

[Abiding Dude]

Mine is still rebooting every one in a while. It does seem to happen close to the time that Indexing is taking place (whatever that is). It seems strange that this seems to be happening to mostly 120gb drives, but perhaps that is only because these drives are all getting old at the same time. I had no problems before the upgrade. I am sorta hoping they have an upgrade soon so the partition-switch will happen and hopefully the problem will go away. I was hoping to get more than 2 years out of my current drive :)

[edadave]

My HDVR2 started rebooting randomly about once per day when it got the 6.2 upgrade. Never happened once in the preceding year. DTV said it was probably a bad drive, but to first try reset, then try clear everything. Did those - no improvement.

DTV then sent a replacement unit and behavior is the same. Unit is plugged into a UPS.

Two different HDVR2s and a UPS - can't be the hardware, so what's left? There must be some unlikely combination of events that expose the software bug and cause the reboot given that many owners never see it. I work in software QA and this looks, smells, and tastes like an intermittant and hard to reproduce software bug.

Has anyone changed from an HDVR2 to another box and seen this problem go away? There is always a chance it only affects certain hardware. Otherwise, I'll give DTV/Tivo a couple more months to fix this, and otherwise reluctantly switch to DISH.

For those who say they never get a reboot - are you sure? If you have the 30-second skip programmed in and it is retained, your unit has not rebooted. Otherwise, you may never know unless you happen to be watching when it happens or see a seven minute gap in a recorded show.

[rmassey]

I deleted all my Thumbs Ratings and I haven't had a problem since that time. It was rebooting several times per day. It's not rebooting anymore.


Go to Messages & Settings, Restart Recorder, Clear Thumbs.

My DTivo was rebooting every day. I cleared the thumbs ratings and it has stopped rebooting.

So much for the theory that a secondary boot sector has a bad spot causing reboots. Unless, of course, the thumbs data is stored on this bad spot of the boot sector.

[Mike_TV]

OK, one of my upgraded units (added a 120 GB drive) rebooted twice while watching a saved program since the 6.2 upgrade. This never happened with the older version of the software. I'll have to start making a log and see how frequently this happens.

[23goober23]

I have a HNS SD-DVR40 and i have had it replaced by dtv for the same prob. they sent me the same kind. i've tried to clear the thumbs ratings and they stay deleted for a lil while, but some how they come back. i never use those buttons so i dunno how!!!

[the new guy]

I never use the thumbs buttons, either. It appears, however, that any program I record (manual or season pass) is automatically assigned one thumb up.

Both my units were rebooting daily or more until I ran the MFS cleanup on them. Now I get one reboot every 3-4 weeks.

Tim

[edadave]

My 2-3 times per day reboot, on two different units, stopped cold when I took away an IR emitter from a remote control extender. Seems the 6.2 software either has an IR Easter Egg to reboot from a sequence that matches random IR noise, or with the 6.2 speed-up, the unit is more susceptible to IR glitches. I'll experiment with different RF receiver and IR emitter locations, or get a higher-end extender. I have a Terk Leapfrog that worked perfectly before 6.2. It still works, but surprisingly triggers reboots.

For anyone having reboot problems - check to see if you have any unexpected IR sources around, or just for an experiment, cover up the IR receptor when you don't need it.

[rmassey]

My 2-3 times per day reboot, on two different units, stopped cold when I took away an IR emitter from a remote control extender. Seems the 6.2 software either has an IR Easter Egg to reboot from a sequence that matches random IR noise, or with the 6.2 speed-up, the unit is more susceptible to IR glitches. I'll experiment with different RF receiver and IR emitter locations, or get a higher-end extender. I have a Terk Leapfrog that worked perfectly before 6.2. It still works, but surprisingly triggers reboots.

For anyone having reboot problems - check to see if you have any unexpected IR sources around, or just for an experiment, cover up the IR receptor when you don't need it.

Interesting.... I have two HDVR2s, the one in my HT was doing reboots and I use an X10 powermid to control it from the master BR. The other one in the FR has not suffered the reboots and does not use a powermid. Although since I cleared the thumbs ratings, the rebooots have stopped and I still have the powermid in use.

[the_scotsman]

I have 2 DSR7000 machines which both received the 6.2 update after re-activating them (I was in an apartment for 5 months). Prior to 6.2 both machines we rock solid, now both are suffering from random reboots.

I've tried a couple of the suggestions here but nothing has helped so far. As soon as I get a chance I'm going to install some large HDDs to see if that helps.

Paul

[richierich]

Use Maxtor 300 gig Quickview hard drives. That is what Weaknees recommends and they should know since they are in the business of upgrading Tivos and adding hard drives.

[the_scotsman]

Thanks, but I'm going to use some 160GB drives from my connectstor II until I'm sure that this will fix the reboot problem. I'll restore the previous version if it doesn't. Until then my trusty SAT-T60s will be my primary machines.

Paul

[SteveInNC]

I think it's interesting that there appear to be two main problems since the 6.2 upgrade: some (like me) get hang problems, where in the midst of running, the screen just hangs up, often with a still image. Reboot is the only out. Then there is another class of problem where the unit arbitrarily reboots itself (at least that is how it's described). While I can believe that a bad block is now stepped on since the upgrade supposedly caused a partition change, I'm amazed at how many people are reporting problems specifically with *this* upgrade. I know my unit (Hughes) has been upgraded in the past without any ill effects. The coincidence of the number of failures makes me think that there is some intermittent OS bug that just hasn't been nailed down yet, maybe something like a memory leak or a dangling pointer that eventually gets out of hand. Sometimes it causes a reboot, sometimes a hang.

If anyone here has upgraded a drive, while you were poking around there, have you looked to see if the Linux syslog has any "panics" listed?

[richierich]

I got the "f" download and my unit started pixellating, freezing, etc. I ran SpinRite and that corrected it. However, I find it amazing that there could be so many alternate inactive partitions waiting for the next download that just happen to be residing on a bad or marginal sector. However, when SpinRite rewrites the data it works just fine. I had 3 bad sectors removed and after that it ran perfectly, in fact the guide and other functions worked a little faster than before.

When the picture freezes it is not reading any more video and is just displaying the last video image that was correctly read. When it reboots it is trying to correct an unrecoverable error such as running out of memory to be able to function so it reboots trying to recover space that was used temporarily and should have been freed up or the CPU gets into an unrecoverable logic loop. This unit should have had a faster processor to handle the extra video data being processed. Maybe it is the way that the download writes the data. SpinRite can write in a lower level way so it facilitates good reads.

[Rych6896]

I have a unmodified SD-DVR120 which finally got the upgrade last weekend. (I have Callvantage and I just set up PPP. ) Anyhow I've been getting reboots all week. I did the reset thumbs thing without success. Luckily I have the DTV protection plan and will call tonight to get it swapped out.

[Rych6896]

Dam! Directv comes through hard! I called them at 6PM Friday night. they said they'd ship me a new one within 2 business days. I come home today at 1pm and the new unit is sitting in my driveway. How can I complain about 18 hour turnaround? Hopefully the Samsung sir-s412020r is a good unit.

:D :D

[Rych6896]

Oh well. I got a lemon. It's stuck on Welcome. Powering up...

[richierich]

Oh well. I got a lemon. It's stuck on Welcome. Powering up...

You could open it up and see if the hard drive's IDE & Power Cable are securely fastened. That is normally the problem and would only take 10 minutes to take off the top with a #10 Torx wrench (5 screws) and then look at the cables. Sometimes they come loose during shipment or when moved around.

[Rych6896]

Yeah, I should have thought of that before calling DTV. My guess is the brown Santa will have a present for me when I get home today.

[richierich]

The only problem with that is that you lose all your recordings, settings, SPs, WishLists, Favorite Channels, etc. and you may get a unit that also has a bad WD drive or HDMI port. I would rather open it up and see if it is a quick fix.

[edadave]

Just following up that moving an IR emitter made the difference for me. I had a finger-tip emitter in front of the IR window on my HDVR2 and was getting 2-3 reboots per day. I replaced it with a table-top emitter ten feet away and have had no reboots in over a week. The finger-tip emitter worked fine prior to the 6.2 update, but 6.2 is apparetly more susceptible to IR glitches.

[veener88]

I just started to have this problem I noticted last week but I only had it once a week at most. Well Monday when I was home it rebooted twice on my but I have not had it do it since but that is only with about 3 hours a night of it being on. I will see how it does this weekend and go from there.

D* just gave me a great deal on the HD receiver so I am not sure if they will send me out a new unit or not at no charge. I have the Huese receiver and it is about 1.5 years old.

[kayson712]

I have a HNS SD-DVR40 upgraded with second 120GB drive that was solid before 6.2. Since then reboots were occurring as frequently as every 45 minutes and averaged 4 to 5 per day. As you can imagine, this wasn't very much fun when I was trying to save ten episodes of "Roswell" to my DVD recorded in case I got to the point where I was ready to do a complete clear and delete everything.

Customer Service had me pull my power cord out of my surge protector and go straight into another wall outlet - of course this didn't work. Also tried the pause 58 with no luck.

As suggested here I reset all of the Thumbs ratings and so far no resets for the last two days. Hopefully this will last.

[el Dragon]

I just got an R-10 it came with 6.1... IS the R-10 also going to get 6.2 update...

[Davidec]

....As suggested here I reset all of the Thumbs ratings and so far no resets for the last two days. ....
How does one do this type of reset? Did I miss the instructions in the thread?

--David

[aristoBrat]

I just got an R-10 it came with 6.1... IS the R-10 also going to get 6.2 update...
IIRC, 6.1 on the R10 is the same as 6.2 is on the other models.

[richierich]

How does one do this type of reset? Did I miss the instructions in the thread?

--David

Obviously you haven't read the manual or looked at your Menu. You hit the Tivo Button where "Now Playing" and other functions come up on your screen. You tab down to the bottom of the screen to the obvious function "Messages and Setup". You select that function which takes you the next screen where lo and behold you have "Restart or Reset System" which is what you are trying to do. You then tab down to "Reset Thumb Ratings & Suggestions" and select it. Then you press Thumbs Down 3 times and press enter to proceed. Now that wasn't that difficult to find if you would have looked thru you Menus to see what the options were. Or looked in your manual.

[Davidec]

Obviously you haven't read the manual ....

:rolleyes:

Well you see I had it in the bathroom and ran out of paper so I thought that using it as I did was a better use of the paper than trying to read it.....

:D

I did find the needed info in this forum after my posting and now for the last 24 hour my Philips DirecTivo has not rebooted when before it had started rebooting every 15 hours starting this past Monday [08/01/2005]....

-DEC

[Davidec]

:rolleyes:
.....and now for the last 24 hour my Philips DirecTivo has not rebooted when before it had started rebooting every 15 hours starting this past Monday [08/01/2005]....

Well it lasted 26 hours and has started rebooting again every two hours if...
.. watching live broadcasts ...
'IF' watching an item already on the machine before the upgrade it does not reboot?!?

Well talked to tech support they are to be sending me a new machine at no cost...

'IF' anybody here tracking the machines reporting troubles with the 6.2 update, Older machine was a small Philips DSR704

[richierich]

I think it has to do maybe with the "new restructuring" of the database and it runs into trouble reading it and that somehow triggers a reboot. Don't they test this stuff really good before they launch a "new" version of the software? Shouldn't this have shown up in their beta test? AMAZING!!!!

[Abiding Dude]

Dang, after not having reboots for 2 weeks I received 2 over the last 24 hours. I suppose I could try deleting suggestion data again, but I'm not sure if that just forestalls the inevitable.

[Mike_TV]

My unit rebootted again on Friday after about two weeks from clearing the Thumbs data. Clearing the Thumbs data doesn't appear to fix the problem for me.

[rmassey]

My reboots are back..... I have tried the Clear thumbs data suggestion a few times and it still reboots, eventually. I tried the pause 58 method with no success. I am now running spinrite v6 on the 120 GB drive, while my stock 40 is back in the DTvio to keep it running. The spinrite process will take 30-40 hours to run and I'll see what it reports. I do notice that the original stock 40 is much quieter than the 5400/120GB samsung that I upgraded to a few years ago.

Plan B is to take my kids upgraded DTivo (120GB 5400 Samsung) and give them mine with the stock 40 and call it a day. I'm getting tired of all the fuss with this box.

Plan C is to use my 5 year CCity warranty and get an R10 replacement, thus avoiding the obilgatory 1 year contract renewal with D*.

[richierich]

SpinRite should do it for you, however if you have a really bad drive it will only help you for so long and then the drive as the platter coating degrades you will encounter more bad sectors and you will have to run SR again. I bit the bullet and sent mine off to have the irreplaceable recordings backed up, replace the hard drive with a 300 gig Maxtor or Seagate (avoid the WD drives), add PTVNET, enable the USB port and send it back to me ready to go with Internet capabilities. I Can't Wait to get it back to see how all of this will work, I'm excited about being able to schedule recordings via the Internet, see how much free space is available, have folders on my Now Playing on my PC, check out error message log, be able to re-prioritize Season Passes, WishLists without having to wait or having TV viewing interruption (Yes we do occasionally watch Live TV), also caller-id on screen.

[rmassey]

SpinRite should do it for you, however if you have a really bad drive it will only help you for so long and then the drive as the platter coating degrades you will encounter more bad sectors and you will have to run SR again.

OK, but if SR does not report any bad sectors, what then? So far 15 hours in with 18 remaining on the SR operation, no bad sectors found. if I get to the end and see no errors from SR, I am inclined to leave the stock 40 on the DTivo and call it done.

[BTUx9]

I REALLY don't think that the problem most people are reporting here is related to the HD. My dtivo is hacked, so I see all the loggiing info, and it's not reporting any of the normal linux errors related to HD failure. The timing is also all wrong, with the number of people experiencing problems at similar times.

I have a strong suspicion that it relates to misformed guide data... possibly only hitting people who have a certain SP, possibly those who had a power-cycle at an inopportune time. Whatever the case, clearing Program Data (which nukes just about everything except your recordings and settings) is much more likely to work than just clearing thumbs. I did a Clear & Delete anything, and am desperately hoping this will solve the problem permanently. If it recurs, I'll post.

For those with access to the logs, the trouble starts with:
Audit, line 31 ()
Tmk Fatal Error: Thread HandleDataChanged <337> strayed!
on my tivo, and others.

p.s. this error can cause either a hang or a reboot, depending on how the tivo reacts, from what I've seen... might have to do with the current state of the tivo when it occurs, dunno

[Dan Collins]

I am convinced that it has nothing to do with the hard drive as well. I had a WD 250GB drive in a HDVR2 and experienced a freeze-up about twice a week. I cleared thumb ratings - no joy. I did a "clear and delete everything" and still it froze up (although it took a while to happen again). I finally called DirecTV and they sent me a refurbished Philips DSR-704. The SAME 250GB drive has been in the Philips now for 3 weeks and no problems.

I believe that some units (most notably the HDVR2s) are tripping over database errors when logging data at the end of a recording (my HDVR2 always froze with the record light on).

[BTUx9]

I did a "clear and delete everything" and still it froze up (although it took a while to happen again).
I'm very unhappy to hear THAT part of it... I've got 2 HDVR2s, and if there is a hardware issue with them, I'm up a certain creek. (it does somewhat explain why DTV is so blithely swapping out boxes without much tech support).

It's odd that it only seems to affect certain s/w versions... the one that is still running 3.1.1c has shown no sign of the bug.

People have said repeatedly that there's no significant difference in the h/w between same-era models (non-RID s2) and that the boards are actually made at the same factory. That makes me wonder if there could be a mistake/bug in the HDVR2 - specific pieces of the s/w slice.

I REALLY don't want to go through the hassle of trying to replace my boxen (and extending my contract) and with my luck, I'd end up with the almost unhackable R10 as a replacement :( .

[veener88]

Well I am having to do a full reset of the system removing everything. If this does not work they are going to replace it for nothing. I am kind of shocked since this receiver is the hughes 40 hour one for almost 2 years ago.

They did agree their is a problem with the software though and something this fixes it and some times it does not. From what I have read this has not fixed this for anyone.

Kind of shocks me thought about this is I just said I had this problem and they said they would replace it as long as I did the reset if I still have the problem no matter how radom it is even if it is just once a week. They are very trust worthy of their customers I guess I just got use to other companys were you have to pull teeth to get anything fixed.

I will be at the old software tonight and at 2 am it should download the 6.2 again.


---------------------------------------------------------------------------

Well I did the reset and 3 hour latter it is reset. All I have to say is that I am worried about this thing now. It took the box 3 times to get my local stations downloaded. At first I had only some stations, then the second try I had everything but the locals, and then the 3rd try I finaly was able to get my local channels. I just got a box that said channel not available.

I am going to see what it does durring the week and go from there. It seems like this thing is starting to die or the software is starting to go bad.

[the_scotsman]

I too have gone the C&D route on both of my DSR7000s. They are not fully online yet as I am still "tweaking" them (250GB + mods). If I still suffer reboots I'm going to just reload the older 3.x s/w. Pity, I like the folders, the speed, and the other features.

Paul

[veener88]

Well my system downloaded the 6.2 last night so I will see what happens.

[rmassey]

Well, as I suspected, Spinrite did not find any Bad sectors on the 120 GB Samsung 5400 drive. I ran level 4 for 30 hours and the process completed.

I put the 120 back into the DTivo and will see if the reboots reoccur.

I did notice that spinrite complained about excess heat/temp from the SMART sensor on the SS drive. I put a big fan (12") directly on the drive during operations and it ran at 41C, if I take the fan off, it reported 92C and at the beginning of the SR op, it reported 345C, which is hard to believe. This drive was sitting out of the PC case in complete open area. If it hit 345C, I think the cardboard box it was sitting on would have ignighted into flames. I will also check the temp while running the SS HD in the Tivo. Perhaps the 6.2 sw has enabled use of the SMART info and this is causing the reboots?

So far....

Pause 58 - no success
Clear & Delete Thumbs ratings - temporarily stopped reboots
Ran SpinRite 6 - No bad blocks detected, will watch for reboots this week.

[EDIT] - OMG, I was just doing a clear thumbs rating with the 120 GB drive I just did the SR op on, and the Tivo rebooted again.... or is this part of the C&D thumbs process? It went to powering up mid way into C&D. Oh BTW, internal temp is 45C.

[Dan Collins]

It would be interesting to see the general ages of the effected units. So far, I know I've seen HDVR2s and Philips DSR7000s being reported as problematic. I've got a SD-DVR80 and a Philips DSR-704, both of which have been fine. The Samsung SIR-4040 has not been online long enough to be sure of, but so far it has had no trouble as well. The only other model that goes back as far as the HDVR2 and the DSR-7000 is the RCA DVR-40. If this is isolated to such first generation Series 2 DirecTiVos, it may be a firmware problem.

I assume that this was the "compatibility problem" that stopped the 6.2 rollout for several weeks in the spring. I know that they did hit a problem with some units and decided that the numbers were small enough that they would just replace any bad units.

[rmassey]

Dan, my HDVR2s (both of them) are the very first batch from Dec. 2002. I was on the CircuitCity pre-Order waiting list when this model was first introduced. I upgraded both in about March 2003 to 120 GB Samsung 5400 drives and shelved the originals. My house was then stuck by lightning in 03 or 04 (can't remember) and it turned my HT Dtivo into a doorstop. I have a five year extended warranty with CC, so I had the unit replaced with a refurb HDVR2 and then used the same SS 5400 120 drive to upgrade again. This is the unit that is causing me reboots today.

I could prob call CC warranty and swap it again, but I suspect I'd get an R10 and not an HDVR2. If so, I'd leave it stock with the 80 and give it to the kids and take their upgraded HDVR2/120GB one that is not causing me reboots. Hopefully, this would not cause me to re-up for another year contract with D*. Franlky, I'm about ready to drop all Sat service and just use HD-OTA for free, getting tired of a $72/mo Sat bill. Because of this option, I really don't want to get tied to another 1 year contract with D*.

[rbtravis]

Try replacing power supply or use Hard Disk with less power requirements . It may be looking at power good line and rebooting based on that status. TiVo should have
designed a hefty power supply with more current capacity or made it available as an add on option.

[jfuredy]

It would be interesting to see the general ages of the effected units. ......

Well, I have two Hughes SD-DVR40 units, both with upgraded hard drives, and I have noticed that one of them is giving me reboot and locking problems. I have tried the pause 58 and the clearing of the thumbs, both of which have reduced the frequency of the reboots, but not eliminated them. I have also discovered that the reboots are less frequent when I reduce the amount of data stored on that TiVo by transfering to the other unit.

BTW, where do I need to look in order to check the logs to see when/how often the units are rebooting when I am not watching?

Thanks,
Joe Furedy

[rmassey]

BTW, where do I need to look in order to check the logs to see when/how often the units are rebooting when I am not watching?

I'm not sure about the logs, as this is another hack to get into Linux. I enable the 30 sec skip and if I notice that that is gone, I assume that the unit has rebooted itself. I know this is not as definite as a log file, showing a timestamp, but it works.

[jfuredy]

Thanks for the 30-second skip idea rmassey, but my unit IS hacked to allow access into Linux, and part of that hack is to turn on the 30-second skip at all times. So even after a reboot I don't get that clue about it happening.

Any other ideas?
Joe Furedy

[Dan Collins]

I'm not sure, but I would think that tverr.log would be the logical place for the errors (Tmk Fatal Error) that cause a reboot, to show up. You can tell if your system has rebooted by looking at kernel.log - the "Finished with sysint" message will appear right after each reboot. If you have TiVoWeb installed, the Info page will show total uptime (time since last boot) and this is also visible on the "System Information" page on your TV if you have backdoors enabled.

[su_A_ve]

Plan C is to use my 5 year CCity warranty and get an R10 replacement, thus avoiding the obilgatory 1 year contract renewal with D*.

The thing is that when you replace the unit, you'll have to activate the new one and guess what: It won't be a one year commitment, but a two year commitment...

[su_A_ve]

My 2-3 times per day reboot, on two different units, stopped cold when I took away an IR emitter from a remote control extender. Seems the 6.2 software either has an IR Easter Egg to reboot from a sequence that matches random IR noise, or with the 6.2 speed-up, the unit is more susceptible to IR glitches. I'll experiment with different RF receiver and IR emitter locations, or get a higher-end extender. I have a Terk Leapfrog that worked perfectly before 6.2. It still works, but surprisingly triggers reboots.

For anyone having reboot problems - check to see if you have any unexpected IR sources around, or just for an experiment, cover up the IR receptor when you don't need it.

Interesting... This morning we had a reboot right after I turned the MB TV (which is fed from the FR DTiVo and controlled with a Leapfrog) and changed channels.

On Sunday it also happened once... And yesterday we noticed that the peanut remote was running low on battery as it was not receiving correctly...

[rmassey]

The thing is that when you replace the unit, you'll have to activate the new one and guess what: It won't be a one year commitment, but a two year commitment...

Well, I'll have a very long discussion with CR about this. If D* is not supplying me with a replacment and I am activating a new unit that I acquired elsewhere, why is there a need to commit me for 1 or 2 years. This is absurd.

[veener88]

Just wondering is there a way to see the reboots if I have not hacked my tivo?

[rmassey]

Just wondering is there a way to see the reboots if I have not hacked my tivo?

Enable 30 sec skip (S-P-S-3-0-S) . if the box has rebooted, you will loose the skip.

[the_scotsman]

BTW, where do I need to look in order to check the logs to see when/how often the units are rebooting when I am not watching?

Thanks,
Joe Furedy


If you've done the superpathc_67all hack then the "uptime" should be on the system info screen

HTH
Paul M.

[Mike_TV]

Well I'm in the camp that doesn't think it a hardware problem and want to post what I observed last night.

I have three DirecTivos (one original Series 1 Hughes with a 2nd 80GB drive, one unmodified HDVR2, and one HDVR2 with a 120GB HD).

The problem I'm having is with the HDVR2 with the 2nd 120GB HD.

Last night, my problem unit started to reboot about every 45 minutes while I was playing with it. I noticed a few things. Programs were recording (BB 6 and another show. When I started to play anything recorded on 8/8 I got an error that I've never seen before. Something like there was a problem playing the recording. I don't have the exact text. My only option after that error was to delete the program or go back to the "Now Playing" list.

I got mad at that point and deleted everything recorded on 8/8. Before bed, I went and did the clear and delete everything in the ToDo list, which also removes all of the Season Passes.

This morning, I started putting back my Season Passes in and the unit appears to working just fine. I'll have to watch it a couple of days and see what happens.

Could the number of Season Passes and/or internal database problems be the cause? I had about 85 Season Passes with the problem.

My previous attempt to clear the Thumbs data did not solve the problem so we'll see if problem crops back up and starts rebooting again.

The real frustrating part is that my original Series 1 with the upgraded 80GB drive has been running fine without any problems for years now.

[Dan Collins]

I'm beginning to suspect that the problem really is just a database error. In some cases it is restricted to the thumbs rating database or the "Now Playing" database. so deleting and rebuilding these databases may resolve the problem. But in some cases the error my be in the system portions of the databases, and so, since you can't delete or rebuild these, the only option is to replace the hardware.

If this is correct, then a unit with the problem could be "fixed" by restoring the image from a known working unit to that system.

[richierich]

That is probaby why running SpinRite data recovery software gets rid of those database errors and rewrites the software/data in a better way and eliminates bad sectors.

[BTUx9]

That is probaby why running SpinRite data recovery software gets rid of those database errors and rewrites the software/data in a better way and eliminates bad sectors.
Ummm... no. They are referring to internal inconsistencies within the database... pieces of data that the tivo gags on. Spinrite has no knowledge of the format of the data, it is only concerned with mapping out sectors that are physically failing.

If this is purely database-related, I'm not sure why the newer RID units would be unaffected, seeing as they are running identical s/w (at least, in previous versions, the only differences were the loopsets <sony excepted>). Perhaps there are timing issues that cause occasional corruption... I know the RID motherboards have some significant differences.

I DO agree that it appears as if some units aren't handling corrupt data well, and I REALLY hope these units can be fixed. I think D* sending out this upgrade with these known issues is nothing less than criminal.

The timing of the errors is also rather suspicious... for many people to have the problem erupt simultaneously, I wonder if it may be malformed guide data coming down the pipe that could trigger it.

Just musing aloud, but maybe if we can hash this out, we can find a solution.

[rmassey]

That is probaby why running SpinRite data recovery software gets rid of those database errors and rewrites the software/data in a better way and eliminates bad sectors.

I'm not so sure I agree with this, if there are db index errors or db curruption, spinrite will not correct or alter this information, it only will correct drive errors or detect bad spots. If the db is currupt, SR will just rewrite the currupt info back onto the Hard disk.

[rnwjr]

I have a Hughes DirecTV Series 2 and have never had any problems until last Thursday when it seemed to be stuck on a download with the record light on... We called DirecTV and they suggested moving it to the other room, and that the wiring may need to be replaced... I know it's an issue with the unit, so I did the NASTY and reset my entire unit.... Fingers are crossed....

[Dan Collins]

I can attest to the fact that it is NOT a hard drive problem, since the SAME drive that caused freeze-ups in the HDVR2 is running fine in a DSR-704 - with no diagnotics or disk repair run at all...all I did was copy the Philips image onto the drive and install it.

This started as soon as 6.2 was spooled, so I don't think bad guide data is the issue, at least not directly.

We know that 6.2 rebuilds several of the TiVos databases. It may be that some pre-RID units (perhaps those that ran a particular software release, or got a guide download) have a particular database entry or value that causes the rebuild procedure a problem, which results in a bad system table or index value.

[BTUx9]

Actually, a copy CAN fix a marginal sector, AFAIK, but I agree that, with all the data we have on the problem, HD problems are the likely culprit.

My point on the guide data is that if 3.x was tolerant of certain irregularities, as soon as 6.2 was loaded, the problem would occur, so that doesn't remove it as a possibility, IMHO.

To narrow down this problem, we really need to run a crashing copy of the s/w on a RID unit, and a copy from a RID unit on a crashing machine. If my machine starts hanging again, I'll see if I can try the latter (I don't have a RID unit to try the former).

[richierich]

Well, I ran SpinRite back in March to correct hard drive problems and people said they would come right back but they didnt. I was looking out for the "f" version and monitoring my Tivo each day for it and lo and behold I got it downloaded and activated and guess what? I started experiencing pixellation, freezing, macro blocking, rebooting, etc.

I then ran SpinRite again and my unit has run perfectly ever since. Explain that. I think that it is the way or the level that the software gets written to a marginal or bad sector that creates problems. These were cheap bottom of the line WD drives that didn't even have a one year warranty so how good could they be. I got the "f" version on my other HR10-250 which came from Weaknees with 2 300 gig Maxtor Quickview drives and guess what? I have had no problems with it so it can't be the software or it would be experiencing problems. I think it is a combination of the software download and the hard drive with marginal or bad sectors on it. I had 3 bad sectors on it which SR told me about.

I have sent it off finally to have the WD drive replaced which SMART said was in imminent danger of failing. Tivo turns off SMART but SR reactivates it or uses it in it's attempt to recover data from bad sectors. So I'll be curious if I experience any more problems after I get rid of that piece of ***** drive and replace it with a good one such as Maxtor. Please explain to me if it was data errors and SR didn't fix them how then did mine work perfectly until the next download. I still find it hard to believe that the download was to the inactive partition which just happened to reside on a bad sector but it's possible and then running SR corrected it by removing the bad sector and replacing it with a good one and then writing the software back to that replacement sector.

[rmassey]

I can attest to the fact that it is NOT a hard drive problem, since the SAME drive that caused freeze-ups in the HDVR2 is running fine in a DSR-704 - with no diagnotics or disk repair run at all...all I did was copy the Philips image onto the drive and install it.

This started as soon as 6.2 was spooled, so I don't think bad guide data is the issue, at least not directly.

We know that 6.2 rebuilds several of the TiVos databases. It may be that some pre-RID units (perhaps those that ran a particular software release, or got a guide download) have a particular database entry or value that causes the rebuild procedure a problem, which results in a bad system table or index value.

Dan, I'm beginning to agree with you here. So it looks like a C&D everything or just reimage the drive is the solution. (I think you said this in a previous post). Either way, you will loose everything (recordings, SP, etc). If this is the solution, I'd opt for a reimage, as it's quicker than C&D. The next question is, over time will the issue reoccur. If it's a db index that gets corrupted with excess recordings or SP's that is causing the problem, will it come back and haunt us eventually on a newly imaged drive?

[BTUx9]

As so often happens, people on threads are experiencing different problems... We're not saying spinrite can't fix some problems, we're saying there is a specific problem with older S2 dtivos and 6.2 that causes a very specific hanging/rebooting problem. Obviously, what you're experiencing doesn't fall into that category.

[richierich]

I am convinced that it has nothing to do with the hard drive as well. I had a WD 250GB drive in a HDVR2 and experienced a freeze-up about twice a week. I cleared thumb ratings - no joy. I did a "clear and delete everything" and still it froze up (although it took a while to happen again). I finally called DirecTV and they sent me a refurbished Philips DSR-704. The SAME 250GB drive has been in the Philips now for 3 weeks and no problems.


Just because you have been running good for 3 weeks is no indication that it can't be the POS WD drive as most don't start failing until 6 months of use. Mine took about 5 months. Every time I ran SpinRite it cleared up the problem until the "f" version came out. Maybe it is the way that it writes the download where it loses some info over the satellite download, who knows. I am getting mine back from PTVUPGRADE and I will disconnect the phone line and never plug it back in until I see a download that actually works for most people for at least 3 months. I'll have folders, networking, caller-id, etc. but I don't trust these downloads. I lost over $1,000 worth of PPV recording and other material that I will never be able to recover. Should have offloaded them to DVDs. OH WELL!!!!

[rmassey]

richierich, we are discussing sw version 6.2 for SD DTivos. I think you are discussing version f for the HR10-250, which is different. AFAIK, 6.2 is not available for the HR10-250 yet.

the common problem for SD Tivio owners is reboots began just after sw v 6.2 was installed. You may want to take your topic over to the HD PVR forum.

[richierich]

Thanks, I confused threads.

[Dan Collins]

There are many problems that ARE caused by bad disk drives. Stuttering and pixelation are certainly amoung them, and products like SpinRite will fix those.

But here we are talking about a VERY SPECIFIC class of problem. In one case, the TIVO simply freezes and is totally unresponsive to remote or front panel button presses. The only recovery is to pull the plug. In the other case, the TiVo spontaneously reboots by itself. This is not to say that ALL reboots are caused by this, but when a unit otherwise behaves normally for days at a time, a reboot is an odd occurance. Certainly, the kind of hard freeze-ups I had been seeing are unusual to say the least.

While I had my HDVR2 I tried restarts, clearing thumb ratings, and even a Clear and Delete Everything. In each case the freeze-ups returned in a few days (almost two weeks after the C&DE).

My question is how different are the RID units? We know that there is a software slice for each model of unit, but is tivoapp or dssapp different for RID versus non-RID units?

So, bottom line, based upon my experience and what I read from others, at least SOME non-RID DirecTiVos have been experiencing operational "issues" since the 6.2 upgrade. In SOME cases, clearing thumb ratings or clearing everything seems to solve the problem. But in some cases it does not.

Even if clearing data works, it is an indication that the problem is NOT the hard drive. Clearing data does nothing to reformat or otherwise repair bad sectors. All it does is rebuild the effected databases. This clearly indicates a software issue - either with the database upgrade process, or the database access software, or some combination of both.

[richierich]

[QUOTE=rnwjr]I have a Hughes DirecTV Series 2 and have never had any problems until last Thursday when it seemed to be stuck on a download with the record light on... We called DirecTV and they suggested moving it to the other room, and that the wiring may need to be replaced.. QUOTE]

That CSR deserves a RAISE because that is the BEST BULL***** that I have ever heard from a CSR, tremendous creativity. I bet he was laughing his ARSE off when he got off the phone with you. They are so incredibly INEPT!! We know a hundred times more about Tivos than they will ever know. Did you unplug your unit, wait 30 seconds, remove the card, reinsert it and plug it back in. They love to read that one to you from their script.

[BTUx9]

Actually, we KNOW that tivoapp is identical, because some patching programs found elsewhere wouldn't work otherwise.

[richierich]

I will add one more thing and then leave this thread because I am an HR10-250 guy with a problem but what I have experience and being a computer programmer helps me understand this problem is that when the CPU is busy doing a read on a bad sector, it queues up every tasks as they come in until it completes that read task. Is the Tivo showing a yellow light which says it is not a responsive or bad remote or sluggish remote but it is just queueing up the remote commands to act on them when it finishes the read function. It has to hit a read threshold until it quits trying and then acts on the other requests.

I believe this issue that you guys have with the 6.2 release is the same as I have had with the "f" version and that is why I will not plug in my phone line until I can see alot of people with the HR10-250 experience positive results with the 6.2 release when the HR10-250 gets it if that release OCCURS in MY LIFETIME!!! Good Luck!!! I wish D* would just tell us what they think the problem is because they should know by now.

[the_scotsman]

Even if clearing data works, it is an indication that the problem is NOT the hard drive. Clearing data does nothing to reformat or otherwise repair bad sectors. All it does is rebuild the effected databases. This clearly indicates a software issue - either with the database upgrade process, or the database access software, or some combination of both.


Not necessarily, it *could* still by a HD problem! A C&D clears the data and the now empty HDD doesn't yet use the "Bad" area. Once you start filling it up with recordings it hits the bad area.... problem comes back!

Almost 48 hours and no reboots on the DRS7000s (uptime on the system page is awesome) - fingers crossed!

What is RID?

Paul

[richierich]

Paul, you hit the nail on the head. My HR10-250 did not fail until it was about 60% full. Then I ran SpinRite and it found 2 bad sectors about 55% of the way thru the process. After it took those 2 sectors out I had no more problems until the new download. I ran SR and it discovered 3 more bad sectors. It removed them and I ran just fine ever since. All doing a Clear and Delete does is buy you time before it hits a bad sector again in my humble opinion.

[rmassey]

richierich, in your case, I think SR did indeed fix your problem. I love SR too and I ran it on a 120 GB drive for 30+ hours. It did not report/detect any bad sectors for my drive. With this drive reinstalled into the DTivo, I am still watching the Tivo to see if reboots occur again, so time will tell.

[richierich]

I think that the reason why D* is telling it's CSRs to tell us to do a Clear and Delete is that their technical people have told them that if a bad sector exists 40% or 50% into that drive then the techs know that they can buy time by having us Clear & Delete and have us start over from point zero but I believe when you achieve that 40 or 50% again and hit that bad sector you will have problems.

Another interesting thing that I read in the SR docs is that it rewrites the data with a deeper pit burn so that it can be read easier for a longer period of time. I do know that game CDs use black CDs and say to burn it in 1X instead of 8X to allow for a better pit burn. I am no expert but after SR does it's thing with no re-organization of the database or whatever I am back in business until the next dowload.

Someone please comment on this or explain it to me so I can go away and be happy.

[rmassey]

I think that the reason why D* is telling it's CSRs to tell us to do a Clear and Delete is that their technical people have told them that if a bad sector exists 40% or 50% into that drive then the techs know that they can buy time by having us Clear & Delete and have us start over from point zero but I believe when you achieve that 40 or 50% again and hit that bad sector you will have problems.


Well, how would this work in my case. I was having reboots, I SR the drive, no bad sectors found.... so if no bad sectors, what is/was causing the reboots.

Also, Dan took his same problem drive with no diags, no SR and is using it in a different DTivo with a newly imaged drive. So far no reboots, but they could reoccur once the bad spot is reached (in theory).

IMO, it's a sw or db index issue .vs. a HD issue.

[richierich]

Alot of times reboots are caused because the CPU runs out of temp storage and reboots to save itself by freeing up space so it can function. Perhaps the CPU is getting confused by the reconfiguration of the database. When I was a programmer and we re-structured a database we had to offload all of the data, then re-structure the database by telling it if it was sequential or random or a mix of the two. Then we had to use a utility to reload the data back into the database properly so it could assign the proper indexes.

I can't imagine how they can restructure the database without doing this. If they start using ongoing recordings in one manner and don't get rid of the old structured database then they will encounter problems. That is probably why they want you to do a Clear & Delete. To get rid of the old structure. Going forward it will write everything with the new database structure. Why don't they tell us this? Big Corporation!!!!

[rmassey]

Alot of times reboots are caused because the CPU runs out of temp storage and reboots to save itself by freeing up space so it can function. Perhaps the CPU is getting confused by the reconfiguration of the database. When I was a programmer and we re-structured a database we had to offload all of the data, then re-structure the database by telling it if it was sequential or random or a mix of the two. Then we had to use a utility to reload the data back into the database properly so it could assign the proper indexes.

I can't imagine how they can restructure the database without doing this. If they start using ongoing recordings in one manner and don't get rid of the old structured database then they will encounter problems. That is probably why they want you to do a Clear & Delete. To get rid of the old structure. Going forward it will write everything with the new database structure. Why don't they tell us this? Big Corporation!!!!

Re: CPU, etc. yes, but this problem did not exist with v 3.11. It began with the release of v6.2, so unless they also replaced the Linux OS and how it handles multi threaded process allocation and heap storage, I doubt the theory of the CPU runing out of temp storage is valid.

I'm a programmer too, but I am not going to begin to trouble shoot this D* sw/db problem over the net. :rolleyes:

Why don't they tell us this? because less than 2% of Tivo users would even begin to understand (or care). :rolleyes: :rolleyes:

[richierich]

I am not saying tell us all of the technical stuff but they know what is causing problems, whether it is a hard drive problem or software or whatever, why do we have to endlessly speculate in these forums and threads to try to figure out if replacing the drive will work, or buying and running SpinRite will work or whatever. They could be a little more user friendly and tell us what is going on, be patient and the fix will be approximately delivered in a certain timeframe but don't hold us to it because it may take longer to troubleshoot.

Thanks RMASSEY, for your input and insight and feel free to PM me with any additonal feedback because I have been fighting this problem for over a year and I just want to know more about what is causing all of these problems and why D* hasn't done more to resolve them.

[rmassey]

if replacing the drive will work, or buying and running SpinRite will work or whatever.

Well these actions are not sactioned by D* for users to perform, in fact it voids the warranty. there solution is to just replace the box. The problem for us upgraded users is we are faced with a more telling solution due to our interest in upgrading the box.


Thanks RMASSEY, for your input and insight and feel free to PM me with any additonal feedback because I have been fighting this problem for over a year and I just want to know more about what is causing all of these problems and why D* hasn't done more to resolve them.

I'm with you, I just want a solution, so I can fix it and get on with the party.

[richierich]

My warranty ran out along time ago. In fact I have that replacement deal (I don't know why) but I just sent mine off when I could have had a replacement but it could be a refurbished unit or a new unit with a bad hard drive that won't show up for 6 months or one that has a bad HDMI port so I bit the bullet and paid alot of money to get it replaced along with networking capabilities, etc, that I don't have the time to do. I have the money so I got PTVUPGRADE to enhance my unit even though I lost my recordings.

It is amazing to me that D* doesn't try to do more to inform their most loyal supporters and most people who can afford this stuff. I know we are a small percentage but there will be alot of people following us if we are happy and successful by example, word or the mouth, etc.

[Motterman]

Clueless newbie here.

I've got the Hughes SD-DVR120 that just started crapping out a few days ago. (picture locking up, artifacts, rebooting, non-responsive) I'm furiously trying to back up what I can onto DVD's with my new recorder, but I don't think I'm going to get it all as the problems just keep getting worse and more frequent. I bought the thing at BestBuy (I don't think I got their warranty though), but I do have D*'s service protection plan on my acct. After doing research this afternoon, it looks like my receiver probably downloaded this 6.2 thing and now it's jacked up. I've looked at SpinRite that I saw mentioned here, but I'm not sure that's going to fix my problem. I've looked at the upgrade/replacement options at Weaknees as well, but that's not going to help me keep what I have either... I'm not afraid of cracking cases and tweaking with computer/electionric stuff, although I know nothing about Linux, despite a pretty good knowledge of DOS and Windows.

I need some advice if possible.

Should I buy a new harddrive and just forget about what I'm losing here or should I try and repair the disk with SprinRite/DD/etc. and hope that works... I don't know, maybe I'm just thinking/typing out loud to try and make my decision easier...

In any case, this sucks. :mad:

Oh yeah, my temp is 41, so I'm ok there....

[BTUx9]

re: Motterman - since yours is a later unit, it's unlikely to be the same issue as we're discussing here (though I'm not 100% sure of that). On MY machine (and some others) the rebooting stopped when I disconnected the inputs. It's worth a shot, in that it would at least let you pull the recordings off.

If you wanted a more definitive answer as to the cause, you could connect your tivo drive to a PC, boot a linux livecd (there are several images that specifically support TiVo, or you can use any image and load the tivopart utility to recognize the drive), anc check the log files. The 6.2 issue has an Audit, line (31) message, followed by "thread strayed" messages, whereas HD failure has standard linux errors for hda

this method would also help richierich and others do a differential diagnosis on their problems, as they may be more HD-related than 6.2

[Dan Collins]

One more time...

I had a HDVR2 with a brand new WD 250GB drive installed the week after I got 6.2. After about 1 week I started experiencing freezes - this was NOT the TiVo sitting trying to read a sector. The red record light was on, and it was NOT responding to ANY button presses. I once left it for 12 hours and NOTHING happened. I eventually completely filled the 250GB drive (by recording all episodes of a few series) and saw no difference in behavior from a 100% full drive or from a 10% full drive. I did a "C&DE" and still had freezes after about 12 days. The frequency of the freezes was anywhere from a day or two to a week or more between occurances.

I then called DirecTV and they sent me a refurb DSR-704. That SAME 250GB drive was pulled from the HDVR2, reimaged with the Philips version of 6.2, and installed in the DSR-704. That drive is now full of recordings and suggestions and I have seen NO MORE FREEZES.

The freeze ups I was seeing had NOTHING to do with bad drive sectors.

[Dan Collins]

...I've got the Hughes SD-DVR120 that just started crapping out a few days ago. (picture locking up, artifacts, rebooting, non-responsive)...Oh yeah, my temp is 41, so I'm ok there....What you are describing ARE the classic symptoms of a drive failure. This is NOT what we are talking about. Other than occasionally locking up or rebooting, the TiVos we are referring to work fine - no artifacts, no stuttering, no unresponsiveness. I'd say you ARE experiencing incipient drive failure.

41 is pretty warm for a SD-DVR120 - you should be in the low 30's on those units (they used the B revision chassis with a heftier fan).

[rnwjr]

richierich... I agree with you comment, but I was hoping the tech's knew what they are talking about... Six hours later (Was late from work) I cleared my TIVO only to find that it froze again with the recording light on... At least I can watch two of my programs until it fails again...

Should I go to Circuit City/ Best Buy and get a R10? (Wonder if this requires new service or can be for existing customers for the $99.00 price)

or

Get a refurb from DTV?

[richierich]

Gotcha Dan.

[rnwjr]

It appears that mine freezes when it is recording programs in my season pass only... Off to Circuit City I go...

[aggiedwc]

Thanks for all of the information on this thread. I also have a Hughes DVR2 and started seeing spontaneous reboots after receiving the 6.2 software download. I have one 80G WD drive in this system (was the secondary before my 40G totally died last year).

I have another problem at the same time because I also recently switched to Vonage and haven't been able to successfully complete a daily call. I originally thought that the reboots might be an unfriendly way D* had added to force me to make a call or call in, but from this thread it sounds like they are truly two separate issues.

I tried the thumbs database clear tonight. We'll see how that goes. May make life a little more bearable for a week or to if I'm reading this thread correctly. Hopefully I won't have to go to the full clear and delete.

One item Dan mentioned in his 8/8 post was that he thought it might be related to a database error "while logging data at the end of a recording". Might still be a database error, but while recording long baseball games (had to record lots extra cause I kept missing extra innings :)) my reboots seem to have regularly occurred in the middle of recordings and not exclusively near the end.

Thanks for being out there and sharing. It helps to have others to commiserate with. Who knows, maybe we'll figure this out yet.

P.S. Thought the IR theory was interesting, too, as I am using an RCA D930/D935 wireless IR repeater. Don't know how that compares to everyone else, but it's more data at least.

[veener88]

Right now for me the reboot and clearing my whole system has seemed to work so far. I have not had a reboot all this week. I am waiting for a few weeks to make sure.

[chasmm]

Add me to the list...

I've got two DVR40's, one stock and the other has the Weaknees dual 160 drives installed. The upgraded unit would not receive 6.2. After corresponding with Weaknees, it was suggested to do a Clear & Delete. I did this tonight, and then forced a daily call.

Lo and Behold...6.2! Of course, I was pretty surprised when it locked up on me while reading the message about the DVR upgrade. Since then it has rebooted over 10 times. I can't even get through a session of setting up the parental controls without it rebooting. I've tried forcing a call (it reboots), I've tried running a system test (it reboots). In short, it reboots almost continously.

At first, it was rebooted whenever it got to 72% of the sat data, then it started going from 72% directly to LiveTV. Now it will get to 95% and then go to LiveTV, but within 10 minutes of getting to LiveTV, it WILL reboot.

I was so upset that it wouldn't load 6.2 because it was slow. Now I've got a box that seems to be useless...

Any suggestions would be greatly appreciated.

BTW, this is a box that, to my knowledge, never spontaneously rebooted in the prior year. I never had to redo the 30-second hack.

[brad639]

My locked up system was with the Hughes DVR2.

It was one of the early batches, had it for about 2 years when the hard drive failed around december. I put an upgraded 160GB NEW Drive in it.

Four months later got the 6.2 upgrade and about a month later got pauses and stops and reboots.

I did the clear and delete thumbs, season passes, and to do list. Still got the stops and reboots after 2-3 days.

Then I did the pause 58 thing and it has been working well for about 3 weeks+ with only 2 stop reboots spaced out.


It seems to be software related with DVR2's and upgraded drives??

[Motterman]

richierich... I agree with you comment, but I was hoping the tech's knew what they are talking about... Six hours later (Was late from work) I cleared my TIVO only to find that it froze again with the recording light on... At least I can watch two of my programs until it fails again...

Should I go to Circuit City/ Best Buy and get a R10? (Wonder if this requires new service or can be for existing customers for the $99.00 price)

or

Get a refurb from DTV?

Yeah, I called D* tech support on Thursday night. She said to clean and delete everything... I tried a few times to record what I could onto DVD before starting the process. I started it before I went to work at 8am Friday morning, and when I got home from work around 5pm, the screen still said "process may take up to an hour, do not unplug" and the red record light was flashing. I called D* support and this girl said that even though it says it should only take an hour on the screen, it could take up to 24 hours. :rolleyes: Lovely. So, anyways, went to bed and woke up on Saturday... not surprised to see it still blinking and on the same message. Called D* tech support again, they said to unplug it and then plug it back in and I should be fine.... well, I kept him on the line while it was starting up, and, sure enough, it went back to the clean and delete screen / red light blinking thing. So, they transfered me over to get a replacement, where I was told that, since it was Saturday, they won't process the replacement order until Monday, and I might not get the "comparable DVR unit" until Wednesday. :mad:

I'm assuming this is "classic" D* tech support, yes?

[Nightfall]

I have an HDVR2 and I noticed the last few weeks that my Tivo has been rebooting randomly. Today was the first time I saw it reboot while I was watching a recorded program. I don't think this has anything to do with a bad drive. After the system rebooted, I finished watching the show and deleted it.

I have read through the 8 pages of information in this thread so far. It seems that it could be the 6.2 OS, the fact I have 2 160GB drives in the unit, the database, the season passes, or the Tivo itself.

I wish that I knew what was causing the problem.

I am going to monitor this more closely to find out how often it is rebooting. I watch TV once a day on average, and some days I have to do the 30 second skip while other days I don't have to do it. I think this is a once every 2-3 day thing, but I haven't gotten it locked down as of yet.

[BTUx9]

Update:
After running a Clear & Delete Everything on my HDVR2, I've been hang/reboot free for 12 days, now. I'm still monitoring the machine closely, but I'm hopeful this indicates a stable machine. I *DID* reboot 2 days ago, for other reasons, and there's a very slight possibility that rebooting once a week may be helpful.

[the_scotsman]

I too did a clear & delete (+ HDD upgrades). Been reboot free for over 10 days.

[veener88]

I came up with a way to find out if your TIVO is rebooting when you are away from the house with out have to hack the unit.

Go this tread and put in this backdoor code.

http://www.tivocommunity.com/tivo-vb/showthread.php?t=245727

The only way you will lose this option is when your system reboots or if you disable it. So if you have it enabled and you come home and no longer have this enabled your system did a reboot.

I had this happen this week to me and it popped on my head to keep this going.

[Mike_TV]

For the people that did the Clear & Delete Everything, did you put all of your Season Passes back in?

I have about 100 SPs (a bunch of ARWL for music artists/groups that show up on late night talk shows).

I was wondering if the nubmer of SPs may be a factor....

[BTUx9]

I don't have large numbers of SPs, but I did restore mine (using TWP) and that didn't seem to be an issue. There WAS a post on DDB saying that one of the SPs someone restored caused a reboot, but that may have been an anomaly.

For the record, my tivo is misbehaving again. It was after some unsupported actions better discussed elsewhere, and the hanging has a different cause (in the logfiles) than the initial problems. It looks like a corrupt stream in 6.2 can actually corrupt MFS, so caveat hacker.

[jawhn]

This is driving me crazy! :mad:

Samsung S4040R. Had it for over a year and I NEVER saw a reboot. Got 6.2 and reboots started shortly thereafter. Started reading this thread and Most suggested HD problems. Replaced the old 40GB HD with a BRAND NEW 160GB HD (wanted the extra space anyway). NOTICED reboots starting within a week. They vary from once every couple of days, to twice in an hour. I've tried resetting the Thumbs and a Total Reset.

There seems to be NO common link. Does it when watching live TV (I know it's ALWAYS recording) and watching recorded material.

OBSERVATION: If it's bad sectors on the HD and it does it on pre-recorded material, shouldn't it show up each time you view the same recording? It doesn't on mine!

[BTUx9]

If you notice, most who suggest HD troubles are redirected to a different thread. There's a definite instability with 6.2 and SOME older dtivos. And, yes, "driving me crazy" is a common reaction. I wish I had something more constructive to say than "join the club" :(

[joelv]

I have the same problem. Samsung SR5412-DR. I called D* tech support and level 2 tech got on the phone (level 1 can't help). I described the problem and without missing a beat she said "we'll send you a new one, where do you want it to go?"... That was it. I never had a chance to bitch or anything.

Sounds like they've gotten quite a few of these calls already and didn't even bother telling me to try a reset.

[veener88]

I have the same problem. Samsung SR5412-DR. I called D* tech support and level 2 tech got on the phone (level 1 can't help). I described the problem and without missing a beat she said "we'll send you a new one, where do you want it to go?"... That was it. I never had a chance to bitch or anything.

Sounds like they've gotten quite a few of these calls already and didn't even bother telling me to try a reset.


Just wondering did they tell you what they are sending you for the replacement?

[vigfoot]

Here's my deal- I bought a new Philips 708 from weaknees, which arrived last week. Finally got around to hooking it up (to replace a working 7000) last night. Watched it for about an hour and went to bed. I think the next call was gonna be overnight, so I figured the 6.2 upgrade might be on it this morning. When I turned on the TV, the frame was 'paused'. I couldn't get out of it so I unplugged/replugged a few times and never got a 'powering up' screen or a lit light on the front panel, but I could hear the fan. I swapped back the 7000 and it worked fine.

Do harddrives degrade w/ non-use?

[joelv]

Just wondering did they tell you what they are sending you for the replacement?


Sounds like its going to be a Hughes. I said I don't care as long as its 100hrs like the Samsung.

[veener88]

Sounds like its going to be a Hughes. I said I don't care as long as its 100hrs like the Samsung.

I have a Hughes 40 hour unit and I am just a litte worried about getting the same unit back with the exchage and having the same problem again incase it is a hardware issue with that box.

[joelv]

They're sending mine via FedEx Ground. I'll try it out and let you know if the problem re-occurs. I hope that a fresh, clean install on a new unit does the trick (as opposed to an upgrade).

You might as well call it in. Worst case they send you a new unit. Can't be any worse then the one you have now (mine was up to two reboots an hour - maddening!!!)

[joelv]

One quick note - I have been with DirecTV since 1996 and Sunday Ticket since the first year it was on. They've got a boat-load of my money so maybe thats why the service swapped my unit so easily.

Just throwing that out there since I heard from a couple people that they didn't get the same level of service...

Good luck all! Thanks for the helpful thread!
JOEL

[Nightfall]

It looks like mine is rebooting about once every 2 days. So now, what do I do? That is the question. I think I will do a clear and delete, but I still have a lot of programs on my Tivo I want to watch. I would hate to do that for a while. At least until I watch my programs.

[Nightfall]

My locked up system was with the Hughes DVR2.

It was one of the early batches, had it for about 2 years when the hard drive failed around december. I put an upgraded 160GB NEW Drive in it.

Four months later got the 6.2 upgrade and about a month later got pauses and stops and reboots.

I did the clear and delete thumbs, season passes, and to do list. Still got the stops and reboots after 2-3 days.

Then I did the pause 58 thing and it has been working well for about 3 weeks+ with only 2 stop reboots spaced out.


It seems to be software related with DVR2's and upgraded drives??

Could this be the issue?

[the new guy]

Both of my units are RID boxes, hacked and running brand new Quickview drives. One is using the 62small image, the other is imaged from the factory drive, which was allowed to upgrade from 3.1.1e. Both have the same errors in the tverr log file:
Aug 21 23:25:31 (none) myworld[193]: Tmk Fatal Error: Thread myworld <193> strayed!
Aug 21 23:25:31 (none) myworld[193]: pc 0xb1aa48 status 0x8001fc13 cause 0x000008 bva 0x5ecf385c hi 0x000010 lo 00000000
Aug 21 23:25:31 (none) myworld[193]: R00 0x00000000 R01 0x100a3cd4 R02 0x00000080 R03 0x00a92ff8
Aug 21 23:25:31 (none) myworld[193]: R04 0x00000000 R05 0x5ec79598 R06 0x5ec5032c R07 0x5ec501a4
Aug 21 23:25:31 (none) myworld[193]: R08 0x00000001 R09 0xffffffff R10 0x5ec50114 R11 0x5ec501d8
Aug 21 23:25:31 (none) myworld[193]: R12 0x00002184 R13 0x00000000 R14 0xa4b58000 R15 0x00015180
Aug 21 23:25:31 (none) myworld[193]: R16 0x5ec594a4 R17 0x00000000 R18 0x00000020 R19 0x5ece0bac
Aug 21 23:25:31 (none) myworld[193]: R20 0x00000ce9 R21 0x1d78dabd R22 0x00000000 R23 0x5ece0b94
Aug 21 23:25:31 (none) myworld[193]: R24 0x00000000 R25 0x00b1aa34 R26 0x00000001 R27 0x00000000
Aug 21 23:25:31 (none) myworld[193]: R28 0x1006d910 R29 0x7fff6490 R30 0x5ecda3b0 R31 0x00a93014
Aug 21 23:25:31 (none) myworld[193]: bt -t /tvbin/tivoapp
Aug 21 23:25:31 (none) myworld[193]: read 0x2aaa8000 /lib/ld.so.1
Aug 21 23:25:31 (none) myworld[193]: read 0x2ab04000 /lib/libutil.so.1
Aug 21 23:25:31 (none) myworld[193]: read 0x2ab48000 /lib/libdl.so.2
Aug 21 23:25:31 (none) myworld[193]: read 0x2ab8c000 /lib/libpthread.so.0
Aug 21 23:25:31 (none) myworld[193]: read 0x2abe8000 /lib/libm.so.6
Aug 21 23:25:31 (none) myworld[193]: read 0x2acb0000 /lib/libc.so.6
Aug 21 23:25:31 (none) myworld[193]: 0x00b1aa48 0x00a93014 0x00b20ba8 0x00b209e4 0x00b2f358 0x00b2ee5c 0x00b2ec28
Aug 21 23:25:31 (none) myworld[193]: 0x01353b7c 0x01353f1c 0x0130372c 0x013032f8 0x0137f73c 0x01389c84 0x00b1fe40
Aug 21 23:25:31 (none) myworld[193]: 0x00b1dcf4 0x00a857e0 0x007a41b4 0x00612e00 0x00403090 0x2acc13fc
Aug 21 23:25:31 (none) myworld[193]: Tmk Fatal Error: Thread myworld <193>: unexpected signal 11
Aug 21 23:25:31 (none) myworld[193]: Tmk Fatal Error: Thread died due to signal 11
Aug 21 23:25:31 (none) myworld[193]: Invoking rule 834: rebooting system

This sequence seems to be pretty consistent each time a reboot occurs. I have run the MFS cleanup, but the issue comes back after a while. I haven't seen any mention of this, but the reboots seem to occur while watching live TV. If I try to rewind back into the buffer, I will see the flash from the front panel confirming the remote signal was received, but the unit does not respond. Within five seconds, the gray Welcome... screen will show up. I have never seen a reboot while watching a saved program. There is obviously some issue with the new software that D* and TiVo need to address.

Waiting for 6.2.1...

Tim

[BTUx9]

the new guy: Was there anything in the logs BEFORE what you posted... in my experience, there are usually warning messages before threads stray. Of course, I've seen 2 different threads straying causing hangs (neither of them myworld), which is rather suspicious.

[the new guy]

Here is some of the kernel log leading up to a reboot:
Aug 21 22:39:15 (none) kernel: !!!!WARNING: Needed 2 tries to set video STC to 0x031cbe59
Aug 21 22:39:15 (none) kernel: Before = 0x031cbeb4, After = 0x031cbee1
Aug 21 22:39:15 (none) kernel:
Aug 21 22:39:33 (none) kernel: !!!!WARNING: Needed 2 tries to set video STC to 0x1839c6cd
Aug 21 22:39:33 (none) kernel: Before = 0x0329ae90, After = 0x0329aebe
Aug 21 22:39:33 (none) kernel:
Aug 21 23:25:31 (none) kernel: Illegal read at 00000040
Aug 21 23:25:31 (none) kernel: do_page_fault #2: sending signal 11 to myworld(193)
Aug 21 23:25:31 (none) kernel: $0 : 00000000 100a3cd4 00000080 00a92ff8 00000000 5ec79598 5ec5032c 5ec501a4
Aug 21 23:25:31 (none) kernel: $8 : 00000001 ffffffff 5ec50114 5ec501d8 00002184 00000000 a4b58000 00015180
Aug 21 23:25:31 (none) kernel: $16: 5ec594a4 00000000 00000020 5ece0bac 00000ce9 1d78dabd 00000000 5ece0b94
Aug 21 23:25:31 (none) kernel: $24: 00000000 00b1aa34 1006d910 7fff6490 5ecda3b0 00a93014
Aug 21 23:25:31 (none) kernel: Hi : 00000010
Aug 21 23:25:31 (none) kernel: Lo : 00000000
Aug 21 23:25:31 (none) kernel: epc : 00b1aa48 Not tainted
Aug 21 23:25:31 (none) kernel: Status: 8001fc13
Aug 21 23:25:31 (none) kernel: Cause : 00000008
Aug 21 23:25:31 (none) kernel: 8001e9fc 8001eac0 80022bb4 80022d74 80024db8 00b1aa48
Aug 21 23:25:31 (none) kernel: 00b1aa48 00a93014 00b20ba8 00b209e4 00b2f358 00b2ee5c 00b2ec28 01353b7c
Aug 21 23:25:31 (none) kernel: 01353f1c 0130372c 013032f8 0137f73c 01389c84 00b1fe40 00b1dcf4 00a857e0
Aug 21 23:25:31 (none) kernel: 007a41b4 00612e00 00403090 2acc13fc
Aug 21 23:25:31 (none) kernel: Tmk Fatal Error: Thread myworld <193> strayed!

There are numerous warnings about setting the video STC before that. In looking over the kernel log, nearly every reboot happens after the myworld thread strays. Is this different than the reboots everyone else is having?

Tim

[BTUx9]

I can't speak for everyone, but my reboots seem to be from a different cause (though quite probably related)... My log DOES have the warnings about 2 tries needed to set STC, that doesn't seem to be related, and may be "normal"

I'll keep my eyes open for a myworld-related reboot/hang... actually, it does make sense, in that most of my issues have been hanging, not rebooting, and it looks like when myworld dies, a reboot is called.

[the_scotsman]

Damn! One of my DSR7000s is now rebooting once again with a frequency of 2 or 3 times a day :-(

I have also seen the STC message in my log file but have not had enough time to compare the (so far) "stable" machine with the one now rebooting. I've really found no log file messages prior to rebooting that suggest a problem.

I've now restored the original tivoapp to see if that helps.

Also, I have a ground loop that I need to break - perhaps this machine is more sensitive and the ground loop is causing it problems - don't know! I do know that it is causing rolling horizontal purple lines on the monitor.

Frustrating thing is that I just bought 2 more DSR7000s to replace the T-60s (which are rock solid) as the folders and speed are great features plus MRV rocks. Final resort will be to go back to 3.x (which was perfectly stable). I would have D* swap these out but I really do not want an R10.

Paul

[the_scotsman]

Oh yeah, one other symptom, which I had not observed before, was that the video would freeze or stutter every now and then (live & recorded), both during normal viewing and FF. This may be a side effect of the large HDD so I'm going to try the original again if the tivoapp restore dose not work.

Paul

[Nightfall]

I am getting one reboot every 2 days or so on average. I know cause I have to set the 30 second skip up again. I know I want to get this resolved before the new season of TV hits. The big question is, what do I do? I am going to start with a clear and delete everything here in the next month. That will hopefully fix my problems as it had with other people here.

To those of you who did a C&DE, did it fix your problems with the reboots? I know 10+ days later, no reboots which is a good sign. However, is that still the case?

[kayson712]

For the people that did the Clear & Delete Everything, did you put all of your Season Passes back in?

I have about 100 SPs (a bunch of ARWL for music artists/groups that show up on late night talk shows).

I was wondering if the nubmer of SPs may be a factor....

Mike - My SPs were similar to yours. I knocked mine down from about 100 to 50. Not sure if this makes a difference or not. (FWIW D* support claims that the reboots are a known issue and they suspect the harder you make the machine work the more likely it is to start doing the restarts). Anyway - boot free for about two weeks now on a SD-DVR40 upgraded with second 120GB from Weaknees. Before the clear & delete was rebooting 6-8 times per day.

[Nightfall]

I am starting to wonder if the upgrade from 3.1.1 to 6.2 caused problems if you didn't do a clear and delete everything upon the upgrade. Just a thought.

[Nightfall]

Well, after a few more reboots, which are happening about 1-2 times per day, I decided to call Directv. They said to do a clear and delete everything. Since I was all caught up on most of the shows (except a couple things I wouldn't have minded keeping but probably wouldn't have watched anyway), I did the clear and delete. I am doing it on the other Tivo as well since hockey season is coming up and I use that for all hockey recordings anyway.

So, I hope this will fix my reboot problem on my primary Tivo....

I know there are some people who did the clear and delete everything and were reboot free for 10+ days. Could those people check in to see how things are going?

[kayson712]

I know there are some people who did the clear and delete everything and were reboot free for 10+ days. Could those people check in to see how things are going?

Checking my notes, it looks like I did the clear & delete on 8/3/05. No reboots since. Did come home one day about a week ago and had to manually reboot because I had a frozen picture on my TV coming from the Tivo. A manual power off reset fixed this. These freeze frames were occurring quite frequently along with the random reboots before the clear & delete. Just keeping my fingers crossed that the reboots won't come back.

[SteveInNC]

Checking my notes, it looks like I did the clear & delete on 8/3/05. No reboots since. Did come home one day about a week ago and had to manually reboot because I had a frozen picture on my TV coming from the Tivo. A manual power off reset fixed this. These freeze frames were occurring quite frequently along with the random reboots before the clear & delete. Just keeping my fingers crossed that the reboots won't come back.

I still wouldn't trust this. I suspect that you may have delayed the issue by moving data off of some failing disk blocks, but I also suspect that the problem will come back. I never got reboots on my unit which had a failing disk, but got a freeze about once every few days. This gradually became a freeze about once every three hours.

This would be a good time to copy stuff to a new drive, while it's still a viable image. I waited too long for my unit, and the copied disk image wouldn't boot (lots of errors during the copy). I had to find an old 3.1 image to load, then let the whole thing upgrade again after replacing/upgrading the disk. I haven't had any problems since.

At the very least, back up the current image you have to a PC in case it does fail on you later.

[BTUx9]

I still wouldn't trust this. I suspect that you may have delayed the issue by moving data off of some failing disk blocks, but I also suspect that the problem will come back. I never got reboots on my unit which had a failing disk, but got a freeze about once every few days. This gradually became a freeze about once every three hours.

This would be a good time to copy stuff to a new drive, while it's still a viable image. I waited too long for my unit, and the copied disk image wouldn't boot (lots of errors during the copy). I had to find an old 3.1 image to load, then let the whole thing upgrade again after replacing/upgrading the disk. I haven't had any problems since.

At the very least, back up the current image you have to a PC in case it does fail on you later.
Sorry to be rough, but please stop saying it's a HD problem when this thread is specifically for non-HD issues regarding 6.2 on older dtivos.

Linux is quite good about logging errors about failing HDs, and for those experiencing the 6.2 issue, those errors are not showing up.

I'm not saying that nobody posting in this thread has HD issues, but giving advice as if they were, when there's no evidence of it, you're just wasting a person's time and money and giving them false hope.

p.s. The previous poster's symptoms being from just a failing HD is extremely unlikely.

[Dan Collins]

FWIW, I can force a reboot on demand. I just attempt a "Quick Reload" of TiVoWebPlus 1.2.1. This causes a reboot with the following written to tverr.log:
Aug 25 20:25:36 (none) TmkAssertionFailure[14717]: (DumpArenaAndBlocksAndDie, line 1472 ())
Aug 25 20:25:36 (none) tivosh[14717]: Tmk Fatal Error: Thread tivosh <14717> strayed!
Aug 25 20:25:36 (none) tivosh[14717]: bt -t /tvbin/tivoapp
Aug 25 20:25:36 (none) tivosh[14717]: read 0x2aaa8000 /lib/ld.so.1
Aug 25 20:25:36 (none) tivosh[14717]: read 0x2ab04000 /lib/libutil.so.1
Aug 25 20:25:36 (none) tivosh[14717]: read 0x2ab48000 /lib/libdl.so.2
Aug 25 20:25:36 (none) tivosh[14717]: read 0x2ab8c000 /lib/libpthread.so.0
Aug 25 20:25:36 (none) tivosh[14717]: read 0x2abe8000 /lib/libm.so.6
Aug 25 20:25:36 (none) tivosh[14717]: read 0x2acb0000 /lib/libc.so.6
Aug 25 20:25:36 (none) tivosh[14717]: 0x013b3e3c 0x013b3c90 0x013b3f84 0x00f58234 0x00f9312c 0x00fd98d0 0x00f9e50c
Aug 25 20:25:36 (none) tivosh[14717]: 0x00fb7a28 0x00f8eb18 0x00f96cac 0x00fb7a28 0x00f8eb18 0x00fd99ec 0x00fdd23c
Aug 25 20:25:36 (none) tivosh[14717]: 0x00f58150 0x00612c48 0x00403090 0x2acc13fc
Aug 25 20:25:36 (none) tivosh[14717]: Tmk Fatal Error: Thread tivosh <14717>: assertion failure
Aug 25 20:25:36 (none) tivosh[14717]: Tmk Fatal Error: Thread died due to signal -2
Aug 25 20:25:36 (none) tivosh[14717]: Invoking rule 834: rebooting system
It would appear that the problem is simply that if the TiVo gets too busy, it can't catch back up.

This is also on a TiVo that runs flawlessly otherwise. This is NOT a disk problem, this is a bug in the software, probably related to whatever they did to speed up operational performance.

[Nightfall]

Dan,

If it is a bug in the software, wouldn't it affect all Tivos? Why have only some 6.2 users been hit with this bug?

There is part of me that thinks that the upgrade from 3.1 to 6.2 didn't really upgrade very nicely. Some databases didn't upgrade well. Which is why those people who did a clear and delete everything post 6.2 aren't having issues for the most part.

I guess we will see I suppose.

[BTUx9]

Which coincides with someone else's observation that his reboots only occur while indexing... that could be why some machines that are rebooting very often will stop if the satellite is disconnected... possibly.

Nightfall: some people who use AlphaWolf's 62small have had the issue, which wouldn't happen if it were a database condition problem... I think it's a combination of factors, so that many people's systems aren't stressed enough to have it occur very often. At least, that's my current theory :rolleyes:

Dan: is this on the replacement RID unit from D*?

[Dan Collins]

Dan,

If it is a bug in the software, wouldn't it affect all Tivos? Why have only some 6.2 users been hit with this bug?

There is part of me that thinks that the upgrade from 3.1 to 6.2 didn't really upgrade very nicely. Some databases didn't upgrade well. Which is why those people who did a clear and delete everything post 6.2 aren't having issues for the most part.

I guess we will see I suppose.My TiVos don't reboot unless I load them up with work.

Bottom line, no matter what I do with TiVoWebPlus, there should NOT be an assertion error in tivoapp. I could see video interruption, a failed recording, or other problems, but there is only word to describe what I've seen - a bug.

I suspect that at least some of the speed improvement was attained by "streamlining" the error handling code.

[BTUx9]

My TiVos don't reboot unless I load them up with work.

Bottom line, no matter what I do with TiVoWebPlus, there should NOT be an assertion error in tivoapp. I could see video interruption, a failed recording, or other problems, but there is only word to describe what I've seen - a bug.

I suspect that at least some of the speed improvement was attained by "streamlining" the error handling code.
And there's ample evidence that 3.1 boxes when loaded with work did NOT assert and die. (except for those running at setpri fifo 1)

[Dan Collins]

...Dan: is this on the replacement RID unit from D*?I can reproduce it on the Philips I got from D*, as well as both the SD-DVR80 and the SIR-S4040. If I exit TivoWebPlus and then restart it manually, all is well. It is ONLY when I try to restart from the menu that it causes a problem. I'm guessing that the start sequence begins before all the resources are released from the stop, and the TiVo runs out of either memory, processor power, or both.