If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

HR10-250 Rebooting when scanning for OTA channels

Wanted to see if anyone has heard of this one. Whenever I go into the settings and have my HR10-250 try to scan for OTA channels (Just put up a new antenna) it reboots. In checking the tverr log the below pasted error is found. This unit is running 3.1.5f with networking, mfs_ftp, tivowebplus 1.2.1, elseed, tivotitle, encryption disabled, sort always on, and busybox hacks all setup. Any help will be greatly appreciated... btw, the unit also reboots when I accidentally change channels to one I don't receive instead of showing the usual blue banner saying the channel isn't available (Noticed this one when I sat on the remote and the unit tried to change to channel 1). Unit has been running fine for months on end.

Same Problem

I am having the same problem, except for that it is consistently doing this on normal satellite only. I have not set up ota channels yet. Seems to be in an endless rebooting loop. Always reboots while downloading the satellite programming. If I unplug the LNB, unit runs fine playing recorded items from dvr list. I have the same log info...

Well my issue turned into a constant reboot loop just the other day. I re-imaged the TiVo and went back to stock 3.1.5f un-hacked. I'll run it that way for now and see what happens. This is the second of these units I've had that turned into a constant reboot piece of crap... Apparently no one here knows how to decypher the errors we've been posted.

HR10-250 Reboot Loop

Add me to the list. I had my secondary 250gb drive hacked and working fine for a couple weeks so I blessed the original drive and installed a twin breeze. Now I get to 95% on acquiring signal and it reboot. Tried a bunch of different drive and jumper configs and the only way I can get it work is with no OTA or Sat lines attached and only the primary hacked drive installed.

Has anyone figured out why this is happening? I did manage to shock the *!@#* out of myself when I accidentally brushed across the copper square thing next to the drive. Ouch!

Will I have to have Directv replace my Tivo? Do they warranty it if I bought it off eBay?

This has happened to me twice now, getting to 95% and rebooting, and no one has been of any help at all.

Each time I have had to go back to a non-hacked image and re-hack. This time I stayed non-hacked for a week and nothing happened, didn't even reboot at all. I just re-hacked the other day and so far so good.

I had to do the same thing. I restored the un-hacked image to my original drive that I had tried to bless to the hacked drive and everything works fine now. I am going to re-hack the original drive and then try again to bless the secondary in.

Is it possible the bless command is messing something up? Should I try taking both drives out and running mfsadd?

I left mine un-hacked for a week and re-applied all except for elseed and tivotitle and it's now been running about 2 weeks hacked again. This is what I did before and it happened all over again after a few months so who knows.

You probably haven't gotten a reply because nobody knows the answer to your problem. I've never seen it myself and I have three HDTivos. Most likely you restored a bad image or something got hosed during the backup/restore process that's causing the glitch to occur. Go back over your process and look for any errors that you may have induced in the command line you entered. There are known issues when restoring images to large hard drives that are not documented in Hinsdale's so I'd start by doing a search on that topic. Some people have had problems when using mfsadd for expanding large images. Also make sure you used the proper switches in the restore process. This post at the TCF may be of some help:

Please don't PM me or any other members looking for personal assistance. You'll do better by posting (after you've exhausted the search feature, of course) and taking advantage of the collective expertise of the membership instead of a single individual that may or may not be able to help you. Thank you and enjoy your stay at DDB!

Sorry, I missed that part about it working for months prior to the reboot issue. My first inclination would be a drive failure. A hard drive can apparently work fine but yours may be deteriorating at a slow rate and the reboot may be occurring only when certain things happen like the alignment of the planets. I'd definitely recommend running a non-destructive diagnostic on the drive to see if there's an issue with the drive. If that checks out OK then I'd recommend re-imaging the drive and see how it goes.

Please don't PM me or any other members looking for personal assistance. You'll do better by posting (after you've exhausted the search feature, of course) and taking advantage of the collective expertise of the membership instead of a single individual that may or may not be able to help you. Thank you and enjoy your stay at DDB!