TiVo Community Forums Archives - Problem reinstalling .bak on second drive?

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

Problem reinstalling .bak on second drive?
(Click here to view the original thread with full colors/images)

Posted by: coffeo

My model 312 died with the following symptom -- constant reboot at "please wait a few sec's screen". I used MFS to add a 80mb second drive last year -- working perfectly until yesterday. After reviewing forum and opening tivo box, sounds like original 10mb drive is shot (constant whine).

I believe the best strategy is to use the secondary 80mb drive (still OK -- I believe) as sole drive. I am following MFS instructions to reinstall TIVO.bak onto this drive.

Two issues:

(1) After bootup, LINUX is NOT recognizing the 80MB tivo drive giving the error messages: Invalid geometry and 0 physical heads.

(2) Ideally, I'd like to run a diagnostic on the 80mb drive, but since I'm running XP, MFS suggests this is a major risk (and I don't want to partition, etc.)

I welcome any advice on how to proceed.

Thanks.

Posted by: stevel

Be sure that you have jumpered the drive properly.

Use a floppy-based diagnostic as sipplied by the drive manufacturer.

Posted by: Robert S

Sounds to me like it's the 80Gb drive that's failed.

If you give up on the failed drive (and thus lose your recordings), you should be able to restore the backup to the original A drive. Note that this is a slightly special case, so use the alternative command line that Hinsdale provides for restoring to the original A drive.

Posted by: coffeo

Great call (hopefully). I ran diagnostics on both drives and the 80MB fails the test and the 10MB master is clean (after a full test).

Next step -- try to get the .bak on to the original drive.

Thanks. (and please stand by if i can't make it work).

Posted by: coffeo

All fixed.

Thanks for the helpful and prompt response.