Hichhiker
08-06-2006, 01:47 PM
Well, the my out-of-date knowledge strikes again. I am about to embark on yet another upgrade, upgrading S2 Dtivo (6.x zippered) to a 320GB hard drive. I have done many upgrades for myself, family and friends, and I am generally pretty comfortable with Linux and Tivo upgrade processes, however to date I have never dealt with the really large drives (over 160GB) and from many readings here I recall there was an issue with swap partition size over 127mb. And that drives over a certain size (somewhere around 300GB) need larger swap space. Unfortunately while I recall seeing a lot of info, I was not paying attention to it and searching the forums now results in a lot of uncertain and irrelevant info :-/
So I figured I'd ask what I wanted to find out :
* What is the proper way to calculate the swap requirements (not that blindly assigning 500+MB to swap is a big loss of space on 320GB drive, but I hate doing things blindly)
* How to create a swap partition over 127mb
* How to allow Tivo Kernel to USE full swap space if it is over 127mb
* Do I need to change the Kernel for above if I am alreay running a zippered dtivo.
* Anything else I should know before I do this? I am keeping recordings and would prefer to do this only once :-)
From searching the forum, I gathered:
* 6.x Software already includes LBA48 Kernel
* You must use an upgrade CD which supports large hard drives (LBA48).
* S2 units can be expanded only once. So if you already upgraded the size of hard drive once, you cannot simply expand it again without loosing the recordings. If I remember correctly, S1 units could be expanded a few times, but have a similar limitation in the end.
* mfstools will create a swap partition over 127mb without a problem with -s # command
* TPIP command (http://www.courtesan.com/tivo/tpip.html) will fix the kernel to use the larger swap space. Syntax seems to depend on version of tpip.
* It has been suggested in this thread to use 1mb of swap per 1GB of space rule of thumb i.e. 320MB for a 320GB hard drive. Alternatively people suggest 1mb per 2gb. Latter seems to jive better with other posts I've seen suggesting that problems with swap of 127 start with hard drives in about 300GB range (2x127=254 and since most drives are either 250gb or 300gb it would make sense that 300gb is the cut off range) Of course these are rough rounded estimates so real world numbers would be a bit off. Its always better or over estimate than underestimate here.
Is this correct and am I missing any details?
So in the end:
using PTVUpdate's CD (with tpip version 1.2)
with original drive connected to Pri master (/dev/hda)
and new drive connected to Pri slave (/dev/hdb)
Creating swap space of 320mb
# mfsbackup -Tao - /dev/hda | mfsrestore -r 4 -s 320 -xzpi - /dev/hdb
# tpip -s /dev/hdb
And thats all. Don't forget "-r 4", otherwise bad things happen (as in BSOG loop)
Thanks
-HH
So I figured I'd ask what I wanted to find out :
* What is the proper way to calculate the swap requirements (not that blindly assigning 500+MB to swap is a big loss of space on 320GB drive, but I hate doing things blindly)
* How to create a swap partition over 127mb
* How to allow Tivo Kernel to USE full swap space if it is over 127mb
* Do I need to change the Kernel for above if I am alreay running a zippered dtivo.
* Anything else I should know before I do this? I am keeping recordings and would prefer to do this only once :-)
From searching the forum, I gathered:
* 6.x Software already includes LBA48 Kernel
* You must use an upgrade CD which supports large hard drives (LBA48).
* S2 units can be expanded only once. So if you already upgraded the size of hard drive once, you cannot simply expand it again without loosing the recordings. If I remember correctly, S1 units could be expanded a few times, but have a similar limitation in the end.
* mfstools will create a swap partition over 127mb without a problem with -s # command
* TPIP command (http://www.courtesan.com/tivo/tpip.html) will fix the kernel to use the larger swap space. Syntax seems to depend on version of tpip.
* It has been suggested in this thread to use 1mb of swap per 1GB of space rule of thumb i.e. 320MB for a 320GB hard drive. Alternatively people suggest 1mb per 2gb. Latter seems to jive better with other posts I've seen suggesting that problems with swap of 127 start with hard drives in about 300GB range (2x127=254 and since most drives are either 250gb or 300gb it would make sense that 300gb is the cut off range) Of course these are rough rounded estimates so real world numbers would be a bit off. Its always better or over estimate than underestimate here.
Is this correct and am I missing any details?
So in the end:
using PTVUpdate's CD (with tpip version 1.2)
with original drive connected to Pri master (/dev/hda)
and new drive connected to Pri slave (/dev/hdb)
Creating swap space of 320mb
# mfsbackup -Tao - /dev/hda | mfsrestore -r 4 -s 320 -xzpi - /dev/hdb
# tpip -s /dev/hdb
And thats all. Don't forget "-r 4", otherwise bad things happen (as in BSOG loop)
Thanks
-HH