MFS Tools 2.0! An upgrade revolution!

[bkirk]

Just wanted to say thanks to Tiger. I upgraded my AT&T TiVo with no problems, went from 40 hour to 142 hour for only a $50 120GB HD. Great for us newbies. :up: :up: :up:

(oh yeah...and D* blows too). Drop D*, get cable and then you can use TivoToGo, HomeMedia, etc....it rocks. D* won't ever allow that.

[RabidLamb]

Originally posted by bkirk
(oh yeah...and D* blows too). Drop D*, get cable and then you can use TivoToGo, HomeMedia, etc....it rocks. D* won't ever allow that. [/B]

I'd agree were it not for dual tuners. That's the ONLY important feature. If I could get that w/ cable then I would. But untill I can get dual tuners in an SA TiVo, i'm sticking w/ my DirecTiVo, and suffering through not having ToGo and HMO.

[ThreeSoFar]

Well you can get it, you just need multiple SAs.

Not what you meant, I know. But it's what I do. Initially because we couldn't see the sats through trees in our old house, and now because of D* being essentially anti-TiVo.

[zeph]

I used MFS tools 2.0 to add a 160Maxtor HDD to my Series 2 SA Tivo. My Original Tivo is a Western Digital 80 hour. I have have reported 243hours on my Tivo. The upgrade went smooth, however now I am seeing breakup in my AV with playing back and when I hit the record. Any suggestions?

[Robert S]

That might be over heating.

But it probably means your new drive is faulty.

[JEJ]

This caught me by surprise and I suspect that it may be due to the fact that mount cannot determine the fileystem type of my FAT32 disk.

I took a 40GB disk and attached it to my W2K system and created a 20GB partition, which I then formatted in FAT32. Then, while booted off of the CDROM, I attempted

# mount /dev/hdc1 /mnt/c
mount: you must specify the file systemt type.

What is the best way to create a FAT32 disk so I can backup my Tivo disk?

Thank you,
Jerald

[ThreeSoFar]

Are you sure hdc1 is the right partition? Keep trying other numbers, hdc2, 3, 4...see if any of them work.

A "dmesg | grep hd" may show the valid partitions on that drive.

[CableNinja]

I just recieved my Tivo box from Tivo. I am not sure of the model but is has series 2 on the fron left. It is suppose to be the 40 hour model. I have downloaded the tools and am reading the the FAQs. What drive combination shoud I use? Replace the existing one or add a second unit? What brand and size will give me the best performance? Sounds like I need to do a backup first, should I hook it up and register first or after the backup? Sorry for being the dummy but I jsut got mine!

JJ

[ThreeSoFar]

Replace with a Samsung 160G. Newegg.com has great prices, no rebate hassle. That should be plenty of space. Read Hinsdale's HOWTO (http://www.tivocommunity.com/tivo-vb/showthread.php?s=&threadid=36974&highlight=howto). Carefully.

If your TiVo has a white panel on front that lights up, you can use the LBA48 boot CD to use all 160G of your drive.

[Raymond Day]

I have MFS tools 2.0 it works real good to back up and restore you TiVo and do hacks to it.

One thing would be good if it could mount a network samba type file system. I did this command but it did not work.

mkdir /mnt/windows
mount -t smbfs "//winserver/My Storage" /nt/windows

It gave a error. Could MFS tools 2.0 or maybe next one 2.1 do this type of thing? I guess it have to have a lot of network drives to work with a lot of network cards and some type of network file sharing in it.

Thank you for MFS Tools 2.0

-Raymond Day

[Robert S]

Mount is a Linux command. It's not part of MFS Tools.

The boot CD probably doesn't have smbfs installed.

MFS Tools will run under any version of Linux, so if you can find one with the SMB stuff - Knoppix would be worth trying - you can use that instead.

[bike2020]

Has anyone noticed how fast the menus come up when you upgrade the hard drive ? And with the TIVo To GO update the menus are even faster now.

[dtebbe]

Does MFStools 2.0 have support for drives over 137gb? Or does that take some other special version? I am getting ready to buy an R10, and want to know how big I can go on the hard drive (want to install a single big drive) and which version of MFStools I need to do the upgrade.

Your help will be appreciated!

DT

[ThreeSoFar]

It does as long as it is running in a kernel that recognizes it. Hinsdale's guide has a link to one that recognizes LBA48 drives. There may be a max of 300G though?

[KevinG]

I have 2 dsr6000 dtivos, both have an extra 80 gig drive that I added to the 40's via the old hinsdale how-to guide.

Yesterday night, one of the dtivios started rebooting itself. When it was done, it would work for a few minutes, then reboot again. I took the cover off, and that made it last a bit longer between reboots. So, I'm thinking bad disk.

I pulled both drives out and ran them through the maxtor tests, and they both came up as "fine". So, I went out and bought a 120 gig drive anyway.

I figured I would use MFSTools 2.0 to combine them onto the new 120 gig drive. It quickly informed me that they wouldn't fit. I checked the math, and it was right.

So, here's my thinking.
1) copy the 40 to the 120, but don't do anything to it...put it all back together and the system should be as before (no extra space, recordings intact, but no reboots).
2) If that is true, wait a while, and then expand it.
3) If that doesn't work out, my 80 gig was probably at fault... Copy that onto the 120 gig, and put the old 40 with the new 120 in and see if all is well.

Sound like a good plan?

Here's one other question. Is there any truth that cpu speed drastically affects the time it takes to do the dd from one drive to another? I'm currently doing it on a 333 Mhz old spare machine. If this is confirmed, I may very well move the whole process to my 3 Ghz machine.

Thanks.
-Kevin

[Bombsheal]

Has anyone noticed how fast the menus come up when you upgrade the hard drive ? And with the TIVo To GO update the menus are even faster now.

lol. nice sarcasm. I hope they can fix the 7 software so it doesn't take the 10 seconds or so for menus to load. it is seriously annoying.

[Lotharius]

OK, I got two 200Gig MAXTOR Diamondmax 10 hard drives. Using the Weaknees guide I used MFSTOOLS2 to move over all my shows to the new hard drive in my HDR31202 Phillips Series One 30hr Tivo. I reinstalled these in the Tivo and everything runs fine, but it says I have 94hrs best quality, and 344hrs Basic quality. From everything Ive read here, shouldn't I have over 400hrs basic quality? Where did I go wrong, and what do I have to do to fix it??? (please provide links)

[ThurstonX]

I'd agree were it not for dual tuners. That's the ONLY important feature. If I could get that w/ cable then I would. But untill I can get dual tuners in an SA TiVo, i'm sticking w/ my DirecTiVo, and suffering through not having ToGo and HMO.
It is possible to "upgrade" a DTiVo to 4.0x so you get HMO, etc. And it's all somewhere on this Web site ;-)

[alan]

I was upgrading my Series 1 Sony SAT-T60 last night using a CD image of mfstools 2.0 from the http://mfstools.sourceforge.net/ link and ran into the problem where the TiVo drives were complaining about the 1492/9214 byte-swap probem. My configuration was:

hda: DOS
hdb: new drive
hdc: single TiVo drive
hdd: cdrom drive with mfs boot cd image

I saw the reported byte-swap complaint about

hdb: Signature 1492, be16 Signature 9214
03:00: block 0 has signature 9214 rather then 1492
unknown partition table

hdc: Signature 1492, be16 Signature 9214
03:00: block 0 has signature 9214 rather then 1492
unknown partition tableI tried booting with the swap option, but got a kernel failure (NULL pointer or something).

Anyway, I couldn’t seem to get around this and so I got the floppy version from the link in hinsdale’s how-to and was able to boot, I didn’t even see the partition tables in the initial boot output, so I assumed that it was happy and I backed up the original TiVo drive to DOS, and restored from DOS to my new TiVo drive. I tested it out in the TiVo and things seemed to be okay. So, I reconfigured the drives (pulling the DOS drive and putting the new TiVo drives in Primary Master and Primary Slave for the new TiVo drive A and B respectively) and started to do the restore (saving recordings) via the specified command:

Mfsbackup -Tao - /dev/hdc | mfsrestore –s 127 –xzpi - /dev/hda /dev/hdbMy disk config looked like this:

hda: new TiVo disk A (80GB)
hdb: new TiVo disk B (80GB)
hdc: old TiVo Disk (40GB)

During the copy I got an error saying:

Unable to handle kernel paging request at virtual address …

The error can be seen here: screen image (http://home.xnet.com/~kae/error.jpg)

I only saw one of these errors, but the backup/restore continued and it seemed to not care that this paging request failed.

After the copy finished, I put the two new drives in the TiVo and it seemed to work fine. I moved around the menus and played several of the recordings in the Now Playing List and things seemed to be fine.

Should I be concerned about the kernel error or redo my drives?

I’m wondering if I should go back to the mfstools 2.0 cdrom and try booting with the vmlnodma option and list bswap on some of the drives like this (I don’t know if this is the right format):

Boot: vmlnodma hdb=bswap hdc=bswapI haven’t found the information for the vmlnodma option and if it even takes args like above. I did see this option on someone elses boot CDROM, but they only had one of the disks named. I’m not sure that’s supported on the mfstools 2.0 cdrom image. Anyone know?

Right now I’m just using the new drives, which brought my old TiVo up to 140 hours. I haven’t had a problem (Much thanks Guys for working on this software and instructions)

I just wasn’t sure what to do with the byte-swap problem on the drives. Is there another way around this?

Thanks!

[ineedcolor]

Jolly and Roger,

STEPS I TOOK TO UPGRADE

1. Copied MFS tools to CD. (bootable image)
2. Coped HDVR2 image 3.1b-1 to CD
3. Connected New Drive to Primary Slave (hdb).
4. Booted From CD Secondary Master (hdc).
5. After MFS booted and at "/#" prompt. I Took out MFS CD and inserted CD with image
6. At this point I perforemed the following (there was already a cdrom dir):

/# mount /dev/hdc /cdrom
/# mfsrestore -s 127 -xzpi /cdrom/<image>.mfs /dev/hdb
Starting Restore
Uncompressed backup size: 1449 megabytes
Restoring 1449 of 1449 (100.00%) (84.30% compression)
Cleaning up restore. Please wait a moment.
Restore Done!
Adding pair /dev/hdb14-/dev/hdb15
new estimated standalone size: 147 hours (107 more)
/#

7. Popped Drive into Hughes - HDVR2 and it powered on just fine.
Thanks for all the help everyone.

David

And thanks to David for posting these instructions, this is exactly how I needed to do my drive replacement and it worked perfectly for me this afternoon....

Cheers,

[RabidLamb]

It is possible to "upgrade" a DTiVo to 4.0x so you get HMO, etc. And it's all somewhere on this Web site ;-)

And it's now done and works great :) Thanks a whole lot to the brilliant people here and at the "Other Forums."

[MtEverest]

Doing a one drive upgrade using MfsTools 2.0, get to step 7 where you have to issue Mkdir and Mount command i get ' mount: you must specify the file system type


entered commands as such,

mkdir /mnt/dos

mount /dev/hda /mnt/dos


went back and did a search of thread and found the answer i needed, figured some one had run into it before just did not see it when i browsed through thread.

thanks to all that put up so much great info.


Update : Just finished moving backup to new hard drive, hooked back into Standalone unit to test, first gray screen comes up no prob, second sreen no prob and then i get green screen of death.(UGHHHH) Says to leave plugged up for next 3 hrs will it runs some tests, if after that time need to call an 800 number. Any ideas? Will be stranding by to hear.


Mt Everest

[philwatson]

I recently purchased a TiVo S2 40gb unit. I ran it for a few days and decided to upgrade it to a 160gb drive. Using MFS tools I noticed that the backup for the original drive was 31191mb (even though I had deleted all movies from the TiVo menu). Is it still wanting copy all of the video even though I deleted it? If so, how do I erase it so I a minimal backup image? Thanks.

[ThreeSoFar]

What exactly was the command you backed up with Phil?

Following is from Hinsdale's HOWTO (http://www.tivocommunity.com/tivo-vb/showthread.php?t=36974&highlight=hinsdale+howto). The /dev/hdX letters are yours to choose. Be careful.

For your backup, you want something from section 7). Probably:mfsbackup -f 9999 -6so /mnt/dos/tivo.bak /dev/hdc

That should be no more than 600M or so. Then you can use section 10), Upgrade Configuration #3 to dupe your entire drive, shows and all, to the new one:mfsbackup -Tao - /dev/hdc | mfsrestore -s 127 -xzpi - /dev/hda

[philwatson]

ThreeSoFar:

