TiVo Community Forums Archives

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

Bad B drive...
(Click here to view the original thread with full colors/images)

Posted by: bbsux

Guys... Here's my situation:

I have a dsr 6000 with a 120 gig wd A drive and a maxtor 80 gig B drive.

Apparently the 80 gig has started to fail...

What are my options?

Can I DD the B drive to a bigger one and expand or am I stuck with 80 gig even if I use a 120 gig?

(I'm trying to save my recordings....)

Posted by: Robert S

Expanding the B drive multiple times is not a problem. Just use mfsadd (on both drives, naturally) after dd completes.

Posted by: bbsux

Ahh... Very cool... But I assume axpanding the A drive is a big NO-NO then....

Posted by: bbsux

guys I decided to copy both drives with mfstools....

Got a 120 thats same as A drive and the 120 to replace B drive...

do I type this command:
mfsbackup -Tao - /dev/hda /dev/hdb | mfsrestore -s 127 -zpi - /dev/hdc /dev/hdd

or

mfsbackup -Tao - /dev/hda /dev/hdb | mfsrestore -zpi - /dev/hdc /dev/hdd

Drive designations are right I just need to know if I need to reset swap on same size drive... My guess would be no....

Also I like to run mfsadd later by itself... Is this a problem or do I need the 'x' in the command line?

Posted by: Robert S

The -s 127 on the restore side recreates the 127Mb swap partition on the new A drive.

The problem with the A drive is that there are only 16 entries in a TiVo partition table and there are 9 system partitions on the A drive. As current TiVoes ship with two pairs of MFS partitions on the A drive, that means there's only room for one upgrade pair.

I'm not sure why you'd want to run mfsadd separately. It seems more reliable to restore with -x.

If you want to do it that way, restore with -l (that's an L). That provides a work-around for the partition problem - when you restore with -x or -l, MFS Tools tries to move MFS partitions on to the B drive to make room for further expansion of the A drive.

Posted by: bbsux

yeah but the drive that is being copied already has the expanded 127 meg swap... Does it get knocked out or something?

I mean isn't putting it in allocating ANOTHER 127 meg on a same size drive which will error out?

As for the -x I have had times where it didn't expand as it should... and as a consequence I always run it seperate now...

do I have to put the 'l' in if I am going to run without the 'x'? I don't care about adding space to the A drive....

all I'm am doing is copying the A drive to another of exact same size and copying the B drivce to a 120 from a 80... So I'll need the mfsadd afterwords...