TiVo Community Forums Archives - Many problems upgrading

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

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

Posted by: mck321

I absolutely cannot get my upgrade to work. I am upgrading a Sony
SVR-2000 30 hour unit to a 120 gb Samsung HD.

Last weekend, I loaded the original 30 GB Tivo drive along with the new 120 GB drive into a PC, made a MFSTools 2.0 boot CD and tried to copy one drive to the other. The process booted up without any problems and I was able to execute the dd command. After 5 hours the process finished but when I put the new drive in my tivo, it would not start up.

Since that didn't work, I decided to try making a backup imagine on to a DOS drive and restoring the image to the new drive this weekend. My current setup is as follows:

hda: 8GB DOS Drive
hdb: 120GB "New" Tivo Drive
hdc: CD-ROM
hdd: 30GB "Old" Tivo Drive

The 8GB DOS Drive is freshly formatted, completely empty, and is FAT32. When I boot MFSTools all 4 drives are recognized and are the correct size. Here is what happens to me, however:

/# mkdir /mnt/dos
/# mount /dev/hda1 /mnt/dos
/# mfsbackup -6so /mnt/dos/tivo.bak /dev/hdd
Primary volume header corrupt, trying backup.
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!
mfsbackup: Backup failed to startup. Make sure you specified the right devices, and that the drives are not locked.
/# mfsbackup -6so /mnt/dos/tivo.bak /dev/hdd
/mnt/dos/tivo.bak: Read-only file system

Can anyone assist me? My Tivo is dead in the water and I'd really like to get it working. Thanks in advance.

Posted by: mck321

The old drive appears to be flaky. I think I'd be better off trying to find an image from another source. Here is what happens if I try to use mfsinfo to get information on my old drive:

/bin# mfstool info /dev/hdb
Primary volume header corrupt, trying backup.
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!

/bin# mfstool info /dev/hdb
/dev/hdb10: Success
mfs_load_volume_header: mfsvol_read_data: Input/output error

/bin# mfstool info /dev/hdb
/dev/hdb10: Success
mfs_load_volume_header: mfsvol_read_data: Input/output error

/bin# mfstool info /dev/hdb
MFS volume set for /dev/hdb
The MFS volume set contains 2 partitions
/dev/hdb10
MFS Partition Size: 512MiB
/dev/hdb11
MFS Partition Size: 27661MiB
Total MFS Volume size: 28173MiB
Estimated hours in a standalone TiVo: 30
This MFS volume may be expanded 5 more times

As you can see, if I type the command enough times it will actually give me the information. If I had to guess, the drive is toast. Could someone PM me a site where I can find an image for a Sony SVR-2000, 30 hours, 3.0.01-1-010.

Thanks!

Posted by: ThreeSoFar

I used the "mfsbackup ... | mfs restore ..." option when I did my similar upgrade(s) recently. No problems. Maybe try that?

Posted by: weaknees

It does sound like your old A drive is problematic. Did you have any problems with the TiVo before attempting the upgrade? Did you ever boot the PC with the A drive into XP?

Michael

Posted by: mck321

Thanks to all those that got me an image site:

I loaded the image for version 3.0 on to my new hard drive using mfsrestore and all seemed to go well. The process completed and I put the drive back into my TiVo to test it out.

Now when I boot up I get to the "Almost there..." screen and the system reboots immediately. I can't figure out what I'm doing wrong, but I manage to keep doing it.

Posted by: Montaño

Double check the jumpers on the Samsung drive. They are usually the culprit. :)

one example: http://www.tivocommunity.com/tivo-v...threadid=104286

Posted by: ThreeSoFar

Jumpers were confusing on the Samsung, I remember that...