I used the following command since I was upgrading the original TiVo drive to the 160gb drive (I'm using the original as my backup):

mfsbackup -Tao - /dev/hdc | mfsrestore -s 127 -xzpi - /dev/hda

Should I have issued another command before the above in order to get the file size down to 600m as you mentioned? Thanks.

[ThreeSoFar]

This does not create any backup file on any filesystem, so you needn't worry about the file size. This essentially backs up one drive, the output from that is "piped" into the restore command, which writes it (en toto) to the new drive. The end result here is two working TiVo drives, same content, one bigger than the other.

In other words, boot the one that's in /dev/hda in your TiVo and it should work as-is.

[tivofun]

I am having an issue with mfsbackup or mfsrestore.

I have a SA TCD540040 (nightlight) ruining software 7.1a-02-2-540 and am replacing the factory drive with a Maxtor DiamondMax Plus 200GB drive using Hindsdale's guide (Feb 8th 2005) and mfstools 2.0 with LBA48.

Hda is fat32, hdb is new 200G drive, hdc is original tivo 40G, and hdd is cdrom.

I did the mkdir and mount (no errors)
mfsbackup -f 9999 -6so /mnt/dos/tivo.bak /dev/hdc (no errors)
mfsrestore -s 127 -bzpi /mnt/dos/tivo.bak /dev/hdb (no errors)
umount -f -a -r (no errors)
ctl-alt-del and power down.

I put the drive in the Tivo, got the welcome screen and it went blank after around 28 seconds and nothing else. Tried it again to make sure I did not typo.

Same thing. Tried the restore without the -s 127 and got the same thing.
One time when I was booting up mfstools I noticed that the original drive had a bunch of partitions but the new hdb drive just showed "hdb: unknown partition type"

My final attempt was to do a:
"mfsbackup -Tao - /dev/hdc | mfsrestore -s 127 -xzpi - /dev/hdb"
(I did not move the new drive from hdb to hda)

This worked. I watched a few seconds of a show that I had recorded.

My issue is that I would like a good backup that I can burn to a CD and I don't know if it was the backup or restore that went wrong.

I assume that I did something wrong. Just not sure what.

Thanks.

[ThreeSoFar]

How big is the .bak file?

Any chance it was a slave/master thing?

What do you mean by "(I did not move the new drive from hdb to hda)"? Only part I didn't understand.

[tivofun]

The .bak file is somewhat larger than 500Meg. I am not in front if that computer right now.

Possible on the slave/master question, but I am fairly sure it wasn't.

For the "I didn't move ...", in Hinsdale's guide, section 7&8, for the backup and restore it recommends the fat32 be hda, the new drive be hdb, and the orig tivo be hdc. For section 10, option 3, it recommends the new large drive be hda, and the original tivo drive be hdc.
I did not want to disconnect the fat32 drive so I left the new one at hdb and adjusted the command. (I had to move the jumper every time I tested it back to master, and slave when in my PC)

Is there any way to test the backup to see if it is good (other than a mfsrestore)?

Thanks.

[ThreeSoFar]

The Hinsdale hdX entries aren't recommendations. He just picked some and went with those. Just adjust what you type to where the drives end up in your PC.

I don't know of a way to test a backup image other than restore and fire it up.

[sandi94533]

I recently tried to use MFS 2.0 and forgot to unplug my windows and booted to windows disk with the tivo original plugged into secondary master needless to say windows wrote some junk to my original tivo disk rendering it useless. Is there some kind of software that will clean the original tivo up?

[ksv666]

This may be an odd case, but I could really use the help:

Original: 30hour TiVo (312)
Upgraded to a single 160GB drive and all is working.

However, now I need to change the configuration to 2 - 120GB drives. I need to preserve all recordings and it looks like there is around 140GB of content.

I restored my original TiVo image to the drives and grew them with the CD, so now I have a dual-drive setup (no content). I now want to take all the video content from the 160GB drive and move it to the new drives. None of the scenerios work when I try to restore (or copy) the content from the existing 160GB drive to the now expanded 2 - 120GB drives.

Can anyone offer a suggestion? I am stumped.

Thanks,

-Kirk

[trainedmonkey]

I'm a little confused about the following scenario and I apologize up front if this question has been asked and answered a thousand times.

I have 2 DTIVOs one Hughes and one Philips 704.

Both had 40 gig drives originally. Using MFSTools I upgraded. Lifecycle of boxes were:

Hughes
3.1.1c on 40gig to 3.1.1c on 2 120gig drives to 3.1.1d to 3.1.1e
Philips
3.1.1c on 40gig to 3.1.1e to 2 160gig drives to 6.2

Now that 6.2 is out I want to upgrade to 2 300gig drives on the Philips

Can I do this and still save my recordings?

I've seen some posts that talk about upgrading multiple times without losing recordings and others talking about it and saying it can't be done.

Am I confusing upgrading drives with expanding existing drives? (my understanding is that it is possible to expand the 160s from their original limit of 137g to their full capcity of 160g. I think this can only be done on drive B but not sure about that).

Thanks in advance for your feedback.

[bnm81002]

Tiger,
when will MFS Tools 3.0 be available? any links? thanks

[earnric]

The .bak file is somewhat larger than 500Meg. I am not in front if that computer right now.

Possible on the slave/master question, but I am fairly sure it wasn't.

For the "I didn't move ...", in Hinsdale's guide, section 7&8, for the backup and restore it recommends the fat32 be hda, the new drive be hdb, and the orig tivo be hdc. For section 10, option 3, it recommends the new large drive be hda, and the original tivo drive be hdc.
I did not want to disconnect the fat32 drive so I left the new one at hdb and adjusted the command. (I had to move the jumper every time I tested it back to master, and slave when in my PC)

Is there any way to test the backup to see if it is good (other than a mfsrestore)?

Thanks.


I also tried to add a small drive (30 GB) to my 40 gb series 1 Philips (6000)... I used MFSTools 2.0 to "mfsadd", but i had my Tivo A drive jumpered to slave... as well as the "new" drive.

After reinstalling in the Tivo, it wouldn't boot. I had to mfsrestore the image on the A drive.

So, 1 - do you have to jumper the orig tivo A drive as a "Master"... and 2 - can you have a smaller B drive than A drive?

The old "B" drive was used on a windows system... I didn't format it -- I thought mfs would handle that... Maybe that's my problem?

Thanks

[earnric]

Ok,

I've tried to use MFSTools and Hinsdale to add a second 30GB drive to my Philips 6000 series 1 twice now... I can't get past the boot screen.

I put the old A drive as secondary master, the new (actually an old drive from my linux box) as primary slave... Backup'd the A drive and then ran

mfsadd -x /dev/hdc /dev/hdb

No go -- I continually boot and re-boot when I plug the tivo in.

Do I need to reformat the new 30gb drive and try again?

Rick

[earnric]

I tried again... using

mfsrestore -s 127 -xzpi /mnt/linux/home/tivo.bak /dev/hdc /dev/hdb

to restore my good backup image across both drives... My philips still continually goes between the two boot screens:

Powering Up

&

Almost there...

If I restore to the orig 40gb drive, the tivo boots just fine.

What can be going wrong??

Signed -- starting to drive me nuts!

[bnm81002]

still no word when MFS Tools 3.0 will be available yet? :(

[hantousha]

I heard of the LBA48 support e.t.c.. I need to know what utility I need to use to upgrade the 40GB to 400GB. I tried MFSTOOLs2.0 and it only give me a total of 147hours? What I am doing wrong. I tried mfsadd -x /dev/hdb , mfsadd -r 4 /dev/hdb e.t.c.. Any hints would be appreciated. or I am I stuck at 147 Hours? I have a TIVO 240040A. Currently running Software version 7.1. (TivoToGo).

[ThreeSoFar]

same command, just boot a Linux that is new enough to recognize the larger drives. There's a LBA48 bootable CD image on Hinsdale's HOWTO page. Hinsdale's post here used to be a sticky but isn't anymore since he isn't a paid sponsor of this site.

One way would be to boot the CD you have, copy the mfsbackup and mfsrestore binaries (and mfsinfo is useful) onto your DOS/vfat/windows drive. Then boot some other new cd (Knoppix works great), mount the DOS drive and run it from there (or copy it to /bin, which is a RAMdrive at that point.

(I know, mfsrestore and mfsbackup and mfsinfo are all links to mfstools. Copy it just once and make links after booting Knoppix if you know how to do that.)

[Gojira69]

I heard of the LBA48 support e.t.c.. I need to know what utility I need to use to upgrade the 40GB to 400GB. I tried MFSTOOLs2.0 and it only give me a total of 147hours? What I am doing wrong. I tried mfsadd -x /dev/hdb , mfsadd -r 4 /dev/hdb e.t.c.. Any hints would be appreciated. or I am I stuck at 147 Hours? I have a TIVO 240040A. Currently running Software version 7.1. (TivoToGo).
Hantousha and I are both using the mfstools 2.0 disk. I get the same result too, 147 hours. Using mfsadd returns message "nothing to add"

Addenda 6/29: I have solved my problem. The boot media I was using did NOT include LBA48 support. I had wrongly assumed ALL "2.0" versions of MFSTools had LBA48 support.

Addenda 6/30: I've got telnet bash!!! How weird the seemingly easiest part of this process was the hardest and the seemingly hardest, the easiest!

[emarsh]

Will moving from 2.0 to 2.0.1 get me around the problems I'm experiencing? They are described in the thread http://www.tivocommunity.com/tivo-vb/showthread.php?t=246548

[mr_fusion_512]

I asked this question earlier on the underground forum:

*snip*
I've got a question... I have what was originally a 40 gb series 2 (240-0000-xxxx-xxxx, model # TCD24004A) and I upgraded it to dual 160's a couple years ago. At the time, the various tools around could only see 128 GB of the 160's but oh well...

Now, I hear that the software used on these series 2 40 gb's can go up to 250 GB per drive?

If so, which software do you recommend and will it automatically handle the larger drives, etc.?

Also, from what I heard, the software on the 140 GB's and higher can take 400 gb drives, but the 40's can only go up to 250GB per drive?
*end snip*

and had an answer that 400 GB drives were supported since I was running 7.1 and I used an LBA48 boot disk, but I was told that I couldn't upgrade the A, just the B drive, if I wanted to preserve recordings...

Well, after poking around the two 160's, I do notice that there are 16 partitions (and therefore no more room) to Re-Expand... so if I follow the suggestion for a single B drive upgrade, it should just be a matter of DD'ing my B to the new B... and then presuming my A is on hda and my New B is hdc, then I just need to remarry the drives with: mfsadd –x /dev/hda /dev/hdc

Right?

Anyway, while flipping through the different posts on MFS tools 2.0, I'm under the impression that with that command:

mfsbackup -Tao - /dev/hda /dev/hdb | mfsrestore -s 127 -xzpi - /dev/hdc /dev/hdd

I should theoretically be able to put my two 160's on hda/hdb and my new 200's on hdc/hdd (I would actually gain 160 GB because I'm only using 128 GB from the first two 160's) but I run across an error...

My first problem was (and is) that I couldn't find a boot floppy that supports >128 GB... (was using http://www.upgrade-instructions.com/downloads/mfs2floppy.zip)
so I worked around it with the weaknees cd and a spare pci ide controller which started adding in hdg and hdh and was a general pain... but as the boot disk never saw any partitions on the new blank drives, it errored out and although it got the "read" part of the command down, it would never start the "write" part of it...

So, can anyone tell me what I'm doing wrong or should I just abandon the whole thing and go for switching out the B drive for a 300?

Thanks!

[blarg]

hey kids, I've been struggling with this all day and can't seem to get it to work...maybe someone here knows what I'm doing wrong.

about a 2 years ago I bought a 40 hour tivo (model 240). I immediately put in a 160 gig drive and upgraded it. At the time, it was only supposed to see 128 MBs of the 160, but the drive was so cheap, I didn't care. I got 155 hours.

now, I have os ver. 7.1 and would like to "re-expand" the HD. From what I've read on these forums I should expect about 170 hours, but after copying the original backup to the drive and re-expanding, I STILL only get 155 hours. In a way this makes sense because I went back to the original 4.1 kernel, but MFStools2 should see the extra space shouldn't it?

I've got the backup problem sorted out now so I backed up my ver 7.1 image...MFStools said it was originally a 40 gig image, and made the backup a 40 hour image). Still, when I try to expand the HD, I still only get the same capacity I had before.

Do I have to somehow remove the existing partitons from the 160 gig drive before I re-expand it? What am I missing here?

[winders]

blarg,

You have to boot with an LBA48 kernel when using MFSTools. You also need to have an LBA48 kernel on the TiVo drive too. Does your MFSTools boot CD or floppy have an LBA48 kernel?

Scott

[mr_fusion_512]

If you're trying to preserve your recordings, then according to what I've heard, the first upgrade brought your A drive to it's partition limit of 16 (starts with 14, upgrades add 2), thereby not allowing any more re-upgrades to that drive. (Someone please correct me if I'm wrong). So what I've been told is that to get the full use of the drive, I've got to start with the original 40 gb image (by whatever means) and use an LBA 48 boot cd and that should give you that 25% boost in space. The only way to retain your recordings in this case that I know of is to transfer your shows onto another tivo on the network and then transfer them back...

Anyways You can find the Weaknees LBA 48 Cd here:
http://www.weaknees.com/weaknees_lba_boot_cd.iso

I had a slightly similar problem (with 2*160's recognized as 2*128's) and I'm awaiting a response from someone on why my B drive upgrade won't work (based on the theory that it can be upgraded a half dozen times unlike the A drive).

-Jason

[blarg]

I couldn't care less about my recorded shows. Everything I really wanted to keep got transfered to my PC using ToGo already. I just used my original 40 GB image (with ver 4.0) that the tivo originally came with, but when I expanded, I STILL only got 155 hours. Do I have to somehow WIPE the drive and delete the partitons on it before I can make NEW partitions with more space?

right now, I'm re-downloading all my software updates. from what I can see, I can use MFStools2 to backup my 160 gig drive to a 40 gig image so I don't have to go all the way back to OS 4.0 again, but I STILL can't get it to use the FULL 160 gig drive.

I'm using the MFStools CD that I got by following the link in the begining of this thread. its MFStools2.iso I assumed it had the LBA48 kernel

I also have PVRLBA48-4.01.iso I didn't try it because I thought they were basically the same.

guess I'll try that weaknees CD after I get my 7.1 software back.

[mr_fusion_512]

You may try doing what I did, which is to stick the 40 back in there and run as many "calls" as necessary to get the software updated to 7.x. And THEN do the expansion. I did this successfully with a 540 series 40 hour and will try one tonight with an older 240 series 40 hour model and I'll let you know...

And while you're waiting, you can find some software to wipe your drive completely. If you have a maxtor, I'd recommend their diag disk and choose the quick low-level format option which takes out partitions, mbr, etc. only or just load it into a windows pc and fdisk it (win9x) or use Disk Management in Computer Management (start, run "compmgmt.msc") to wipe it "clean" (or at least unrecognizable as far as Linux/Tivo is concerned)

-Jason

[blarg]

You may try doing what I did, which is to stick the 40 back in there and run as many "calls" as necessary to get the software updated to 7.x. And THEN do the expansion. I did this successfully with a 540 series 40 hour and will try one tonight with an older 240 series 40 hour model and I'll let you know...

And while you're waiting, you can find some software to wipe your drive completely. If you have a maxtor, I'd recommend their diag disk and choose the quick low-level format option which takes out partitions, mbr, etc. only or just load it into a windows pc and fdisk it (win9x) or use Disk Management in Computer Management (start, run "compmgmt.msc") to wipe it "clean" (or at least unrecognizable as far as Linux/Tivo is concerned)

-Jason

well apparently when you use MFSbackup it de-expands your diskimage back to its original size...so I updated my tivo to 7.1b, THEN did a backup, and MFSbackup said it was making a 39-hour image from a 147-hour upgrade. Now I just put in the HD with my windows XP disc and told it to do a complete (not the fast option) NTFS format. Then I'll try to use the LBA48 disc from weaknees.com and see what happens. wish me luck. at least now I know you can backup an upgraded drive back to its original size, and you don't have to lose your preferences, network settings, list of shows that have already been recorded etc....good to know for NEXT time :rolleyes:

[blarg]

ok the stuff I did in the post above WORKED!! the utility reported 175 hours.

so basically

1) use the weaknees LBA48 CD
2) backup your 7.1b hd
3) if the drive was already used in a Tivo, boot up some OS installer and do a LONG format of the HD...I didn't actually finish mine. I just let it go until about 20% and reset the computer.
4) restore your 7.1b image
5) expand the drive.

