Upgraded, now won't work

[jshaffernc]

I went to upgrade my daughter's relatively new Series 2 40 hour unit. Bought a Seagate 250 GB replacement drive. I set the new drive up as a master and the old one up as slave (old one had been set to CABLE SELECT).

I issued the backup restore commands from the instructions, but I got a failure/success. I see why the failure, but the success spooked me.

Figured out I'd gotten the old drive in ok, but the new drive wasn't being recognized, so I fixed that, verified both drives were properly installed, and reissued the command.

Took about an hour to process, said it processed 38 odd GB. Told me I now had 237 hours or so. Everything looked perfect.

I installed the new drive in the Tivo, shut it up then realized I hadn't reinstalled the jumper to make it a master again. I opened it up and installed the jumper to make it a master, reclosed it and sent it home with her (70 miles away).

Of course, it failed. :( "Powering Up" hang. She has no torx drivers, so I have some time to obsess over it.

The original drive had been set to CS. I believe I set the new one to "master". I'm assuming I did something wrong there rather than software. If it is the jumper, I can deal with that. Any chance it's the copy process?

[funtoupgrade]

Jumper should work fine on master. Can you list the exact commands you used for the copy process?

[mick66]

237 hours seems short by about 50 hours, unless this is a DirecTV Tivo.

[jshaffernc]

The command I used was straight from the automated instruction sheet. It had an mfsbackup command piped to an mfsrestore command.

First time, when the destination drive was not recognized, it said it couldn't find something, then (apparently from the piped restore) it declared success, but did not report any numbers. I assumed it had essentially a null input and was happy with that. Took 5 seconds.

Second time, with both drives recognized, as I watched it work, it seemed to "backup" a gig or two, then "restore" that same gig or two as it counted up to the 38 gig or so from the original drive. Then it declared success, showing me the new capacity. I could have remembered the new capacity wrong, I don't have a printer attached to the shell PC I use for this, so I couldn't print.

So, I'll drive up to Baltimore and fiddle with the jumpers (I always seem to get them backwards for some reason....) and failing that here's a question:

Can I use the original disk from my dual tuner tivo to bake the new disk on her series 2 (540040)? Is the software generic enough to recognize it's not in a dual tuner unit?


Thanks,

Jim

[rainwater]

Can I use the original disk from my dual tuner tivo to bake the new disk on her series 2 (540040)?

No, it will not work.

[jshaffernc]

OK, I'll start over from scratch, testing her original drive. If it's shanged, it could explain everything. Can the Mfsbackup command or mfsrestore command shang a source drive? It was the destination drive that was unrecognized, so since the operating system couldn't see it, it should be fine, I'd say.

This, I think, is the exact command I issued:

mfsbackup -Tao - /dev/hda | mfsrestore -s 127 -r 4 -xzpi - /dev/hdb

I carefully checked to ensure hda and hdb referred to the correct drives before issuing.