TiVo Community Forums Archives - Tivo Reboots After Satellite Acquisition

TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like Google.

Pages:1

Tivo Reboots After Satellite Acquisition
(Click here to view the original thread with full colors/images)

Posted by: jeffster

After an apparent power outage caused by air conditioning contracters (although they won't admit it), my SAt-T60 (220GB over 2 drives) is FUBAR.

It will reboot, go through the startup cycle, acquire all the satellite into, and then when it reached 100%, it will reboot again.

During the time it is acquiring the satellite data, I can watch programs in my recorded shows, but eventually it finishes and then reboots.

1. Is there any way to fix this without losing my hundreds of hours of saved shows?

2. If not, is there any way to tell it "forget the satellite, just let me watch what's on disk?"

I'm thinking about getting a new HDVR2 and upgrading it, because this unit's HDs went bad about 6 months ago and I replaced them both, and now something else is flaked out (my unmodded SAt-T60 upstairs has been running fine, but I can barely stand the paltry 30 hours of programming (now more like 15-20 for some reason) it can hold.

Any thoughts on how to progress?

Posted by: weaknees

You can try hitting the TiVo button before it finishes acquiring the satellite, but I think it will continue in the background anyway. In either event, one of your drives is pretty likely damaged, and you probably wouldn't get that far with a recording anyway.

Power outages do take out drives - consider yourself lucky that the other unit is working well.

Michael

Posted by: bsnelson

Couple of thoughts:

1. Disconnect the satellite cables from the back. This will ensure that signal aquisition will never complete, and maybe it will keep the unit from rebooting. This might at least let you drain the shows.

2. Alternately, you might try running diags on both drives, and if possible, dd off the bad one onto a new drive and try that.

Brad