note -

I didn't care about my recordings...you DO lose them in this method...but you also gain about 30 hours of recording time.

[mr_fusion_512]

btw, my upgrade was successful... Using the Weaknees LBA 48 boot disk mentioned above, I managed to get a 17% increase (using the full 160 rather than only 137). Now my newly upgraded tivo has 370 (from 2-160's) and the old one (same drives) has only 317. Both of these are the first Series 2 models (starts with 240-xxxx-xxxx-xxxx) coming stock with 40 gb drives.

Although MFS tools should not require a DD, I did it out of habit before I remembered that I (theorectically) didn't have to...

None the less, I took the stock drive which sat in the Tivo long enough to update itself to 7.1, then DD'd it to my new A drive (incidentally, both the A and B drives I used were in the Tivo before so I ran the Seagate Disk setup cd and did a "quick" "write 0's" to both drives).

After the DD, I ran the following command (with my new DD'd A drive as primary master and my second blank drive as primary slave and 40 gb stock drive upgraded to 7.1 as secondary master):

mfsbackup -f 9999 -so - /dev/hdc | mfsrestore -s 127 -xzpi - /dev/hda /dev/hdb

and this kept all the recordings and settings from that 40 gb...

Hope this helps :)
-Jason *Smile*

[tivo_newbee]

I admit that I'm a novice when it comes to UNIX/Linux, however the commands used for Mfs Tools 2.0 look fairly basic to me.

Here's what I can do: mkdir /mnt/dos

Here's what I am unable to do: mount /dev/hda1 /mnt/dos
everytime I enter this command, I receive an error that reads, " Mount: you must specify the filesystem type" Filesystem type? What???

Any suggestions?

[blarg]

are you sure you only have one partition on that drive, that its a fat32 partition, and that you have it attatched to the right IDE channel and Master/Slave position?

[HomeUser]

I am assuming that the partition you are trying to mount is Fatxx, Are you sure that the hard drive is primary master?

Or you may have more than one partition on the hard drive. check the partitions with "cat /proc/partitions" or just try mount /dev/hda2 /mnt/dos

[tivo_newbee]

I am not 100% positive that I only have one partition on the drive nor am I 100% positive that it is a FAT32 partition. I am 100% positive that I do have it attached to the primary IDE and the jumper on the drive is set to master. (I am borrowing a spare drive from a friend as the pc box I am using for the TiVo upgrade is brand new with the Win XP OS, etc. Therefore I'm using a drive other than what came with the box as my primary C drive.) Now I'm thinking that the spare drive is not formatted as FAT32 with only 1 partition....

[blarg]

I'm not sure that MFSTools will mount NTFS.

the Weakneees CD worked better for me. I couldn't get LBA to work with MFSTools, but the weaknees CD worked like a charm.

[tivo_newbee]

Are you sure that the hard drive is primary master? YES!! Have checked that numerous times.

Or you may have more than one partition on the hard drive. check the partitions with "cat /proc/partitions" or just try mount /dev/hda2 /mnt/dos

The result from "cat /proc/partitions" is as follows:
major minor #blocks name
33 0 4226040 hde (windows "C" drive)
33 1 4225063 hde1 (windows "C" drive)
33 64 117220824 hdef (new Western Digital 120GB drive for TiVo upgrade)


The result from "mount /dev/hde2 /mnt/dos" is as follows:

/dev/hde2: Success
mount: you must specify the filesystem type

So I'm suspicious that the drive I'm trying to mount, which is borrowed from a friend and is "supposed" to be FAT32 formatted with just 1 partition, ain't so.... therefore off I search for a utility to format that drive as FAT32 with 1 sole partition.....any suggestions on freeware???

[tivo_newbee]

Blarg - thanks for responding again.

I was under the impression that the "borrowed" drive I am failing to mount is not NTFS. Here's my dilemma. I have a brand new pc box which I am using to perform the TiVo hack/drive upgrade. This new pc has absolutely no floppy drive, however does have a fully functional CD/DVD ROM drive that also burns CDs. What I'm gathering is that I'll need to create a bootable CD ROM (ISO image) that has an OS that will allow me to format that "borrowed" drive as FAT32 and with just 1 partition. Any suggestions on how to make this work with what I have? I've successfully created bootable CD ROMs using Nero....

[azitnay]

You can reformat the "borrowed" drive from within Windows XP... I believe you can right click on the drive in My Computer and click Format, or use the format utility from the command prompt.

BTW, your friend knows that you're going to format this drive, thereby losing any data that might be on it, right?

Drew

[sholleran]

I love the guide, want to contribute to its improvement.

It appears step 4 has a redundant section titled
Boot the PC from the Linux media that you marked "Weaknees CD"

Verify Drive Sizes

which is followed by

Boot the PC from the Linux media

Verify Drive Sizes

Also, there are 2 important warnings on the page. Don't dislodge the white faceplate ribbon, and don't boot to XP\2000 with TIVO drive installed. Could Weaknees please box that with a yellow background or something so morons like me notice that we may be about to do a bad thing?

[tivo_newbee]

Drew,
Thanks for responding. I successfully reformatted the borrowed drive as FAT32 using my win XP box and then was able to perform the TiVo hack with 100% success. Also, my friend had formatted the drive before letting me borrow it so there was no concern of losing any data. I just have to believe that the drive wasn't formatted at all as my win XP box noticed the drive but prompted me to format it when I tried to access it.

Thanks again for your comments and suggestions.

Sincerely,

Ryan

[pgorbas]

I have asked this question in other threads, but my advisors are not sure what I should do - it really boils down to the inner workings if the mfsbackup command.

Here is the story.

Two years ago i started with a stock dTiVo with a 40gb drive. I added a second 120 gb drive - great I now have 141 hours recording time.

Amazingly I have been running out of disk space a lot lately, and I see advertised some great deals on 300gb drives.

I will explain what I think I should do in a moment, but so you are thinking along the right lines I will post upfront where the tricky part of the process could be. I am wanting to go from this setup (40gb + 120gb) to this setup ( the SAME 120gb + new 300gb). As you see the tricky part is that the same hard drive is BOTH a source and a target.

Now here was my full blown plan.
I will have to use a boot floppy instead of a boot CD since I can only have 4 IDE drives. My IDE drives will get set like so in my PC:
Primary master ........ = fat32 PC drive (hdW set to hda)
Primary slave ......... = Original TiVo drive (hdX set to hdb)
2ndary master ......... = Second Original TiVo drive (hdY set to hdc)
...this drive is also . = Target (New) TiVo drive (hdZ is ALSO set to hdc)
Secondary slave ....... = Second Target (New) TiVo drive (hdzz set to hdd)

I am somewhat nervous that I will be using the SAME ide slot and hard drive as both the Second Original TiVo drive=hdY AND the Target (New) TiVo drive=hdZ

This would my mount command:
mount /dev/hda /mnt

My comand for the safty net backup would be:
mfsbackup -f 9999 -1so /mnt/backup.bak /dev/hdb /dev/hdc

and my final mfsbackup command to complete the swap is like this:
mfsbackup -Tao - /dev/hdb /dev/hdc | mfsrestore -s 127 -r 4 -xzpi - /dev/hdc /dev/hdd

Does this look right? In order for it to work msfbackup must be smart enough to buffer the data from the 120gb hard drive so that the orginal data is not over written before it is read. In essence it would be shoving the data from the old 40gb drive into the front of the 120gb drive , then allowing the excess to go onto the new 300gb hard drive.

If someone is sure this will not work, or if it sounds riskky would this alternative plan work:

Make a backup of both my original hard drives ( my 40 gb and 120 gb ) to my PC's hard drive like so:
mfsbackup -f 9999 -1so /mnt/backup.bak /dev/hdb /dev/hdc
Restore this image to both target drives (my 120 gb and the new 300 gb) IN A SINGLE PASS:
mfsrestore -s 127 -r 4 -zxpi /mnt/backup.bak /dev/hdc /dev/hdd.
I have the notion that keeping a smaller HD as the primary would give me a slight performance increase - that is if the index is kept there.)

Or would I need a even more involved procedure like this:

Make a backup of both my original hard drives ( my 40 gb and 120 gb ) to my PC's hard drive as above.
Restore the backup image to a single hard drive ( the new 300 gb hd since the 120 gb would be too small):
mfsrestore -s 127 -r 4 -zxpi /mnt/backup.bak /dev/hdd
Follow the standard instructions for adding a second hard drive to a single hard drive tivo. Would I need to re-format the 120gb drive or something ?

[blarg]

I'm guessing that you're doing this because you want to keep your recordings?

how about using ToGo to dump all your recordings you a PC, performing the upgrade and then you can move them back to the tivo using the latest Tivo desktop or Galleon and tivo 7.2?

I'm also guessing that you don't have access to another HD for temp image?

[pgorbas]

I'm guessing that you're doing this because you want to keep your recordings?

how about using ToGo to dump all your recordings you a PC, performing the upgrade and then you can move them back to the tivo using the latest Tivo desktop or Galleon and tivo 7.2?

I'm also guessing that you don't have access to another HD for temp image?
Yes - you are correct - I do want to retain my recordings. Also my DSR704 is a direct tv tivo - a DTiVo. It is my understanding that the most recent software for DTiVo's is 6.2. I also think the "ToGo" and "Galleon" utilities are also only regular TiVo utilities - I have never heard about them before. :)

[azitnay]

Yes, Galleon/ToGo is standalone-only at the current time.

There are "other" ways of getting video off a TiVo, but we can't discuss them here.

Drew

[davera98]

Thanks to all who have contributed knowledge and tips.

I tried an older version of the Hinsdale instruction on my series 2 Tivo (14000 series) which has os 7.5. the upgrade kept failing on a step that mentioned edit params (??). so i aborted my upgrade efforts for the interim. I have since downloaded newer instructions and files off the weaknees site. i will check if there is a newer Hinsdale set.

The issue i have right now is after the repeated failings, somehow my boot disk on my pc got set to boot to the tivo boot (Linux). The tivo boot cd is not in the cd drive. the only way i can boot to windows is if i force a boot menu and then i choose hard drive c instead of normal.

any ideas?

ps. i truly hope that this post is to the right thread. apologies if it is wrong

[HomeUser]

Floppy?

[blarg]

1) pretty sure there's no OS 7.5 for Tivo...the LATEST version is 7.2...and older models don't get it.

2) your linux disk somehow overwrote your boot sector.

if you're running windows 2000/XP boot to the windows CD, exit to the recovery console, and type "FIXMBR" and "FIXBOOT" (two different commands). That should repair the boot sector and your boot menu.

