TiVo Community Forum banner
1 - 20 of 33 Posts

· Registered
Joined
·
5 Posts
Discussion Starter · #1 ·
I have a TCD540040 and I'm trying to replace the 40g maxtor TiVo drive with a Caviar 320g hd...i have everything connected correctly in my PC, i booted the Weaknees_lba cd and entered the following command

mfsbackup -f 9999 -so - /dev/hdb | mfsrestore -s 127 -r 4 -xzpi - /dev/hdd

and got the following error message

mfsbackup: Backup failed to startup. Make sure you specified the right devices, and that the drives are not locked.

I tried replacing the drive letters, but no success. I understand that people have had this problem in the past, but i couldn't find any threads with a good explanation of whats going on....HELP!!
 

· Registered
Joined
·
100 Posts
According to what you wrote, it seems that your original TiVo hard drive (the 40GB Maxtor) is the Primary Slave and your new hard drive (the 320GB one) is the Secondary Slave.

If all you are doing is a direct copy to your new drive, I believe you should type:

mfsbackup -Tao - /dev/hdb | mfsrestore -s 160 -r 4 -xzpi - /dev/hdd
 

· Registered
Joined
·
2,198 Posts
First for a 320G drive the swap should be at least 160.
Do you have the 40G original drive connected to the primary channel slave
the 320G on the secondary channel slave?

from the command line type dmesg | grep ide find where your drives are actually connected in the output
 

· Registered
Joined
·
5 Posts
Discussion Starter · #4 ·
HomeUser said:
First for a 320G drive the swap should be at least 160.
Do you have the 40G original drive connected to the primary channel slave
the 320G on the secondary channel slave?

from the command line type dmesag | grep ide find where your drives are actually connected in the output
Yup, thats how its set up. What do you mean by "the swap should be at least 160"?
 

· Registered
Joined
·
5 Posts
Discussion Starter · #5 ·
i typed in exactly
dmesag | grep ide
and it said that the command wasnt found...

i tried doing
mfsbackup -Tao - /dev/hdb | mfsrestore -s 160 -r 4 -xzpi - /dev/hdd
that mjitkop suggested, but i got the same error...help help help!!!!!
 

· Registered
Joined
·
2,198 Posts
To prevent possible TiVo recovery errors in the future the swap file needs to be larger. The consensus is that 1M of swap is needed for every 2G of storage. Replace the -s 127 with -s 160 in the mfsrestore options. After the copy/expand is complete you need to run the program tpip to fix a known issue with swaps larger then 127 created with mfsrestore.

If dmesg reported that the drives are in the correct locations the check your typing very carefully. Note: the mfsbackup command you typed is not copying the recordings the options in mjitkop post will.

See if mfsinfo /dev/hdd reports valid information about your original TiVo drive.
 

· Registered
Joined
·
5 Posts
Discussion Starter · #7 ·
HomeUser said:
If dmesg reported that the drives are in the correct locations the check your typing very carefully. Note: the mfsbackup command you typed is not copying the recordings the options in mjitkop post will.

See if mfsinfo /dev/hdd reports valid information about your original TiVo drive.
the mfsinfo /dev/hdb (my original tivo hd is in b) gives me the following message

Second MFS Drive Needed: No such file or directory
Second MFS Drive Needed2: Illegal seek
Second MFS Drive Needed: No such file or directory
Second MFS Drive Needed3: Illegal seek
mfs_load_volume_header: Total secotors(78703616) mismatch with volume header (703819776)
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!

Can you make sense of that?
 

· Registered
Joined
·
2,198 Posts
I thought I read on these forums that a larger swap is no longer the way to go. The reasoning was because only a failing hard drive would need it and that a failing hard drive never gets better.
Or anything that causes a re-index of the (now larger) database could be a new version of software, a hickup while downloading data... Id rather trade off a hundred meg of recording time now JIC. It is very difficult to add the extra swap later.
 

· Registered
Joined
·
1,969 Posts
Try the PTVupgrade CD ver. 4.01 instead:
http://www.ptvupgrade.com/products/software/lba48/index.html

Or try using a different PC for the upgrade.

As for swap, you can use 127 for now. If you do finally get it working, then do it again with the more complicated bigger swap and the "tpip" command. Speaking from experience, a few people have screwed up the tpip command and it's one complication the OP doesn't need right now.
 

· Registered
Joined
·
2,589 Posts
To the OP:

