series 1 with 1 400gb drive again

[michaelrj9]

I know this has been asked a million times before but all I can find is bits and pieces of information. have been reading for a while


I know all about the LBA48 that need to be done.


I tried copykern from PTVupgrade LBA48 Boot Disk (version 4.04)
picked kernel (labeled 3.10+ from the menu.
everything seems like it goes fine.

After I ran copykern
I ran mfsadd –x /dev/hdc

All it shows is a total of 147 hours

what could be going on?

But when I put it back into the Tivo It will not get past "welcome powering up" if I restore the backup it works but when I upgrade the kern tivo will not boot up.


What could be going on?

Any help will be greatly appreciated or a link to a post that I may have missed with the same problem

Thanks

Michael

[funtoupgrade]

Your restore command should be:
mfsrestore -s 200 -r 4 -xzpi /mnt/dos/tivo.bak /dev/hd? where ? is the new drive. After the restore is done type mountcd, then run copykern.

[Freightdog]

Your restore command should be:
mfsrestore -s 200 -r 4 -xzpi /mnt/dos/tivo.bak /dev/hd? where ? is the new drive. After the restore is done type mountcd, then run copykern.


Doesn't mfsrestore work correctly with up to -s 127?
I think I read that to use a larger parameter you must execute another command after mfsrestore.

[michaelrj9]

Your restore command should be:
mfsrestore -s 200 -r 4 -xzpi /mnt/dos/tivo.bak /dev/hd? where ? is the new drive. After the restore is done type mountcd, then run copykern.

Thanks for your help. (almost done I hope)

after I did the: mfsrestore -s 200 -r 4 -xzpi /mnt/dos/tivo.bak /dev/hdc

It showed 461 hours (great I thought)

then mount cd
then copykern

BUT the Tivo still gets stuck on the Welcome. Powering up...

Any ideas what I am doing wrong?

Thanks again

Michael

[funtoupgrade]

command mountcd with no spaces - don't know whether this makes any difference or not. Another possibility is that your series one is just too finicky to accept just any larger drive. Others have reported strange problems like this using a different manufacturer's drive of same size.

[mick66]

mfsrestore -s 200 -r 4 -xzpi /mnt/dos/tivo.bak /dev/hd

mfsrestore -s 127 -r 4 -xzpi /mnt/dos/tivo.bak /dev/hd

Unless you you use -s 200 and then use tpip, you probably don't have any swap space at all. I'd leave it at 127

[buddhawood]

mfsrestore -s 127 -r 4 -xzpi /mnt/dos/tivo.bak /dev/hd

Unless you you use -s 200 and then use tpip, you probably don't have any swap space at all. I'd leave it at 127

I think copykern has tpip built in the function and running it separately is not necessary