also, the older howtos have some omissions in the intructions that do things like tell you to use "HDA" for HD designations rather than "HDA1" which would cause the process to fail.

check out weaknees.com. they ask you a few questions and link you to a CD image based on your setup. it worked like a charm for me. I had some problems with the older howtos as well.

[blarg]

Yes - you are correct - I do want to retain my recordings. Also my DSR704 is a direct tv tivo - a DTiVo. It is my understanding that the most recent software for DTiVo's is 6.2. I also think the "ToGo" and "Galleon" utilities are also only regular TiVo utilities - I have never heard about them before. :)

I should really learn to pay more attention. :D

[bmatson]

I have read many times that I should be very careful not to boot a Tivo drive into windows. What about using a former windows drive as a new Tivo drive (i.e. as a target of an mfsrestore, to become a new Tivo A drive).

I have a 300 Gb Seagate drive that has a single NTFS partition on (bootable XP) that I want to install in my series 1 DTivo (sat t-60). I want to use my backup (thus no recordings), booting off an LBA48 CD, and restore, etc...

Is the edict against booting into windows simply that it will hose the Tivo formatting, and require another mfsrestore to be done? Or does windows do something to the MBR or partition table that MFSTools cannot undo?

Thanks.

[blarg]

I have read many times that I should be very careful not to boot a Tivo drive into windows. What about using a former windows drive as a new Tivo drive (i.e. as a target of an mfsrestore, to become a new Tivo A drive).

I have a 300 Gb Seagate drive that has a single NTFS partition on (bootable XP) that I want to install in my series 1 DTivo (sat t-60). I want to use my backup (thus no recordings), booting off an LBA48 CD, and restore, etc...

Is the edict against booting into windows simply that it will hose the Tivo formatting, and require another mfsrestore to be done? Or does windows do something to the MBR or partition table that MFSTools cannot undo?

Thanks.

you are corect. Its the OS that screws it up, not the actual drive. If you use an NTFS-formatted drive as your "target" drive MFSTools will simply overwrite the formatting.

[bmatson]

you are corect. Its the OS that screws it up, not the actual drive. If you use an NTFS-formatted drive as your "target" drive MFSTools will simply overwrite the formatting.

Thank you for easing my mind. I remember hearing that you could literally trash a hard drive permanently by using "qunlock" incorrectly.

[blarg]

Thank you for easing my mind. I remember hearing that you could literally trash a hard drive permanently by using "qunlock" incorrectly. I was afraid this might be similar, or at least make a drive permanently into a "windows" drive (Bill's fondest dream). Hard drive technology gets more mysterious every day - its hard to cull the myth from the fact. Thanks.


its just that XP tags the boot sector somehow that interferes with tivo. it doesn't seem to cause problems for other OS's...just tivo.

[bmatson]

I've just upgraded without saving my programs (all I wanted was the seasons passes). The programs are gone, but the "now playing" list wasn't deleted along with the programs they refer to. I don't want to delete each program listing separately (over 300 of them) unless I have to.

This is how I "upgraded" (from 2 x 200 Gb drives - lba48, to a single 300 Gb drive - also lba48) (all work done with PTV-LBA48 boot CD with MFSTools 2.0):

mfsbackup -6so ...
mfsrestore -s 300 -xzpi ....
copykern (Said "tpip: Unknown boot block signature: 0x0" then "Kernel Updated")

Is this behavior normal (a restore from "quick" backup leaving the "now playing list" intact, referring to non-existant programs)?

Is there a better way to clean this up while still keeping my seasons passes (over 100 of them)? "Clear Program Data and To-Do list" apparently doesn't clear out recorded programs, and it MAY delete my seasons pass. If someone can assure me it is not SUPPOSED to kill my seasons passes, I might give it a try. I presume that "clear and delete everything" WILL kill my seasons passes.

Is there a better way? If there is some advantage to doing the "Clear and Delete everything" (like defragging and/or cleaning up crap on the drive?), than maybe I will just redo 107 seasons passes. Suggestions and/or comments? Thanks.

[ThreeSoFar]

I've just upgraded without saving my programs (all I wanted was the seasons passes). The programs are gone, but the "now playing" list wasn't deleted along with the programs they refer to. I don't want to delete each program listing separately (over 300 of them) unless I have to.

This is how I "upgraded" (from 2 x 200 Gb drives - lba48, to a single 300 Gb drive - also lba48) (all work done with PTV-LBA48 boot CD with MFSTools 2.0):

mfsbackup -6so ...
mfsrestore -s 300 -xzpi ....
copykern (Said "tpip: Unknown boot block signature: 0x0" then "Kernel Updated")

Is this behavior normal (a restore from "quick" backup leaving the "now playing list" intact, referring to non-existant programs)?

Is there a better way to clean this up while still keeping my seasons passes (over 100 of them)? "Clear Program Data and To-Do list" apparently doesn't clear out recorded programs, and it MAY delete my seasons pass. If someone can assure me it is not SUPPOSED to kill my seasons passes, I might give it a try. I presume that "clear and delete everything" WILL kill my seasons passes.

Is there a better way? If there is some advantage to doing the "Clear and Delete everything" (like defragging and/or cleaning up crap on the drive?), than maybe I will just redo 107 seasons passes. Suggestions and/or comments? Thanks.
It is normal. Don't know another way to clean them up than delete the (broken) entries after the restore. No advantage I know of to CADE. Takes forever to run, too.

[meyerweb]

Hi all:

First off, I admit to NOT reading all 20 pages of this thread. I probably will, at some point, but I have another question first:

I've got an early series 2, model 24004A. Software version 7.2 something. Is this unit still limited to 137 GB drives, or can it now support larger drives? I've got a 250 GB drive, but if the Tivo will only recognize about half of it I'm not going to use it here.

Thanks for the help.

[ThreeSoFar]

Hi all:

First off, I admit to NOT reading all 20 pages of this thread. I probably will, at some point, but I have another question first:

I've got an early series 2, model 24004A. Software version 7.2 something. Is this unit still limited to 137 GB drives, or can it now support larger drives? I've got a 250 GB drive, but if the Tivo will only recognize about half of it I'm not going to use it here.

Thanks for the help.
As of 7.x, the 137G limitation is gone. If you do the upgrade yourself, just be sure to use a LBA48 capable boot CD (or floppy).

I use the Hinsdale HOWTO myself:

http://www.newreleasesvideo.com/


FYI, my last upgrade was to a Samsung 200G drive ( I highly recommend Samsung. ), and it made it a 224 hour unit.

[meyerweb]

Thanks. I'm printing that how-to right now.

[azitnay]

The programs are gone, but the "now playing" list wasn't deleted along with the programs they refer to. I don't want to delete each program listing separately (over 300 of them) unless I have to.

As TSF said, no great way... But if you turn off folders, and get yourself into a good CLEAR - SELECT rhythm, you can probably finish off all 300 in 5 minutes or so (albeit with slightly cramped fingers).

Drew

[anilgupte]

I got MFS_FTP and WinRar and opened the former and all that. Question is, how do I get it on my TiVo. I know very little Linux, and when the instructions say "requires a working copy of tar in your path" I have no idea what to do. How do I get the MFS_FTP on to the TiVo at all?

I have upgraded my TiVo to a larger capacity drive by following Hinsdale's instructions, so I can be a trained monkey, but that's about it.

Thanx for any help.

AG

[Capricorn]

My question is at the end if you want to skip the details. Thanks to everyone for the great tools and pointers!

I purchased Instant Cake in February and very happily used it to create a 250GB drive for my HUMAX DVD-Burning DRT800 (Hats off to PTVUpgrade). I kept the original disk. :)

In August my HUMAX was updated by Tivo to 7.2 and I started to have frequent "Internal Errors" burn errors :( and it was suggested that those errors were caused by 7.2's greater need for swap space. Another suggested cause was that my disk might be going. So I decided to move to a new disk and to allocate more swap space on it.

Yesterday I used Tiger's MFS 2.0 to try to a backup and restore to a 400GB disk starting with the following command (hdb is the 250GB w/ recordings and hda is the blank new 400GB):

A) mfsbackup -Tao - /dev/hdb | mfsrestore -s 127 -r 4 -xzpi - /dev/hda

and got a "target too small" error so I dropped the "x" option on the restore:

B) mfsbackup -Tao - /dev/hdb | mfsrestore -s 127 -r 4 -zpi - /dev/hda

and that worked (took about 7 hours).

Reading more on this forum today I realized I might be headed for trouble in the future (like the GSOD) if I didn't allow for even more swap space, so I did another backup and restore:

C) mfsbackup -Tao - /dev/hdb | mfsrestore -s 250 -r 4 -zpi - /dev/hda

and that worked too (another 7 hours).

My question is: Do I now need to use tpip to fix my 250MB of swap space, like this:

D) tpip --swapped -s /dev/hda

from the PTVupgrade CD (LBA48 CD v4.0) or am I OK because I was upgrading with a 7.2 system? Or have I created other problems for myself with the procedures above?

Sorry to be so clueless, I've done a lot of reading on this forum but I'm not confident about my understanding.


UPDATE: I think my TPIP question was answered by this reply from azitnay (http://www.tivocommunity.com/tivo-vb/showthread.php?p=3407375&&#post3407375) in another thread, so I'm proceeding with the above TPIP command.

[ThreeSoFar]

I had thought -s250, or any number not 127, would fail. Is this saying that you can do -s250 as long as you then follow up with the tpip command?

I've had my Humax DVD DRT800 freeze up a couple times lately. I upgraded it long ago with -s127, and it upgraded to 7.2 recently.

My question is at the end if you want to skip the details. Thanks to everyone for the great tools and pointers!

I purchased Instant Cake in February and very happily used it to create a 250GB drive for my HUMAX DVD-Burning DRT800 (Hats off to PTVUpgrade). I kept the original disk. :)

In August my HUMAX was updated by Tivo to 7.2 and I started to have frequent "Internal Errors" burn errors :( and it was suggested that those errors were caused by 7.2's greater need for swap space. Another suggested cause was that my disk might be going. So I decided to move to a new disk and to allocate more swap space on it.

Yesterday I used Tiger's MFS 2.0 to try to a backup and restore to a 400GB disk starting with the following command (hdb is the 250GB w/ recordings and hda is the blank new 400GB):

A) mfsbackup -Tao - /dev/hdb | mfsrestore -s 127 -r 4 -xzpi - /dev/hda

and got a "target too small" error so I dropped the "x" option on the restore:

B) mfsbackup -Tao - /dev/hdb | mfsrestore -s 127 -r 4 -zpi - /dev/hda

and that worked (took about 7 hours).

Reading more on this forum today I realized I might be headed for trouble in the future (like the GSOD) if I didn't allow for even more swap space, so I did another backup and restore:

C) mfsbackup -Tao - /dev/hdb | mfsrestore -s 250 -r 4 -xzpi - /dev/hda

and that worked too (another 7 hours).

My question is: Do I now need to use tpip to fix my 250MB of swap space, like this:

D) tpip --swapped -s /dev/hda

from the PTVupgrade CD (LBA48 CD v4.0) or am I OK because I was upgrading with a 7.2 system? Or have I created other problems for myself with the procedures above?

Sorry to be so clueless, I've done a lot of reading on this forum but I'm not confident about my understanding.


