Restore Failure

[sprust]

My Tivo has two 120gig disks in it. Following Steve Conrad's wonderful instructions I backed them up using the following command:
mfsbackup -l 32 -6so /mnt/dos/tivo.bak /dev/hdc /dev/hdb
Now I want to restore this to a single 320gig disk using the command:
restore -x -r 4 -s 300 -zpi /mnt/dos/tivo.bak /dev/hdc

Even though the new disk is showing as its correct size the restore fails with ‘backup target not large enough’.

I’ve found other posts that talk about the backup ‘not divorcing’ properly but I really don’t understand how to get around the problem.

Could someone please advise me.

[ukcobra]

I am having the same problems, with 2 400GB disks this morning as well. The MFSTools 2 ISO is being used, and we are getting some wierd disk sizes being reported back as well.

We are trying a basic restore from 1 disk to another.

As it has failed, we are now just doing a dd from one to the other.

Would like to know the solution to this for future use.

Mark

[blindlemon]

Originally Posted by sprust

I’ve found other posts that talk about the backup ‘not divorcing’ properly but I really don’t understand how to get around the problem.

That is the problem aright. The solution is either to restore to a twin-drive setup or to delete the recordings that are preventing your backup divorcing before you make the backup. To do this properly you will need network access and my DeleteAll script.

[ukcobra]

My problem was resolved by using a machine that can handle a greater than 137GB disk in the Bios.

400GB took almost 6 hours to copy onto the Samsung.

[sprust]

OK Thanks. I've taken an easier root and resorted to using a really old backup I took from my original single 40gig drive back in 2002.

Now that I've got my single 320gig disk version with the replaced kernel, would I be right in my assumption that I can make a backup from it and restore that to another single big disk using exactly the same backup and restore commands but simply skipping the copykern step?

[Cainam]

As I understand it, you would still need to run copykern on any future large disk you restore the image to.

While you may have the new kernel, and you may have defined the swap partition properly with the restore command, the swap partition you need for Tivo to run correctly will not be initialised properly. Copykern will do that for you.

There are other ways of initialising the swap partition, but copykern is the easiest!

[blindlemon]

Originally Posted by Cainam

While you may have the new kernel, and you may have defined the swap partition properly with the restore command, the swap partition you need for Tivo to run correctly will not be initialised properly. Copykern will do that for you.

Correct. Always run copykern - it only takes a few seconds

[sprust]

Many thanks indeed - it's wonderful having real experts on hand!