mfsadd not working properly

[BL]

I have added drives, expanded, etc. before without problems, but this time I am running into difficulties on replacing drives and increasing space on an S1:

1. Unit had 15GB A drive (which was failing) and 80gb B drive. My plan was to replace A drive with 120gb Seagate. I could not get a backup, so I dd'd the A drive to the Seagate, then put it back in the Tivo with the original B drive. After an initial gsod, the unit fixed itself, re-booted fine, worked fine.

2. I pull out the drives to put them back into PC to expand the A. PC does not recognize the original B drive, after running diagnostics, calling Maxtor, etc. I decide it is dead and go get another Seagate 120. Since A drive already dd'd, I assumed i just had to expand and mate the drives.

3. I put the two Seagates into the PC at hda and hdd. Bios and boot up shows both at 120gb.

4. I typed in mfsadd -x /dev/hda /dev/hdd (with the copied, unexpanded A drive at hda and the new seagate at hdd) and got the following response:

/dev/hdd2: success
/dev/hdd3: illegal seek
mfs_load_volume_header: total sectors (25826304) mismatch with volume header (185912320)
mfs_load_volume_header: loading anyway
mfs_load_zone_map: primary zone map corrupt, loading backup
mfs_load_zone_map: secondary zone map corrupt, giving up
mfs_load_zone_map: zone map checksum error
unable to open mfs drives

My assumption is that the failing A drive was so corrupted that when I copied it over, what copied was also corrupted or incomplete, and it is preventing mfsadd from working properly, but that seems odd considering the Tivo seemed to work fine when I re-inserted the drives (back before the B drive failed).

My question is whether I should try starting over using dd rescue with the knoppix boot cd, or is there some better way to proceed given the responses I got when I tried mfsadd.

Any help would be appreciated.

Thanks,

[JamieP]

...Since A drive already dd'd, I assumed i just had to expand and mate the drives. This was your flawed assumption. The A drive was already mated to the old B drive. You can't simply remate it to a different drive.


My question is whether I should try starting over using dd rescue with the knoppix boot cd, or is there some better way to proceed given the responses I got when I tried mfsadd.If your old B drive isn't working at all, your best bet may be to find a replacement image and start over from scratch.

[HomeUser]

If TiVo was working with the new Seagate 'A' drive and the old 'B' drive the 'B' drive is probably ok. I would try and dd the 'B' drive to the other Seagate 120 first before giving up.

What is telling you the "PC does not recognize the original B drive"?

[BL]

The old B drive spins up (I can hear it), but after I took it out of the Tivo and moved it back to the computer to expand it, it appears to have stopped working. The bios display indicated only one drive was attached to the computer (the new A drive, not the old B drive) even though both were connected.

Then, when I booted using the mfs tools boot disk, the computer saw only the new A drive. The display reported the new A drive at full size, but nothing at all for the old B.

I have tried several different ide connections which all worked for the new A (the computer saw a drive at that connection) and I have tried different jumper settings, called Maxtor, etc. Computer still acts as though drive is attached.

Also, I left out the detail that when I put new A and old B back into Tivo, it no longer booted. So, I am pretty sure the drive has had it, but I am willing to try other steps to get the Old B working if anyone has any ideas.

[BL]

Assuming JamieP is correct, is there a way to "unmate" my new A drive so I can add the B drive to it? I would prefer not to have to load a five year old image and start over if I don't have to.

As another piece of infromation, after I was unsuccessful in trying to expand and pair the new (copied) A drive with the new B, I did try the following command to try to just expand the new A drive from 15gb to 120gb: mfsadd -x /dev/hda

I got error messages which were similar to the ones I got when I tried it with two drives.

Any ideas on where to go from here would be appreciated.

[JamieP]

Assuming JamieP is correct, is there a way to "unmate" my new A drive so I can add the B drive to it?That's something Tiger was working on when last seen around here: link (http://archive2.tivocommunity.com/tivo-vb/showthread.php?t=226416). As far as I can tell, that version was never debugged, and is badly broken.
Any ideas on where to go from here would be appreciated.The path of least resistance is to buy an instantcake image and start over.

[BL]

Thanks. Since I do have an old backup, I may try that first. If it does not work, I can always go buy an image.

I don't remember the software version of the backup, but if it is pre-3.11 will it still be automatically updated to the last (and latest) S1 software version?

[JamieP]

I don't remember the software version of the backup, but if it is pre-3.11 will it still be automatically updated to the last (and latest) S1 software version?I assume so, but I don't know for sure on an S1.