UPDATE: I think my TPIP question was answered by this reply from azitnay (http://www.tivocommunity.com/tivo-vb/showthread.php?p=3407375&&#post3407375) in another thread, so I'm proceeding with the above TPIP command.

[azitnay]

Yes, tpip fixes the swap header that MFS Tools is unable to create correctly when you try to give it more than 127MB of swap.

Drew

[Capricorn]

Hmmm, my new disk /dev/hda shows the same size as the 250GB disk I was copying from, that is 274 hours, instead of the 400+ hours I was expecting. Is that because on command "C" above I used the options "-zpi" (not options "-xzpi" as I mistakenly showed above)? I dropped the "x" option because I was getting the "target too small" error.

[Capricorn]

Another question, once you start using a disk is it too late to run TPIP on it? That is, will running TPIP blow away the shows that have been recorded or configuration info in the Tivo?

Thanks.

[miadlor]

Hmmm, my new disk /dev/hda shows the same size as the 250GB disk I was copying from, that is 274 hours, instead of the 400+ hours I was expecting. Is that because on command "C" above I used the options "-zpi" (not options "-xzpi" as I mistakenly showed above)? I dropped the "x" option because I was getting the "target too small" error.

Correct.........the drive didn't expand (X).
As far as too small.....Someone will know.

[Capricorn]

Thanks miadlor! I thought maybe the space caching data for the pipe was too small? If could change my setup so I could use the "x" option it sounds that would help. I have some 5-30GB drives around that I could use if that would work better than booting off a CD. Is there as CD image available that I could use to install Linux and the MFS and TPIP tools onto a scratch hard drive?

UPDATE: I'm downloading Fedora i386 version 4 to try a pipe running MFS from a hard disk. If it doesn't work, at least I'll have learned some Linux. :)

[ThreeSoFar]

Thanks miadlor! I thought maybe the space caching data for the pipe was too small? If could change my setup so I could use the "x" option it sounds that would help. I have some 5-30GB drives around that I could use if that would work better than booting off a CD. Is there as CD image available that I could use to install Linux and the MFS and TPIP tools onto a scratch hard drive?

UPDATE: I'm downloading Fedora i386 version 4 to try a pipe running MFS from a hard disk. If it doesn't work, at least I'll have learned some Linux. :)

Capricorn, I just ran into this same problem, destination too small. Dropping the x is allowing the backup/restore to proceed.

Did you try mfsadd to then expand the resulting system? That's what mfsadd does, right?

I'm about to try that after the mfsbackup|mfsrestore finishes in a few hours.

[ThreeSoFar]

mfsadd failed.

But this worked, preserving season passes and wishlists but losing all recorded content:mfsbackup -f9999 -so - /dev/hdaX| mfsrestore -s 250 -xzpi - /dev/hdaY
followed by:tpip -s --swapped /dev/hdaYto enable the swap size > 127.

Seems like if this combination worked that the usual mfsbackup -Tao - should have worked, but it didn't.

Capricorn, I just ran into this same problem, destination too small. Dropping the x is allowing the backup/restore to proceed.

Did you try mfsadd to then expand the resulting system? That's what mfsadd does, right?

I'm about to try that after the mfsbackup|mfsrestore finishes in a few hours.

[jinatera]

:confused:

please help me I need to made 10,000 clones of one tivo 250 gb I see to copy sector per sector on a copier machine but takes soo much time 2 gb per minut so I need to find a faster option the hd are brand new and are exactly the same that the original please help me I sure we can do if I make the partition and only copy the files that I need

[azitnay]

I don't even want to try to guess what you're doing with 10,000 clones of a TiVo drive, but if you're just trying to image the drives without copying recordings, I'd recommend first making a small backup image using mfsbackup with the -f 9999 and -s options, and then restoring that image to each drive using mfsrestore.

Drew

[Luv2DrvFst]

I have an S2 DTiVo (Hughes) that was previously upgraded to 2 drives (120GB each). MFSTools tells me I can't compress this back to one drive anymore and save recordings, so I want to create 2 new larger drives (320GB and 250GB). However, to use mfsbackup | mfsrestore I need all four of my IDE ports, therefore requiring a TiVo boot floppy. I can't find a boot floppy with LBA48 support -- does one exist? Or, I do have a PCI-card ATA controller installed that the WeaKnees LBA48 boot CD recognizes at startup and properly reads the new drives attached to it. However, I can't get MFSTools to recognize any drives connected to the PCI-card ATA controller (hdg and hdh). I know if I give up on my recordings this is easy, I've done it. But I really want to keep my recordings. Any ideas how this can be done (and I need to increase swap to 127 at the same time).

I've tried everything I've read and researched on all the TiVo forums and can't seem to get this solved. Any ideas?

[HomeUser]

You can use almost any version of Linux to run MFSTools with. Some of the run from CD versions if your system supports it will boot from a SATA or USB drives.

For running the cd you currently have with your ADD-ON IDE card see http://www.tivocommunity.com/tivo-vb/showthread.php?p=3055744&&#post3055744

[blarg]

I believe weaknees has one.

[Luv2DrvFst]

Thanks HomeUser for the lightning fast reply! That link has gotten the backup|restore successfully started -- I've got about 230GB to move so whenever it finishes I'll let you know if it worked. It seems to be going much faster than when I used the boot floppy (that took about 22 hours). It looks like it will only take about 3 hours this time. I hope that's just a function of using a faster ATA controller and the boot CD...

Thanks again.

[Athome17]

I just upgraded my series2 6.2 directv tivo DVR40 to 160GB drive using mfstoos2. It seems to have worked mostly, didnt save my recorded programs. The tivo backup was 1GB so I restored this to my 160GB drive and started my tivo. It booted and I see programs. However, when I push my list or directv button the menu is overlayed on the screen so I see the live TV at the same time I am trying to select from my play list. Is this a common problem? Does the mfstool change basic setups of some kind to change my display on the tivo?

[ThreeSoFar]

Common problem, yes. If you still have your original drive, redo the backup, adding the "-f 9999" option. See the "Hinsdale HOWTO (http://www.newreleasesvideo.com/hinsdale-how-to/index9.html)".

[Athome17]

"Common problem, yes. If you still have your original drive, redo the backup, adding the "-f 9999" option. See the "Hinsdale HOWTO". "

The document I had didnt reflect that and the tools that I had may have been old. The hinsdale guide was great so I started over and did a complet copy 2hrs to complete but very easy. Thank you.

[dragonslayer]

I used the hinsdale guide for a larger hard drive, but when I plug in my new larger hard drive into the tivo it shows the new hard drive recording space of 37hours only how do I fix that, can some help me please.

[ThreeSoFar]

I used the hinsdale guide for a larger hard drive, but when I plug in my new larger hard drive into the tivo it shows the new hard drive recording space of 37hours only how do I fix that, can some help me please.

37h or 137h?

If you mean 137h, you should use the LBA48 boot CD instead of the one you did, which only recognized the first 137G of your new drive.

If you mean 37h, did you skip the mfsadd step?

Before doing anything once the CD boots, it's always nice to run this to see what drive is where:dmesg | grep hd

[dragonslayer]

37h or 137h?

If you mean 137h, you should use the LBA48 boot CD instead of the one you did, which only recognized the first 137G of your new drive.

If you mean 37h, did you skip the mfsadd step?

Before doing anything once the CD boots, it's always nice to run this to see what drive is where:dmesg | grep hd

I installed a 80G hard drive total recording time is 127hrs, you are correct "ThreeSoFar" I did miss that step, once I plug it back in my PC & finally finished that step, now I facing another problem it is stuck at " Powering up" screen what should I do.......can you please help.

[ThreeSoFar]

I installed a 80G hard drive total recording time is 127hrs, you are correct "ThreeSoFar" I did miss that step, once I plug it back in my PC & finally finished that step, now I facing another problem it is stuck at " Powering up" screen what should I do.......can you please help.
Usually that's a jumper problem. Is it still jumpered to slave? All cables snugly fit?

[dragonslayer]

I really do appreciate all you help........Thank you very much

[sheetbird]

Hi List,

I'm attempting to add a 300 GB drive while keeping the orig 80 GB drive to a previously unmod'd S2 (TCD24008A) using the Hinsdale HowTo Upgrade Config #1 and Weakness bracket. I did the back up with the test restore fine. However when I put the orig Drive and new drive in shortly after the TiVo splash screen (yellow/black ... few minutes more) I get a green screen (GSOD) which leads to a reset after about 15-20 seconds. I have some shows on the 80GB I'd like to keep.

The only command affecting my original drive was:
./mfstool add -x /dev/hdX /dev/hdY
where X is the orig and Y is the new drive to be added on.

Any suggestions

Thanks,

Paul

[JamieP]

I'm attempting to add a 300 GB drive while keeping the orig 80 GB drive to a previously unmod'd S2 (TCD24008A) using the Hinsdale HowTo Upgrade Config #1 and Weakness bracket. I did the back up with the test restore fine. However when I put the orig Drive and new drive in shortly after the TiVo splash screen (yellow/black ... few minutes more) I get a green screen (GSOD) which leads to a reset after about 15-20 seconds. I have some shows on the 80GB I'd like to keep.You should have used "-r 4" in the mfsadd command line since you are created a partition > 274GB. This is covered in the Weaknees guide. The Hinsdale guide has never been updated to reflect changes required for large drives, so I no longer recommend it.

You are now in a bit of a pickle, since you've married the two drives together incorrectly. To recover from this, you'll need to make a divorced backup, then restore it back to the drives. Normally you'd lose your recordings when you do this. It might be possible to save your recordings, but you'll need a scratch drive large enough to hold them. You'll probably need something as larger or larger than your current tivo A drive.

[subslug]

After some power outages from a storm that rolled through our area my 40 hour tivo's hard drive had began to make a noisey high pitched sound. Not wanting to risk anything I went and got a new 120gb hard drive, downloaded the MFS tools and followed the how-to and in no-time I have a quieter, not to mention larger Tivo now!
Thanks for the excellent tools to repair these devices with. I wouldn't even want to think about what we'd do if it wasn't for them.

[charlestwaters]

Here's a ?.. Can you use the MFS tools program to access and read/write MFS directly!? For instance... changing channel logos, adding channel logos, etc., since the import doesn't work on the TWP!?

--- Charles!

HR10-250

[ymichael12]

I recently was trying to upgrade my 24004A tivo from a 40GB to the 300GB drive I just got.

I was initally lazy and not going to run a backup but now I think I should have.

I had the "A" tivo drive and new "B" dive connected to my computer, boot with a mfs disk i got from weaknees and did mfsadd -r 4 -x /dev/hda /dev/hdb, my tivo is only recognizing 200 hrs of time when it should be much more right? No errors when starting up, just the incorrect drive space (also tivo has not been running for more than 5 minutes with this error)

How do I expand the 300 drive now? Once it is fixed to see all 300 I will then make a backup (which I think I can do).

[kev-mc]

I have a Hughes HDVR2 that I had previously added a second 40gb drive to. When I did this, the capacity with the two 40gb drives increased from 35hrs to 71hrs. I just recently wanted to replace the two 40gb drives with one 160gb drive, but I wanted to keep my recordings. After trying and failing, and then doing a little searching, I found that I could not do this because of a partition limit. I decided to use two 60gb drives instead. I used the PTV-LBA48 boot CD with MFSTools 2.0 and just did a dd drive copy from each 40gb drive to the new 60gb drives. After verifying that everything went correctly I expanded both drives at the same time with the 'mfsadd -x /dev/hdc /dev/hdb' command. At the end it reported that I had previously had 89hrs and that I would know have 105hrs. Well I originally had 71hrs not 89hrs. I then put the drives back into the Directivo and they only show 89hr capacity, not 105hrs as reported by MFS Tools 2.0.

Did I miss something? The drives work fine and all the recordings are still there. I just need to know why I'm not getting the 105hrs. I have another Directivo that I removed a 40gb drive from and replaced witha 120gb drive. This unit shows a 107hr recording capacity. I assumed that having two 60gb drives would give me the same amount of time. What do I need to do? I would have preferred to use the 160gb drive and keep my recordings but since that doesn't look like its going to work. I figured that the two 40gigs were my best bet.

Both units have 6.2 software version on them, just in case that matters.

[azitnay]

It sounds to me like the mfsadd only expanded one of the two 60GB drives (i.e. one of them is now utilizing 40GB and the other is utilizing 60GB). This works out mathematically, since 71 * 100 / 80 = 88.75 (around 89).

As to why, I don't know for sure, but this may simply be a limitation of mfsadd (or quite possibly, a limitation on number of partitions).

Drew

[mmulet]

OK, I'm stumped.

I've tried 3 different computers, and both the Weaknees as well as MFSTools with LBA, and can't seem to get any of the computers to recognize more than 137G on the new drive.

The setup is:

Original computer drive as Primary Master, 300G Maxtor as Primary Slave, Original Tivo 40 G drive as Secondary Master, and CD-ROM drive as Secondary slave.

All drives are correctly recognized EXCEPT the 300G Maxtor (only recognizing 137G). I am using an LBA Kernel. I've tried with all BIOS settings on NONE & Auto, with LBA turned on and off.

I thought the kernal ignored the BIOS settings; and that by using the LBA kernal it would recognize the 300 G drive. Am I missing something here? Tried the Diskunlock but received the error - disk already unlocked.

I'm pulling my hair out here! Any and all help is greatly appreciated!


mmulet

[ThreeSoFar]

OK, I'm stumped.

I've tried 3 different computers, and both the Weaknees as well as MFSTools with LBA, and can't seem to get any of the computers to recognize more than 137G on the new drive.

The setup is:

Original computer drive as Primary Master, 300G Maxtor as Primary Slave, Original Tivo 40 G drive as Secondary Master, and CD-ROM drive as Secondary slave.

All drives are correctly recognized EXCEPT the 300G Maxtor (only recognizing 137G). I am using an LBA Kernel. I've tried with all BIOS settings on NONE & Auto, with LBA turned on and off.

I thought the kernal ignored the BIOS settings; and that by using the LBA kernal it would recognize the 300 G drive. Am I missing something here? Tried the Diskunlock but received the error - disk already unlocked.

I'm pulling my hair out here! Any and all help is greatly appreciated!


mmulet


You are almost certainly NOT using an LBA48 kernel. That's the only thing that would cause this.

What are you booting, one of the TiVo bootable CDs? What was the URL to that .iso that you burned?

[mmulet]

I think it was a bad hard drive.

I went out and purchased a 300G Seagate drive, and it was recognized without any difficulty.

So, it looks like I have a faulty Maxtor 300G drive.

Thanks!


mmulet

[mmulet]

OK, so the Seagate HD is recognized, but now I get a green screen of death.

I restored the backup image to a NEW 80g Seagate drive (original remains untouched other than backing it up).

I put the new 80G drive back into the Tivo, everything works fine (reported 39 hours, but I hadn't added the additional space, so I wasn't concerned).

So, I hooked up the new 80G drive and the new 300G drive, and did the mfsadd according to the info in Hinsdale's guide. (no -r 4 command, though). Now I get a GSOD.

How do I recover? I still have the original 40g drive, and the 40g's backup image.

Do I just start over, but use -r 4 when doing the msadd? Specifically, what should I do to msadd both drives?

Do I need to do anything to the drives before trying again (ie, like divorce them, reinitialize, etc.)?

Any and all help is greatly appreciated!

mmulet

[mmulet]

OK, got it all working.

I did an MFSbackup/restore from the original drive to the new 80 g drive, and then did an MFSADD with -r 4 with the the new 300 g drive, and all is working for now.

Thank you everyone for your help.

mmulet

[DarkWingDW]

I inadvertantly started WinXP with my original Tivo drive connected to PC. During a back-up of a new and larger HD, will MFS Tools automatically correct the corrupt boot sectors during the back-up or will the corrupt boot sectors be copied to the new drive? I'm asking because I'm not sure if I need to run the MakeTivoBootable on the new hard drive to make it bootable in the Tivo.

Any information would be appreciated.

[eatcarrotsnow]

I downloaded the bootable iso file from the link on the first page. When I click to record the image in Nero, it says unexpected file format. It does this for both the floppy and the ISOLINUX image. What program is this image designed for? What folders also need to be on the cd to use mfstools?

Thanks!

[HomeUser]

The .iso image is complete by its self don't add anything. Just open nero burning rom, cancel the wizard, select file, open, select the .iso file click the open button and burn. I don't know if that image is LBA48 bootable. Instead you might download the PTV or Weaknees LBA48 versions.

[eatcarrotsnow]

I tried it that way too, it still says unexpected file format. I don't have a floppy drive on my computer, so I can't use that one either. I'm using Nero 7, so it should work. Anyway, thanks for the help.

[HomeUser]

I never up-graded from Nero 6 I suspect that the downloaded image may be corrupted you might try downloading and burning a different one PTVupgrade LBA48 CD v4.02 (http://www.ptvupgrade.com/products/software/lba48/lba_4.02_license.html).

[eatcarrotsnow]

Nope, I've downloaded one from weaknees, your link, and the one from the original site. Nero gives the same exception every time. I burned it in Alcohol 120 under the data mode 1, block size 2048, and the disc burns blank. I don't know what to do at this point.

[HomeUser]

I just tried it a different way right click on the mfstools2.iso, select "Open With" then "Nero Burning ROM" then Burn no problem the CD booted just fine.

The selections in the burn tab all but Write speed were left at the defaults
"Write" checked
"Finalize CD" not checked
"Write speed:" I did change this to 8X (1,200 KB/S) I have slow computer.
"Track-at-once"
"Number of copies:" 1
"SMART-BURN" checked
"Use multiple recorder" is not checked

Which OS and what kind of CD burner are you using?

[johnmsch]

First and foremost, thanks for all your hard work. I added a second drive to my Series 2 (24004A) a couple of years ago. Bought the kit from Weaknees, used MFStools and the Hinsdale guide, and it went smooth as silk.

Now I'm wanting to replace the original 40GB hard drive with something larger, like 250GB. I'm on version 7 of the TiVo software, so I'm assuming that the 137GB limit does not exist any more?

I've read through most of the posts in this thread, and noticed somewhere it was mentioned that the Hinsdale guide is not current with regards to the new drive sizes and/or the new MFStools?

Will MFStools make all of the >137GB drive available? What about my current "B" drive (160GB) - will the extra space above 137GB be used after the upgrade?

Just when I thought I had all this figured out, I'm getting confused again!

Thanks again for your efforts!
John

[chrispitude]

Hi all,

So I've read the last several pages, and I see some people have run into the "target too small" problem when doing a second upgrade. I can join that club. :)

I've upgraded my Series 2 540040 once a year ago, from the factory 40GB to a 200GB drive. This first upgrade with MFSTools was quite easy and uneventful! Now I would like to upgrade the 200GB to a 400GB drive, and keep all my recordings and season passes. It's this upgrade that is giving me the "target too small" error:

mfsbackup -Tao - /dev/hdc | mfsrestore -s 127 -xzpi - /dev/hdd

The source (200GB) and destination (400GB) drives are definitely correct. I see some people trying some different switches, removing the x, something about swap space, etc.

Given that I haven't actually done anything which has written to the new drive yet, what's the right set of commands to move from an upgraded drive to a new larger upgraded drive?

Edit: I think what I am really asking is, is 127MB enough swap space for a Series 2 with a 400GB drive? I just reissued the command with -s 127 and without -x and we'll see what happens. :) I'll report back...

Edit: After more reading, I got paranoid and increased the swap to -s 200...

Thanks all!

- Chris

[ThreeSoFar]

Edit: After more reading, I got paranoid and increased the swap to -s 200...

Thanks all!

- Chris
Don't forget the tpip step...

[chrispitude]

Don't forget the tpip step...

Well, I'm almost there! The copy completed and I downloaded tpip. Unfortunately I don't see the --swapped flag that people are using. tpip v1.2 has the following usage:

usage: tpip [-12abpsVv] [-k kernel] [-o old_kernel] [-P "boot params"]
[-S {0,1}] device
tpip [--alternate] [--bootpage] [--flipboot] [--kernel=kernel]
[--mkswap] [--old_kernel=old_kernel] [--parameters="boot params"]
[--partitions] [--series1] [--series2] [--swaptype={0,1}]
[--verbose] [--version] device

Any thoughts?

Edit: I found a post on the MFSTools swap topic which suggested "./tpip -1 -s /dev/hdY" so I tried that and put the drive back in my TiVo. The good news is, it boots up! The bad news is, System Information says it's 224 hours and I'm not sure if that's right for a 400GB drive or not.

- Chris

[chrispitude]

Suddenly, now that I've finally hit all the same problems, the previous posts make sense to me. :) I'm stuck again, and hopefully Tiger (or someone else) can help.

I originally upgraded my factory 40GB drive to 200GB. I am now trying to upgrade from 200GB to 400GB. When I attempted to do an "mfsrestore -xzpi" when copying the 200GB to the 400GB, I got the message about the target drive being too small. I left out the -x option and the copy succeeded. However, the new drive only shows 224 hours, which is consistent with an unexpanded partition.

So, I hooked up the 400GB drive to my linux box and tried mfsadd:

# ./mfstool add -x /dev/hdc
Expand of /dev/hdc would result in too many partitions.

Here's the partition list:

# ./mfstool info /dev/hdc
MFS volume set for /dev/hdc
The MFS volume set contains 6 partitions
/dev/hdc10
MFS Partition Size: 256MiB
/dev/hdc11
MFS Partition Size: 16354MiB
/dev/hdc12
MFS Partition Size: 256MiB
/dev/hdc13
MFS Partition Size: 21563MiB
/dev/hdc14
MFS Partition Size: 0MiB
/dev/hdc15
MFS Partition Size: 151832MiB
Total MFS volume size: 190262MiB
Estimated hours in a standalone TiVo: 222
This MFS volume may be expanded 3 more times

I am lost...

- Chris

[chrispitude]

After doing some more reading, I guess I am trying to figure out the real deal with the partition limit. The first post in this topic says:

Upgrade a second time without losing recordings
It's all over the hack FAQ and the underground. You can only have TiVo upgrade with a blessed drive once. It is set in stone, if you want to upgrade again you lose recordings. Not anymore. Due to research into the workings of TiVo, MFS Tools is now able to upgrade a drive without having to bless it and rely on the TiVo software to upgrade it correctly. In fact, with MFS Tools 2.0, you can upgrade again and again, upgrading one drive up to 5 times (3 for some models)

I've only upgraded once so far, so according to the above, I should have at least one or two more upgrades left. mfsinfo clearly says "This MFS volume may be expanded 3 more times", but mfsadd tells me I have no more partitions left. According to mfsinfo, there are indeed three matched MFS pairs on my drive.

Does anyone have any insight into MFS partition limits, and how to reconcile it with the statements above?

- Chris

[JamieP]

Does anyone have any insight into MFS partition limits, and how to reconcile it with the statements above?There is a limit on the number of mfs partitions on a single A drive (3 partition pairs) and a limit on the total number of mfs partitions over all drives -- 128 characters total in the device list. This overall limit basically boils down to 6 pairs: the longest possible device list string is: "/dev/hda10 /dev/hda11 /dev/hda12 /dev/hda13 /dev/hda14 /dev/hda15 /dev/hdb2 /dev/hdb3 /dev/hdb4 /dev/hdb5 /dev/hdb6 /dev/hdb7".

mfstools is reporting the combined limit, not the single A drive limit.

The easiest solution to your problem is to copy/expand sans recordings. You can save any recordings you really want to keep to your PC and restore them later.

[chrispitude]

Hi Jamie,

Thank you! Now I think it makes sense. The three additional expansions would be three new pairs onto a new drive then.

I have lots of recordings I want to save, but I can put the old drive back in and begin copying those over to my PC. Now the big question is, if I copy things over and lose the recordings:

mfsbackup -f 9999 -so - /dev/hdc | mfsrestore -s 200 -r 4 -xzpi - /dev/hdd

will that reduce my partition count so that I can expand again in the future?

Also, here's a twist... The linux box I am using to do all of this has a 900GB RAID array on it. Is there some way I can use that to store recordings temporarily from the old drive, and somehow combine them together and put them on the new 400GB drive with fewer partitions?

Sorry to answer your kindness with yet more questions...

- Chris

[JamieP]

Now the big question is, if I copy things over and lose the recordings:mfsbackup -f 9999 -so - /dev/hdc | mfsrestore -s 200 -r 4 -xzpi - /dev/hddwill that reduce my partition count so that I can expand again in the future?The "-s" in the mfsbackup will shrink your mfs volume back down to the original two partition pairs. The -x in the restore will expand to fill the target drive, adding another partition pair. So you'll have a single expanded drive, but it will have a full partition table.Also, here's a twist... The linux box I am using to do all of this has a 900GB RAID array on it. Is there some way I can use that to store recordings temporarily from the old drive, and somehow combine them together and put them on the new 400GB drive with fewer partitions?On a hacked tivo, yes, using extraction methods that can't be discussed here. In that case, you can use tivoserver to put the shows back on the tivo. On an unhacked tivo, you can use the TTG/GoBack options in Galleon to pull your shows on to the raid and serve them back to the tivo. The main disadvantage of this approach is that TTG is really, really slow compared to the techniques we can't talk about. 5-10 times slower.

There is another option that I hesitate to recommend, 'cause it is ugly, but if you like to roll up your sleeves and get your hands dirty in the bits, you can look at this (http://alt.org/forum/index.php?t=msg&th=124#msg_num_2) partition coalesce approach to solve the original full partition table problem. The main disadvantage of this approach is that the result is a non-standard tivo drive layout that mfsbackup won't be able to correctly back up.

[chrispitude]

The "-s" in the mfsbackup will shrink your mfs volume back down to the original two partition pairs. The -x in the restore will expand to fill the target drive, adding another partition pair. So you'll have a single expanded drive, but it will have a full partition table.

Jamie, thanks for all your help. Over the weekend, I finally got this done using the following commands:

mfsbackup -f 9999 -so - /dev/hdc | mfsrestore -s 200 -r 4 -xzpi - /dev/hdd
./tpip -1 -s /dev/hdd

The TiVo saw the new drive and confirmed over 400 hours of storage space. I then did a "Delete All Shows/To-Do" which I figured would be a good way to clear out the current programs. Unfortunately, this seemed to put my TiVo into la-la land. None of the programs were removed; I had to delete them all manually. Even stranger, every season pass entry showed no upcoming episodes ("This show has no upcoming episodes."), yet the guide worked perfectly and I could see the upcoming episodes . I finally gave up and did a full reset, and it's been working great ever since. My season pass list needed some housecleaning anyway. :)

Thanks to everyone for their help!

- Chris

[mike55btz]

If I am going to go to a 500gb single on my series 2 is there a general rule of thumb to make the swap size...


I was thinking a swap of 200 then tpip it when done.

[ZeoTiVo]

so where can I get a boot floppy of MFStools with lba48 support ?
aslo where can I get tpip ?

[azitnay]

Do you specifically want a floppy in lieu of a CD for some reason, Zeo? I don't know that anyone's ever made an LBA48-compatible floppy, but the following CD-ROM supports LBA48:

http://www.ptvupgrade.com/products/software/lba48/index.html

I believe it also contains tpip.

Drew

[ZeoTiVo]

Do you specifically want a floppy in lieu of a CD for some reason, Zeo? I don't know that anyone's ever made an LBA48-compatible floppy, but the following CD-ROM supports LBA48:

http://www.ptvupgrade.com/products/software/lba48/index.html

I believe it also contains tpip.

Drew

Thanks all. The TiVo is up an running with 225 hours at best quality.
This was a DT series 2 going from stock 80 hour drive to single 500GiG drive

I thought the PTV link would cost money. Happy to see it had a free option for the opne source stuff I needed :up: Including tpip 1.2.

once the CD-ROM is booted you can dodmesg | grep hdto be sure the Hard drives are seen as the right size.

so also armed with weakness interactive instructions (www.upgrade-instructions.com) on how setup the hard drives in the PC and what that means to the command (I was upgrading a new TiVo so no need to copy over the shows)mfsbackup -f 9999 -so - /dev/hd? | mfsrestore -s xxx -r 4 -xzpi - /dev/hd? I knew how to replace ? with the right drive letter and in reading here I found the rule of thumb to replace '-s xxx" with a swap file size of 1 meg for every 2 GIG. "-s 300" is what I used for my 500Gig to be sure it would have plenty of room.

after that it is just a matter of using the TPIP 1.2 from the PTV CD-Rom to set up the swap file headerTPIP -1 -s /dev/hd? again replace the ? with the correct drive designation you did the mfsrestore to per weakness instructions.

A big thanks to all who posted here and made finding this info easier and an great big thank you to those who made these tools that made this upgrade a lot less of a command line fest :up:

[Jeremybme]

Hi,

First let me thank everyone who has helped in the past and who might help this time.

I have upgraded my series 1's
and eventually replaced with Series 2's and upgraded those as well

Here are some general questions.

I want to buy a new Tivo one of the dual tuner ones. does anyone have the following answers


1... is it possible to upgrade hard drives like previous Series 2?
2... If so what guide should i use now for large hard drives, in the past i have used hinsdale, but it still talks about 137gb limitation
3... is it true that the dual tuner will not work at all with over the air TV it always has to be cable?
4... will i be able to transfer shows to my older series 2's (right now i transfer between them)


Thanks Again. any help is appreciated.

[azitnay]

1) Yes.

2) http://tivo.upgrade-instructions.com/index.php works well.