Your 40G drive is probably locked. Check to see what drive size is being reported by Linux during startup. If it reports 9 or 10 GB, you have a locaked drive. You need to run qunlock (which must be run under DOS) to unlock the drive.

Regarding swap - the -r 4 setting is changing the block size used on the disk. This reduces the total number of blocks for a given amount of diskspace. The end result is that 127MB of swap is sufficient, so tpip is not required.
 

· Registered
Joined
·
5 Posts
Discussion Starter · #13 ·
Dan Collins said:
To the OP:

Your 40G drive is probably locked. Check to see what drive size is being reported by Linux during startup. If it reports 9 or 10 GB, you have a locaked drive. You need to run qunlock (which must be run under DOS) to unlock the drive.
Its not locked...I scrolled up and it reports all of my hard drives as the correct sizes.
 

· Registered
Joined
·
2,589 Posts
thespotlessmike said:
the mfsinfo /dev/hdb (my original tivo hd is in b) gives me the following message

Second MFS Drive Needed: No such file or directory
Second MFS Drive Needed2: Illegal seek
Second MFS Drive Needed: No such file or directory
Second MFS Drive Needed3: Illegal seek
mfs_load_volume_header: Total secotors(78703616) mismatch with volume header (703819776)
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!

Can you make sense of that?
This would appear to indicate that the 40GB drive was part of 2 drive set (IOW a second drive had previously been added to the unit). If not, you've got a problem with the 40GB drive. Does the TiVo boot with the 40GB installed?
 

· Registered
Joined
·
13 Posts
Hey guys. I just picked up the TCD540040 and bought a 250GB hard drive to go in it. Exactly like thespotlessmike stated in the first post.

I've spent the last two to three days trying to get the whole formatting to work.

Downloaded MFStools2.0 and have been following the link on Hinsdale and also at weaknees.

The problem is that nothing I try works. I've tried backing up the original over, that doesn't work. I've tried a direct transfer (mfsbackup...|mfsrestore...) and that doesn't work. So I wanted to see what kind of info my source drive displayed.

I just typed in mfsinfo /dev/hdc (my original 40GB TiVo) and got this message:
Second MFS Drive Needed: No such file or directory
Second MFS Drive Needed2: Illegal seek
Second MFS Drive Needed: No such file or directory
Second MFS Drive Needed3: Illegal seek
mfs_load_volume_header: Total secotors(78703616) mismatch with volume header (567095296)
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!

I don't think my drive is locked because I can read the right value for the size of the hard drive.

I don't think this drive was ever used as a Dual drive TiVo, but I'm not sure since I did buy it used.

Any help? I'm completely stuck right now.... Thanks in advance!
 

· Registered
Joined
·
13 Posts
HomeUser said:
Did your TiVo have the original drive? Does the TiVo work with the drive? If not you need to obtain a preloaded drive, an image or purchase InstantCake
From what I can tell, the HD in the TiVo was the original. Secondly, the drive does work with the TiVo. It funtioned like a regular 40GB TiVo.

When I get home from work today I'm thinking of plugging the original drive back in to the Tivo and ensuring that it still works.

Say it didn't, is there an easy way for me to format the new hard drive so TiVo can read it. I'm not interested in the data on the original 40GB hard drive.

Thanks!
 

· Registered
Joined
·
2,198 Posts
If it works in the TiVo then mfsinfo should recognize the drive. Check to be sure the drive is really where you think it is use cat/proc/partitions or dmesg | grep ide
 

· Registered
Joined
·
13 Posts
HomeUser said:
If it works in the TiVo then mfsinfo should recognize the drive. Check to be sure the drive is really where you think it is use cat/proc/partitions or dmesg | grep ide
Thanks for the help. I'll take a look and see if the drive still works. I'm 100% I was accessing the drive correctly with the command.

You seem to know a lot about this, when I typed MFSINFO /dev/hdX and got the error, what do you think would cause that kind of an error message? Damaged drive? Inproper access?
 

· Registered
Joined
·
2,198 Posts
Looking at the error from the output of "mfsinfo /dev/hdc" mfs_load_volume_header: Total sectors(78703616) mismatch with volume header (567095296)
78703616 * 512 = 40Gig
567095296 * 512 = 290Gig

Looks like mfsinfo thinks the drives are married 40G + 250G
If the 40G does not work by its self in the TiVo try mfsinfo /dev/hdc /dev/hde (if the 250G is on the secondary channel as the primary drive)

Also interested in the abbreviated output of the commands from the previous message.
 
1 - 20 of 33 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top