Registered: Aug 2001
Location: Harrow, Middlesex, United Kingdom
Posts: 1

Hi there,

After reading the very useful threads regarding UK dual drive tivo and 2.5.5 software I have made a backup using the tivoMad disk 3.2 and Msftool 1.1

I used the following command to make the backup....

# /mnt/fat/mfstool backup -o /mnt/fat/tivo.bak -6 -s -l 64 -t /dev/hdc /dev/hdd

and then restored to a Maxtor 120Gb drive using

# mfstool restore -i /mnt/fat/tivo.bak -z /dev/hdc

i thne placed this into my tivo and all was well..it booted.....all screens were present and correct.......it started to record shows etc......

However at this stage it is still unaware of the extra space.......

So i returned the drive to my pc and booted the TivoMad floppy again and went through the script.....

answered:
[1] hdc
[2] no
[3] N/A
[4] N/A
[5] No
[6] Yes
[7] No
[8] Yes

this ran the script as predicted......no errors........

Placed the drive back into the tivo and the following happened:

PoweringUp....

(reboot) as expected

Powering up....

Almost there.....

Severe warning (greenscreen of death)

(reboot) the tivo now cycles through the last three states......


What I cannot understand is if the backup was ok (shown by my restore working ok and all functions performing as expected and that this is running on my new drive) how come when i tivomad it it causes it to die......

Is there something i'm missing or should i use tivomad command line instead of the script or is TivoMad currently unsuitable for 2.5.5 machines?

Any thoughs people have would be great as i'm going greyer by the hour!

Kind Regards

Robin.

POST #1 | Report this post to a moderator | IP: Logged

Registered: Feb 2002
Location: Poole, UK
Posts: 45

you might want to look at this thread.

POST #2 | Report this post to a moderator | IP: Logged

Registered: Aug 2001
Location: Harrow, Middlesex, United Kingdom
Posts: 1

Indeed this is one of the threads i am referring to........

My questions still stand.....



R

POST #3 | Report this post to a moderator | IP: Logged

Registered: Jan 2002
Location: Somerset, England
Posts: 4390

I'm guessing here, but have tried restoring the backup and then immediately running TiVoMad, ie, without returning it to the TiVo first?

POST #4 | Report this post to a moderator | IP: Logged

Registered: Aug 2001
Location: Harrow, Middlesex, United Kingdom
Posts: 1

yes...i'd thought about that (sidling upto the problem sideways and jumping on it) but to no avail...

It's as if everything is ok until i apply the TivoMad script.........then it all goes pear shaped....


R

POST #5 | Report this post to a moderator | IP: Logged

Registered: Jan 2002
Location: Somerset, England
Posts: 4390

Does it report the hard disk size correctly after TiVo madding (in Linux I mean, not in the TivO)?

POST #6 | Report this post to a moderator | IP: Logged

Registered: Aug 2001
Location: Harrow, Middlesex, United Kingdom
Posts: 1

as im restoring to a single larger A drive i didn't think that it reports a drive size unless you are adding a second drive.....

It does not currently report any drive sizes during the tivomad process....


R

POST #7 | Report this post to a moderator | IP: Logged

Registered: Apr 2002
Location: Lincolnshire UK
Posts: 79

I have just performed the very upgrade you are having problems with and all went fine (2.5.5 30GB + 15GB). The only things I may have done/had to do differently are:

A. Had to qunlock both of my original Tivo drives.

B. Tested the new 120GB drive (non expanded) including live and timed recording (few minutes of each) and then deleted the recordings.

C. Deleted the dead recording headers in now playing taken over on the backup, before I expanded the drive.

The FAQ mentions checking your new drive size (as reported by BIOS) after installing in TIVO and returning to your PC, and using qunlock if needed.

I didn’t have to unlock the new drive as the reported size stayed at 120GB after testing in TIVO. The size is also reported in the Linux boot text (shift + page up).

Hope the above is of use!

Roy…

POST #8 | Report this post to a moderator | IP: Logged