3) Yes (I won't go into why; I'm sure there are several threads somewhere on these forums discussing it). Further details on what each tuner can record can be found at http://www.weaknees.com/tivo-dual-tuner.php.

4) Yes.

Drew

[Jeremybme]

Thank You Drew!

Now that i know its possible, and have the link for guide. Im on my way to buy a new Tivo from the store..

-Jeremy

[sjmaye]

Probaby a simple question for the veterans here-

I have been running my Zippered single drive (250GB) HD D*Tivo HR10-250 for about a week now. Everything is working great. I want to add a second drive (400GB).

Here is an excerpt the Hinsdale How-to that is a bit confusing to me.

UPGRADE CONFIGURATION #1:

From: Any Single Drive TiVo

To: Adding a New B Drive

(Fast option – preserves setup, season passes, etc. and recordings)

If you are simply adding a new large B drive to your existing (unmodified or expanded) TiVo A drive from your single drive unit, then your season passes, setup, and recordings will be preserved. After creating and testing your Mfs Tools backup image, all that is remaining to do for this upgrade configuration is to run Mfsadd to make your existing A drive aware of the added space provided by your new large upgrade B drive

Swap File: When increasing your total recording capacity (A+B drives) to over ~140GB (actual threshold number is likely just over 150GB for Series 1 Standalones and over 180GB for DirecTiVos and Series 2 units) the preferable method for upgrade should include a means to increase the swap file so that the built-in TiVo repair utility (GSOD) can complete if ever triggered (rare). Those upgrading to these larger capacities should consider using the Mfs Tools restore option (-s 127 command line parameter increases the swap) outlined in Upgrade Configuration #2 (test image has increased swap already - does not preserve recordings) or Upgrade Configuration #3 (preserves recordings - time consuming) in preference to simply using mfsadd described below to increase recording capacity.

