TiVo Community Forums Archives - Warning: MFS1.1, dd and modem!

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

Warning: MFS1.1, dd and modem!
(Click here to view the original thread with full colors/images)

Posted by: GavinP

I upgraded my parents TiVo last week and added a 120Gb drive to the existing 40Gb (UK Thomson model) using MFS1.1 as this seemed a safer option.

My 240Gb TiVo was done using MFS2.0 using 16Mb block sizes and this works fine with the understanding that a green screen would be terminal...

Anyhow, the "dd" across worked fine and the 40Gb was added as the second drive. The ">140Gb" question was answered with a "Y" to enable 120Mb swap.

The TiVo started up fine and seemed perfectly OK - however when initiating a call (test or daily), the TiVo would reboot.

Running a MFS Restore onto the drive sorted the problem and the recordings were OK afterwards.

One to watch out for...

Thanks

Gavin

Posted by: Robert S

The question about >140Gb is TiVoMad rather than MFS Tools 2.0

It's better to use MFS Tools 2.0 rather than dd and TiVoMad, mostly because, as you say, the larger block sizes result in a faster TiVo.

If you restore with

mfsrestore -s 127 -xpi /mnt/dos/tivo.bak /dev/hdb

if you want to save your recordings, do a pipe:

mfsbackup -Tao - /dev/hdc | mfsrestore -s 127 -xpi /mnt/dos/tivo.bak /dev/hdb

MFS Tool will restore with expanded swap (so a 240Gb TiVo would be safe) and fill the whole drive. If you list your new B drive after /dev/hdb, it'll even bless that in for you.

If you didn't expand swap on your 240Gb TiVo, see the MFS Tools 2.0 fixes thread for a 'rescue' maneuver that will allow your TiVo to recover if it gets stuck on a green screen.

Posted by: GavinP

Robert,

Thanks for the reply - I'm aware of the pro's and con's of MFS2.0 - I would rather the parent's TiVo be able to repair itself in the event of a problem hence why using MFS1.1.

I'm sure MFS2.0 will do a similar job but personally I have more confidence in MFS1.1 at present (in stability anyhow).

The "reboots if you try to use the modem" I haven't seen on here before hence why I was reporting it.

Thanks

Gavin

Posted by: Merle Corey

Gavin:

There are no more cons for MFST2 - we've got the ideosyncracies worked out. See the "Fixes for MFSTools 2.0 swap problems" thread for details.

The modem thing sounds (obviously) like something got munged the first time through - glad to hear redoing the restore fixed the problem, though.

MC