New, working drive but forgot mfsadd!

[Ideasite]

I successfully replaced my factory 40 gig with a Maxtor 120 gig drive. Got everything working, including ethernet, telnet, ftp, etc.

I promptly began using the unit normally and only noticed today that it's only indicating 40 gig capacity.

Re-read (OK, finally read) the entire update proceedure and discovered that I, in my excitement, forgot the last step - returning the drive to the PC and executing the mfsadd command.

Here's my question:

How do I expand the drive to it's full capacity, now that I've been using it?

[Ideasite]

I did this to a Huges HDVR2 using mfsTools2 on a boot CD-ROM. (Really great piece of work - Thanks for this!)

[captain_video]

Put the drive back in your PC and use the mfsadd command per Hoinsdale's How To to expand the capacity to the full size of your new drive.

[Ideasite]

You can't execute mfsadd ona hacked drive. It hangs at "almost there." I had to restore 3.1.1b to the drive, then running Sleeper's ISO.



I ran mfsadd between the RESTORE and the SURGERY steps. Everthing works fine.

[captain_video]

Gotcha. I missed that part about it being a single drive. I thought you were trying to add a 2nd drive to one that was previously hacked. My bad. Sleeper's ISO should run mfsadd automatically as part of the restore phase. If you try to do it after adding the romfs image and the bootpage command it will hose up the hdaXX partition ID you entered during the hacking process since the number of partitions will change due to the extra capacity. Your best option may have been to do as you indicated although I'm puzzled as to why you had to do it at all.

[Ideasite]

Had to because the original 40 gig drive had 3.1.0 on it. I wanted to preserve the original drive and I wanted 3.1.1b on the new 120 gig drive.

So I did a mfsrestore to put 3.1.1b on the 120 gig drive, and then ran Sleeper's iso.

In the process, Sleeper's iso "smells" the original drive and you have to hit "any other key" to get it to leave the -s 127 in the restore step.

Sleeper's script should probably be changed to do the mfsadd command anytime the -s 127 switch is used, rather than basing it on weather it "smells" the original drive. Just a thought.

[Sleeper]

Originally posted by Ideasite
So I did a mfsrestore to put 3.1.1b on the 120 gig drive, and then ran Sleeper's iso.

I am assuming tht you downloaded the 3.1.1b image and mfsrestored it without the scripts to the 120 gig drive.

Exactly what command did you use to do the restore?

After you restored it, you ran the scripts and backed it up again?

Then you restored it again, ran mfsadd and then continued?

I understand why you had to do the mfsadd. The scripts think that the drive is the original tivo drive and removes the -x option and asks about the -s option. This is done because if someone uses their original (40 gig) drive than you must remove those options for it to fit.

[Ideasite]

Before I ran your script, I manually restored 3.1.1b to the new 120 gig drive with mfsrestore -s 127 /mnt/c/31b.mfs /dev/hdc.

I didn't do mfsadd at this point. Instead, I just went right to your script. This is probably why the mfsadd didn't automatically happen.

BTW, thanks for making this whole process one hell of a lot easier. Your script is an ephiphany.