At the # prompt both Boot Cd and Floppy users type the following command:

(The following command assumes your existing TiVo A drive is connected as Secondary Master and your new large upgrade B drive is connected to the Primary Slave)



mfsadd -x /dev/hdc /dev/hdb (Boot CD and Floppy users command)


MFSTools is supposed to be on my LBA48 CD I bought from PTVnet
Can I still use the MFSADD since my drive has been modified via the Zipper?
I have read of the GSOD if you do not increase your swap file size when doing something like this. Where/Who is this done?
Do I use the -x or -r parameter. I have read about both.

[sjmaye]

Thanks all. The TiVo is up an running with 225 hours at best quality.

I thought the PTV link would cost money. Happy to see it had a free option for the opne source stuff I needed :up: Including tpip 1.2.

once the CD-ROM is booted you can doto be sure the Hard drives are seen as the right size.

so also armed with weakness interactive instructions (www.upgrade-instructions.com) on how setup the hard drives in the PC and what that means to the command (I was upgrading a new TiVo so no need to copy over the shows) I knew how to replace ? with the right drive letter and in reading here I found the rule of thumb to replace '-s xxx" with a swap file size of 1 meg for every 2 GIG. "-s 300" is what I used for my 500Gig to be sure it would have plenty of room.

after that it is just a matter of using the TPIP 1.2 from the PTV CD-Rom to set up the swap file header again replace the ? with the correct drive designation you did the mfsrestore to per weakness instructions.

A big thanks to all who posted here and made finding this info easier and an great big thank you to those who made these tools that made this upgrade a lot less of a command line fest :up:

You seem to have had success. Could you give me a hand? I had posted this over in the Zipper section. Probably the wrong place, but they have been great at getting me up and running with a Zippered drive.

I have a Zippered 250GB that was working perfectly. I wanted to add a 400GB drive. I read the best way to do this was to use the MFSADD command. Following the Weaknees instructions I did this:

First try-
hda - cd drive
hdc- 250GB Zippered drive (jumper on Master)
hdd- 400GB New drive (Jumper on Slave)

mfsadd -r 4 -x /dev/hdc /dev/hdd

After I struck enter it took a bit, but it showed about 761 hours. Sounded about right.

Installed in to HR10-250. Boot cycle all worked like usual. I still had my Zippered drive enhancements. I checked System Info. Recording capacity did not change 30hrs HD, 200hrs SD.

I read a post where two other people had the exact same problem. They said the drives had to be on different IDE channels and did not use the "-r 4" option.

Second try-
hda - 250GB Zippered drive (jumper on Master)
hdc- cd drive
hdd- 400GB New drive (Jumper on Slave)

ran:

mfsadd -x /dev/hda /dev/hdd

After I hit return response was pretty quick- "added 480 hours" for a total of 761hrs.

Looked good.

Put drives in the HD D*Tivo and booted. Got past the Tivo unleashed splash, rebooted waited a while, then GSOD. After a few seconds on GSOD it rebooted again. This process kept repeating.

Third try-
I thought I might have needed the "-r 4" after all and went to try it. Took the drives back out and put them in the PC. The response was "nothing to add".

Now I am stuck. I could probably start from scratch, reapply the drive image, and rezipper with both drives from the start, but I hate to add back all my season passes etc.

Based on everything I have read I think I married the drive together correctly. Looks like I have to change my swap file size.

Since the TIVO was down with little chance of me fixing it soon I put the factory drive back in so I bought some time.

My dilemma-

I would like to save my Season Passes and settings. If possible I would like to save the recordings.
I had hoped it would be as simple as mfsadd to marry the drives and everything would work fine. NOT.
I did not make a backup of drive before marrying the two together.
I would definitely like to save all my settings
I would prefer to save my recordings, but not a must
I think I need to increase my swap file size, but the only way I can see to do this is to do a backup and then restore it and I am not really sure how with these two drives

No matter how carefully I approached this thing I screwed it up and can not figure a way back out of it.

Can someone help?

[ZeoTiVo]

You seem to have had success. Could you give me a hand? I had posted this over in the Zipper section. Probably the wrong place, but they have been great at getting me up and running with a Zippered drive.

sorry I did my upgrade on a Series 2 DT unit and am not well versed in two drives. I did not see what the problem was from reading your post.

[JamieP]

Can someone help?You do need -r 4 when adding partitions > 274 GB. By marrying your drive to a B drive without -r 4, you've made a mess that will be difficult to clean up without dropping your recordings.

[Brillian1080p]

If you have recordings that are important to you and you can't seem to access them, you might want to try this program.

Winhex.

You'll have to see if it would work for the Linux/Tivo.

I had a crash and thought I had lost a couple years of my Twin Grandbabies pictures. I tried this program and it saved my rearend.

I was considering paying one of those data salvage companies.

They have a trial version.

[sjmaye]

You do need -r 4 when adding partitions > 274 GB. By marrying your drive to a B drive without -r 4, you've made a mess that will be difficult to clean up without dropping your recordings.

I can do without the recordings, but would like to avoid redoing the Zippering of the drive all over again.

Is there a way to do that?

[sjmaye]

I can do without the recordings, but would like to avoid redoing the Zippering of the drive all over again.

Is there a way to do that?


I did some over night reading. It looked like I needed to create a backup of my drives.

Following the Hinsdale guide I created a 2GB FAT32 partition on my project PC C:/ drive.

I then performed the backup as specified. There was one instruction I was sure of:

At # prompt both Boot Cd and Floppy users type the following commands to mount your C: drive:

mkdir /mnt/dos
mount /dev/hda1 /mnt/dos

This is what I actually typed:

mkdir /mnt/dos
mount /dev/hda2 /mnt/dos

I entered hda2 as when in linux I performed fdisk -l and that the FAT32 partition showed "hda2".

The whole backup operation went well and I can see it on the drive, but I am not sure if I am looking at hda1 or hda2.

I am ready to restore the backup and expand, but do not want to screw it up again. Can someone give me some pointers where to go from here?

Configuration I am trying to get to a dual drive Zipper:
Tivo A 250GB (currently located on hdc)
Tivo B 400GB (currently located on hdb)

[sjmaye]

so also armed with weakness interactive instructions on how setup the hard drives in the PC and what that means to the command (I was upgrading a new TiVo so no need to copy over the shows)
mfsbackup -f 9999 -so - /dev/hd? | mfsrestore -s xxx -r 4 -xzpi - /dev/hd? I knew how to replace ? with the right drive letter and in reading here I found the rule of thumb to replace '-s xxx" with a swap file size of 1 meg for every 2 GIG. "-s 300" is what I used for my 500Gig to be sure it would have plenty of room.

after that it is just a matter of using the TPIP 1.2 from the PTV CD-Rom to set up the swap file header
TPIP -1 -s /dev/hd? again replace the ? with the correct drive designation you did the mfsrestore to per weakness instructions.

A big thanks to all who posted here and made finding this info easier and an great big thank you to those who made these tools that made this upgrade a lot less of a command line fest


Guys- I am sorry to be such a pain, but I have just about worn the threads bare on the tivo taking drives in and out. Just trying to get it right this time. I appreciate your help AND patience :o

If I understand this correctly, in my situation:
hd? would be hda2 since mybackup image is there? It doesn't need to know exactly what directory?
the xxx should be about 325? for a 325MB swap file for my combined hd total of 650GB
the hd? in mfsrestore would be hdc? since this is where my "Tivo A" drive is?

then I issue a mfsadd command with the "-r 4"? to marry the drives correctly?

[ThreeSoFar]

Guys- I am sorry to be such a pain, but I have just about worn the threads bare on the tivo taking drives in and out. Just trying to get it right this time. I appreciate your help AND patience :o

If I understand this correctly, in my situation:
hd? would be hda2 since mybackup image is there? It doesn't need to know exactly what directory?
the xxx should be about 325? for a 325MB swap file for my combined hd total of 650GB
the hd? in mfsrestore would be hdc? since this is where my "Tivo A" drive is?

then I issue a mfsadd command with the "-r 4"? to marry the drives correctly?Sounds like your first hd? was fine for the FAT32 partition. If booted to windows your PC sees the .bak file where you expect it to, then you're fine. Also, it should be pretty big.

The xxx of 325 for your swap size should be fine. NOTE THOUGH: "tpip" should be in all lowercase.

hd? in mfsrestore---that should be where your new TiVo A drive is. A "dmesg | grep hd" command will help you clarify (by size/brand of drive) that that is the case.

Finally, if you're doing this command:mfsbackup -f 9999 -so - /dev/hd? | mfsrestore -s xxx -r 4 -xzpi - /dev/hd?Then you DO NOT need the mfsadd command. The "x" argument to mfsrestore takes care of that (expand to fill the drive).

Good luck!

[JamieP]

Guys- I am sorry to be such a pain, but I have just about worn the threads bare on the tivo taking drives in and out. Just trying to get it right this time. I appreciate your help AND patience :o

If I understand this correctly, in my situation:
hd? would be hda2 since mybackup image is there? It doesn't need to know exactly what directory?
the xxx should be about 325? for a 325MB swap file for my combined hd total of 650GB
the hd? in mfsrestore would be hdc? since this is where my "Tivo A" drive is?

