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



Desperate for Help!

(Click here to view the original thread with full colors/images)



Posted by: DeadHDVR2/3

Dear Tivo Community:

I am desperate for some help! I did exactly as Hilsdale told me to do on myupgrade on my HDVR2/3, and I still have the GSOD. I waited overnight, and that didn't heal it? Is there any way to go back and start over without killing my original files?

Drive A - supplied by Huges Maxtor 40GB
Drive B - WD 100GB

Thank you in advance, I have a wife to answer to!



Posted by: ThreeSoFar

There is if you did (and tested) a complete backup before you ran into this problem.

More detail in what you tried might help us troubleshoot.

Spelling Hinsdale's name wrong might not be the best way to start your plea, though...



Posted by: DeadHDVR2/3

I followed the directions exactly from Hinsdale for the Series 2. I did a backup of A, did a restore to B (new drive), and the only thing I skipped was to test B. I proceeded to update the capacity (mfsadd) and then put the drives in the Unit, and Poof! GSOD. I was using the Floppy version of the tools. Thank you for your help!



Posted by: DeadHDVR2/3

Okay, from the Hinsdale directions, this is exactly what I did:

1) removed A drive from Tivo Unit
2) put A drive from Tivo Unit on Secondary IDE Master
3) put B drive (with some old data on it) on Primary IDE slave
4) used Option 1 - Backup a single Tivo Drive - using the command mkdir /mnt/dos
mount /dev/hda1 /mnt/dos

then: mfsbackup -f 9999 -6so /mnt/dos/tivo.bak /dev/hdc

5) did a restore to B drive using mfsrestore -s 127 -bzpi /mnt/dos/tivo.bak /dev/hdb and got a report that it was a successful restore
6) Then I issued the command mfsadd -x /dev/hdc /dev/hdb and got the announcement that I now have 151 hours.

7) I changed the jumper on the A drive to Master and made sure the B drive was on Slave and installed the A drive to the end of the cable, the B drive to the middle. That's when things went GREEN. If you need anymore info please let me know. Thank you a ton for your help!
Michael



Posted by: Robert S

Well, there's nothing wrong with what you did.

If the GSOD is staying up, then I'd let it run at least overnight. Occasional reboots are normal, but if it's rebooting every few minutes then it's not doing useful work.

Sometimes upgrading does cause a GSOD for reasons that aren't apparent, but it doesn't necessarily indicate a serious problem.



Posted by: ThreeSoFar

That's the detail I was looking for, thanks.

OH! I think I see a problem. You're calling "drive A" your old TiVo's drive. But in the new configuration, it's going to be the second drive in the TiVo, usually called the B drive. As such, that one should be slave to the new drive A, not the other way around, as you state in #7 above. Now if you've used drive A and B ambiguously and are sometimes referring to the old A drive as the new B drive, then this may not be your problem. In that case, read on.


I don't see any problems with getting primary/secondary master/slave wrong anywhere.

You hopefully have a valid .bak image (this is untested at the moment since you skipped that step).

I would start over from the restore onto what you're calling drive B, but do not skip the single-drive boot of the just restored image. This confirms that drive and the image both work.


Since you went ahead and added the second drive (which if I'm right was your original TiVo drive? And so now your only copy of your old system is the untested .bak image), and then things went GSOD it could be:

1) a bad .bak image

2) a bad brand new drive (which you're calling "drive B", though it seems to be your primary TiVo drive in the ultimate configuration)

3) a bad mfsadd result; or

4) a bad original TiVo drive so it didn't take the mfsadd...

Your mfsadd syntax I'm no help with. Like I said, I usually do drive replacements and stick with one drive per TiVo.



Posted by: bidger

I know that for older HdDs, there were compatibility issues between Maxtor & WD. I don't know if this was ever resolved, I've only used Maxtor for my upgrades.



Posted by: DeadHDVR2/3

Okay, here's what I did now -

I restored the backup to the new drive, tested it, and just decided to skip using both drives. BUT, I would like to someday use both drives, so if anybody has a tip for me on how to make it work, I would appreciate it.

The tivo.bak file worked well though. I now am at 106 hours (Tivo reports 87 hours)! Much improved over the 35 hours from before! TIVO rocks!

Thank you all for your help!



Posted by: ThreeSoFar

Great! Could be the original TiVo drive chose this time to die on you. Good think you got the .bak first!





vBulletin Copyright ©2000 - 2009, Jelsoft Enterprises Limited.
vB Easy Archive Final ©2000 - 2009 - Created by Stefan "Xenon" Kaeser Modified by Adam J. de Jaray