No add. capacity after 750GB upgrade w/ Instantcake

[uncleakamai]

I recently purchased the Tivo Series 3 version of Instantcake from dvrupgrade.com along with various other tools needed for the upgrade. I purchased a 750 GB drive to replace my failed stock drive. I followed the instructions and after 3.5 hours I received an error message:

mfs_load_zone_map: Primary zone map corrupt, loading backup

New estimated standalone size: 881 hours (599 more)

The "automated" process was complete. I placed the new drive into my S3 and of low and behold IM STILL AT STOCK CAPACITY. The tivo still thinks I have a stock drive in the system. I even upgraded the software version on the box to 9.2/9.3 and still have no additional capacity. I've now tried the same procedure twice.

My next step was to boot into the drive using MFStools. I then ran mfsinfo /dev/sda and got the following output:

/dev/sda10
MFS Partition Size: 288 MiB
/dev/sda11
MFS Partition Size: 105833 MiB
/dev/sda12
MFS Partition Size: 288 MiB
/dev/sda13
MFS Partition Size: 131161 MiB
Total MFS volume size: 237570 MiB
Esimated hours in a standalone Tivo: 282
This MFS volume may be expanded 4 more times


Perfect right? Maybe not...when I run:

mfsadd -r 4 -x /dev/sda

I get:

***?: No such file or directory
***?: No such file or directory
Current estimated standalone sieze: 282 hours
Nothing to add!

I've tried using multipliers of 1, 2, and 3 and I get the same result. Where am I going wrong?

FYI...I posted the same information here. (http://www.tivocommunity.com/tivo-vb/showthread.php?t=389153)

[uncleakamai]

Did a little more digging into this "instantcake" product. There are basically two bash scripts that are the meat of the application:

PTVBAKE and PTVBAKE_

The Tivo software image on the CD is named "000001" and is used as the source install.

The first script runs the Novice setup while the second runs Advanced. In Novice mode the command that is actually executing my install is this line:

/mfstools-2.0/mfstool restore -x -r4 -s $SWAP -zi /cdrom/.images/$PTVimg /dev/$PTVupgradeA

If I were to run the script in Advanced mode, this command would be run:

mfstool restore -x -s $SWAP -r4 -zi $RESTORE_IMAGE_CLASSIC /dev/$PTVupgradeA

Aside from the variable names both commands are identical. Why is this not working?

[uncleakamai]

Still no ideas on my end. I could copy the image from the instantcake DVD and run my own mfstools. Any other ideas?? Bueller?

[uncleakamai]

PROBLEM SOLVED...

Basically the version of instantcake that I received did not work. For whatever reason it did not expand the image onto my drive.

I'm hoping that I am the only one that had this issue and it isn't a symptom of an old version of the software.

So how did I solve the issue?...

1. Hook drive up to PC using IDE to SATA converter as Secondary Master. I don't think this really mattered since I was booting into windows and not relying on a linux live cd to enumerate my drives

2. Download and run the latest BETA of WinMFS.

3. Backup the existing image.

4. Restore backed up image and click OK to expand image onto drive.

What a concept...Its amazing when something works as designed. I'll post more details later.

WOOHOO!!!

[Lou Jacob]

Did you not have your SATA drive connected with an IDE to SATA converter when using InstantCake? IE. What device was your target drive configured as when you were using InstantCake?

[uncleakamai]

I did indeed use the IDE to SATA converter that I purchased from you folks. My target drive was configured as the secondary master. I can't remember if it was hda/hdb or hdc, but I went over it multiple times and even tried the advanced configuration where you specifiy which drive is which.

[Lou Jacob]

I did indeed use the IDE to SATA converter that I purchased from you folks. My target drive was configured as the secondary master. I can't remember if it was hda/hdb or hdc, but I went over it multiple times and even tried the advanced configuration where you specifiy which drive is which.

Seems odd that it didn't work but without more specifics, it is difficult to say. I know that it works fine on all the PC's here and I've not heard of any problems where the software imaged the drive, but did not expand.

My only recommendation would be to have tried on a different PC or perhaps attempted some adjustments to the firmware of your particular PC (like turn off firmware discovery of drives from AUTO, to OFF) as PC behavior can vary from model to model...