then I issue a mfsadd command with the "-r 4"? to marry the drives correctly?You want to restore from the backup, not copy from one disk to another. This is necessary since you are going from a dual disk setup (A+B) and overwriting one of your drives (I'd do the 400GB B drive).

Go lookup the Weaknees instructions for restoring from a backup on your model. Hinsdale is no longer a good reference, since it leaves out little critical details like -r 4 for large drives.

If you really want to be safe, buy a third drive and restore to that instead, so you don't overwrite either of your drives until you know the backup worked.

[sjmaye]

OK, if I don't get it working it's not for a lack of trying! :eek:

Thanks for all the input, however, after reading and re-reading I finally came to the conclusion I would just start over.

On the Tivo A drive I redid the process I did before that had my single drive working right with the Zipper.

Installed a fresh Instantcake HR10-250 drive image
Ran the Zipper
Reported SUCCESS at the end

With Tivo A on hdc and Tivo B on hdb I performed the following:

mfsadd -r 4 -x /dev/hdc /dev/hdb

Now I am hoping all this is correct. I want to make this the last time I install the drives in the HD D*Tivo.

There is one last thing I read about when adding a second large drive (my total capacity will be 250gb + 400GB = 650GB)

tpip -1 -s /dev/hd? [/I]

Should I do this in my case?
If so, should the statement be "tpip -1 -s /dev/hdc /dev/hdb" for my dual drive setup? :confused:

[JamieP]

...
There is one last thing I read about when adding a second large drive (my total capacity will be 250gb + 400GB = 650GB)

Should I do this in my case?
If so, should the statement be "tpip -1 -s /dev/hdc /dev/hdb" for my dual drive setup? :confused: If you restored from instantcake, you have a standard size swap and you don't need the tpip step. There are two schools of thought (http://www.tivocommunity.com/tivo-vb/showthread.php?p=3825639&&#post3825639) on the need for additional swap on a Series2.

[sjmaye]

If you restored from instantcake, you have a standard size swap and you don't need the tpip step. There are two schools of thought (http://www.tivocommunity.com/tivo-vb/showthread.php?p=3825639&&#post3825639) on the need for additional swap on a Series2.


Yes, I did restore from instantcake, but I Zippered it immediately thereafter. Does that make a difference?

Something occurred to me while I was out today. Right after Zippering the Tivo A drive without doing any sort of prep to the Tivo B drive I did the mfsadd. I worried that I might have some sort of partition problems. Or is the adding and expanding overwriting any partitions that were on it?

Is there something I should be looking for in partition info to show everything is OK?

So, if all is good and no need for "tpip" then all these problems happened just because I did not use the "-r 4" in the mfsadd?

[sjmaye]

This is a repost of info on the Zipper thread. I thought MFSTools could help.


I did a successful mfsadd on my dual drives using:

mfsadd -r 4 -x /dev/hdc /dev/hdb

After mounting in the HD D*Tivo I got no GSOD. :)

Everything looked good. After about 2 hours the video started stuttering and locking up. I tried rebooting a few times and got no where.

I thought I had maybe done something along the way to mess things up so I decided to start all over (again).

I tried applying the drive image to the 400GB drive. After it completed the restore and was cleaning up it said unsuccessful.

I then tried applying the drive image to the 250GB drive(which was successfully imaged twice before) . Image went on fine, but came back with "not enough space to expand on A drive".


I thought applying a drive image overwrote everything. Seems like when the drives are brand new imaging and everything else works fine.

Is there something I can or should do to prep these drives for imaging?

[Pearldiver]

I'm having issues. I have a Series 2 that I had upgraded to two 120GB drives. After a new channel lineup and perhaps software version had been installed the system was giving me an incorrect channel line up, so I went in to correct it and when I was done it wanted to download the guide info again. No matter what I did, I couldn't get it to finish the process (it would fail after loading just under half the new info) and after talking with a couple of techs at Tivo we did a repair. Now that system is stuck in the Green screen repair loop. I saw on the fourm that this could be caused be a swap partition that is too small. I was able to stick in my old original drive to get back up and running for now in for now.

When I did the original upgrade, I had a friend who is familiar with linux help me, so I'm not sure how to fix this. Can anyone tell me if there is a way to enlarge the swap partition so that it may be able to repair itself? If so can you please give me the command to do it? Or is there something else that may fix the issue?

I'm hoping to get this fixed so that I can recover my recordings. If not I guess I can just start over on the upgraded drives from the original drive that is currently running in the Tivo. Thanks.

[TiVoJimmy]

Can I copy or 'install' the PTV ISO on a spare hard drive to dedicate an old PC to upgrading TIVOs? Does anyone have instructions on how to do so, I am Linux impaired.

Thanks,

Jim

[grins]

Hi folks! Having some trouble with my zippered HR10-250.

I'm going from a single 250 GB to a single 500 GB. I used the weaknees interactive guide to get a backup command, and it told me to use

mfsbackup -Tao - /dev/hdb | mfsrestore -s 300 -r 4 -xzpi - /dev/hda

I'm quite sure of the device letters, even though they're not the norm.

At boot time, the console log shows hda with 500108 MB and 1 partition, and hdb with 251000MB and lots of partitions.

I issue the backup | restore command, and get
Scanning source drive. Please wait a moment
Source drive size is 281 hours
- Upgraded to 283 hours
Uncompressed backup size 211018 megabytes
Restore failed: Backup target not large enough for entire backup by itself.

Any ideas? aTdHvAaNnKcSe :-)

p.s. Sorry for the double post, I also put this in the weaknees thread.

[frankrizzo]

Just want to give props to the Mfs Tools 2.0 programmers and also the Hinsdale-How-To. The process was easy and simple following the How-To...no problems or hiccups at all. I did a nice modest upgrade of my Series 1 DirectTivo (Sony T-60)...originally had 40GB (35hrs) and I added an 80GB drive I had lying around here for a total of 105 hours. I'm a happy camper, especially now that my wife has learned how to record programs! :)

I love my Tivo - it's been going strong for 4 years now...eventually I'll go HD but for now, it's perfect!

[ThreeSoFar]

Hi folks! Having some trouble with my zippered HR10-250.

I'm going from a single 250 GB to a single 500 GB. I used the weaknees interactive guide to get a backup command, and it told me to use

mfsbackup -Tao - /dev/hdb | mfsrestore -s 300 -r 4 -xzpi - /dev/hda

I'm quite sure of the device letters, even though they're not the norm.

At boot time, the console log shows hda with 500108 MB and 1 partition, and hdb with 251000MB and lots of partitions.

I issue the backup | restore command, and get
Scanning source drive. Please wait a moment
Source drive size is 281 hours
- Upgraded to 283 hours
Uncompressed backup size 211018 megabytes
Restore failed: Backup target not large enough for entire backup by itself.

Any ideas? aTdHvAaNnKcSe :-)

p.s. Sorry for the double post, I also put this in the weaknees thread.
You used a swap greater than 127, but I don't see tpip--probably because you didn't get that far, but don't forget it.

I have seen this error before, but given your command and drives' sizes, I'm not sure why this error would come up. Maybe run "fdisk /dev/hda" and use that to delete the one partition on hda, but really that shouldn't matter.

Google "Restore failed: Backup target not large enough" (http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLD,GGLD:2003-45,GGLD:en&q=Restore+failed%3a+Backup+target+not+large+enough)

Some of those links go into it in a bit of detail, not sure if they're helpful. ANd I'd post the URL's except for some reason a lot of those sites show up as "****" instead of a real domain. TCF.com must be broken (or perhaps it is just rude).

[what the!?]

Ok. I'm at about wits end now.

So i'm trying to upgrade my Humax DRT400 from a 40GB to a 400GB drive.

I followed the Hinsdale drive and used the msftools boot cd. My configuration is:

mfsbackup -Tao - /dev/hdb | mfsrestore -s 127 -xzpi - /dev/hda.

After a couple of hours I put it back (i need to save my wife's recordings) into my Tivo and I booted up. I got to the "Almost there..." and it GSOD'd on me and went through an endless loop. Then I read I needed to use the -r 4 switch and a larger swap file.

I then used:

mfsbackup -Tao - /dev/hdb | mfsrestore -s 512 -r 4 -xzpi - /dev/hda

Then I get the same result after placing the drive back into the Humax.

What am I doing wrong? Do I need to reduce the swap file back to 127 or 200? Do I need to use that thing called tpip? If so, what is the command.

Help! My wife is about to kill me! :)

[azitnay]

-s 512 definitely won't work without tpip... Either use tpip as well, or just so -s 127.

Drew

[what the!?]

-s 512 definitely won't work without tpip... Either use tpip as well, or just so -s 127.

Drew

Hi Drew,

Thanks for the quick response. I'm running through it again with this command:

mfsbackup -Tao - /dev/hdb | mfsrestore -s 127 -r 4 -xzpi - /dev/hda

Hopefully this works! My wife just told me, "get it to work by the time Days of Our Lives is on tomorrow, or you're dead meat!" :)

*I'm keeping my fingers crossed*

[azitnay]

If that fails (which it shouldn't), just throw the old drive back in there... No reason to risk bodily harm :).

Drew

[what the!?]

Awesome Drew! It worked for my Humax DRT400! Now...

So I did the same exact thing for my TCD540040 with the same command:

mfsbackup -Tao - /dev/hdb | mfsrestore -s 127 -r 4 -xzpi - /dev/hda

upgrading from a 40gb drive to a 400gb seagate drive and I get the rebooting and GSOD.

Any thoughts?

The Humax DRT400 was a 40gb Seagate drive, and the Tivo TCD540040 drive is a Maxtor (drive wasn't locked as it showed the correct size)

I don't get why it would work for one, but not the other?



If that fails (which it shouldn't), just throw the old drive back in there... No reason to risk bodily harm :).

Drew

[Brillian1080p]

I had an existing 500gb drive and used MFStools 2.0 to add a second 750gb drive. It only took a second and it reported a large amount of recording time.

I put the drives back in the box, it boots up fine, didn't loose any recordings, passes or settings, but info shows only 1 hour available for sd and hd, and here is what TWP info says:

Expired Invisible 4 2960 MB -0.3% 1:13:58
Expired Suggestion 33 68302 MB -7.5% 37:46:07
Expired Season Pass 1 5024 MB -0.6% 0:52:03
Expired Single 1 11760 MB -1.3% 2:02:04
Single 24 150910 MB -16.7% 33:04:31
Season Pass 25 89962 MB -9.9% 18:32:05
Suggestion 23 26639 MB -2.9% 25:43:46
Live Cache 2 1808 MB -0.2% 0:42:24
Used User Space 113 357365 MB -39.5% 119:56:58
Reserved Space
Expired Tivo Clips 3 272 MB 0.0% 0:58:06
Used Reserved Space 3 272 MB 0.0% 0:58:06
Space Summary
Total Space - -905844 MB 100.0% -308:58:02
Total Used 116 357637 MB -39.5% 120:55:04
Total Free - -1263481 MB 139.5% -429:44:50
Deleted** 30 113522 MB -12.5% 38:52:26

Should there be negative numbers? How do I fix this?

[vegaspl]

I had an existing 500gb drive and used MFStools 2.0 to add a second 750gb drive. It only took a second and it reported a large amount of recording time.

I put the drives back in the box, it boots up fine, didn't loose any recordings, passes or settings, but info shows only 1 hour available for sd and hd, and here is what TWP info says:

Expired Invisible 4 2960 MB -0.3% 1:13:58
Expired Suggestion 33 68302 MB -7.5% 37:46:07
Expired Season Pass 1 5024 MB -0.6% 0:52:03
Expired Single 1 11760 MB -1.3% 2:02:04
Single 24 150910 MB -16.7% 33:04:31
Season Pass 25 89962 MB -9.9% 18:32:05
Suggestion 23 26639 MB -2.9% 25:43:46
Live Cache 2 1808 MB -0.2% 0:42:24
Used User Space 113 357365 MB -39.5% 119:56:58
Reserved Space
Expired Tivo Clips 3 272 MB 0.0% 0:58:06
Used Reserved Space 3 272 MB 0.0% 0:58:06
Space Summary
Total Space - -905844 MB 100.0% -308:58:02
Total Used 116 357637 MB -39.5% 120:55:04
Total Free - -1263481 MB 139.5% -429:44:50
Deleted** 30 113522 MB -12.5% 38:52:26

Should there be negative numbers? How do I fix this?

I'm not sure if this is where I respond (kinda) to your thread, but I noticed in your signature you mentioned you had an HR20. I assume that's the same as the
3 HR20 DVR's I'm getting This Saturday from DTV. Is your's upgraded and if so could you direct me and my Tech Friend to the proper site(s). He upgraded all my many Tivo's and I hope he will do the three HR20's coming.
As far as the info you displayed..WOW!!!!. I and many others had been pushing TiVo since way back when I was a Beta Tester for ANY kind of a "Time remaining indicator. I was pleased when I downloaded the HR20's Manual and found that low and Behold it showed a gauge for that, but yours "Tremendous"
If I'm not asking too much could you also send info on how I can get even 1/2 of what you displayed

[Brillian1080p]

The display was from tivowebplus running on the HR10-250. With TWP you open a browser on a PC and type in the network address of your box.

But my problem is I don't think the new 750gb drive is being recognized properly. Everything went smoothly during the add, but I'm not sure these numbers are correct.

[vegaspl]

Thanks for the info but tell me about your HR20 ... DTV DVR? Upgraded? even if No, then any info on Upgrading HR20's would be gratefully received

[Brillian1080p]

My HR20 is stock. There are threads that talk about using Esata drives to increase recording time.

[gary80920]

Hi,

I asked this question over in the " PTVupgrade TiVo Upgrade CD with LBA48 support for Series1 and Select Series2 Units" thread. But was told that I should ask my question here.

I currently have a Series1 running v3.0-01-1-000 with a 120gB drive. I am getting ready to add a 160gB drive to it. And, I have a couple of questions:

If I use one of the traditional non-LBA48 boot CDs, I can just proceed along and the 160gB will only be expanded to the 137gB limit. Correct? I already have the swap file set at 127mB.
If I want to use all of the 160gB, I need to do the following:

boot using a LBA48 compliant CD/kernel
use mfsadd to add/marry the 160gB drive to my existing 120gB drive
use the copykern utility to update the Tivo kernel to be LBA48 compliant


Thanks!