
Originally Posted by
Soapm
I came home determined today and I believe I came to some solid conclusions...
TivoHD/Premier have a different partition table than the other Tivo's (duh).
I can't speak from experience on the Premier. Maybe Jamie or Omikron can chime in a bit more on that platform, but it is definitely not true of the TiVoHD. I don't think it is true of the Premier.

Originally Posted by
Soapm
And, the tools used for other Tivo's don't work well with the HD/Premier partitions.
Again, I can't speak to the Premier, but I guarantee that is not the case with the THD. That is not to say those platforms (or even the S3) cannot make use of a scheme that is not supported under the traditional tools. Indeed, we know for a fact this is not the case, since the S3 - unhacked - can support a 2T drive, which is not possible with traditional tools. A hacked S3 can make use of a 2T drive using traditional tools, as well.

Originally Posted by
Soapm
Some tools kind of work but they fail when it comes to accessing the drive.
I guarantee you that a stock THD drive, or one expanded by WinMFS or MFS_Tools can be accessed by a PC running Linux. MFS_Live should work, and has been reported to do so, but I cannot confirm personally that it works on anything other than an S3 with a stock drive, because I have never used it on anything else.

Originally Posted by
Soapm
When I pdisk, fdisk, cat, dd the HD image created by jfms I get block 14 and drive doesn't exist or the partitions isn't valid errors. This is both with mfslive and PTV.
I don't know the details of what jmfs does, but a guess would be it converts the 32 bit Apple partition map into a 64 bit map. This would certainly explain the issues you are seeing. I suggest you not start with a partition map modified by jmfs. Perform your hacks first and get them all working, then try jmfs. That should work. An even better choice may be WinMFS. With a hacked kernel, it can create partitions larger than 1T

Originally Posted by
Soapm
However, If I load the HD drive with WinMFS then all the above work just fine.
WinMFS does not load the drive. It merely reads the partition map and copies over the structure of each partition. It doesn't have to be able to read the contents.

Originally Posted by
Soapm
The problem with this is I ended up with reboots every 20 minutes once the drive got over 300 gigs full (began using the 1.7T partition).
That makes sense.

Originally Posted by
Soapm
So I tried using knoppix thinking I would be more in a linux environment.
What kernel version? Is this another live CD?

Originally Posted by
Soapm
If I can just figure out a way to dd in Jamies kernel and the author file I could at least begin working from the Tivo itself. The question then becomes will busybox or wolfs all in one work with this foreign set of partitions...
Again, I suggest you try might try hacking an ordinary TiVo drive and get that working, then apply the jmfs upgrade. Unless jmfs inserts its own kernel (very unlikely), then your hacks should still work. A better solution, I think, is to use Jamie's hack that allows partitions larger than 1.1T. Then you can just use WinMFS to expand the drive. Either way, hack first, then expand.

Originally Posted by
Soapm
I am considering using the 1TB drive from my S2DT knowing that a WinMFS created image will work fine so I should be able to get her up and running. I just really had my heart set on having a 2TB TivoHD but I guess my skills will have to greatly improve before I can leap that fence...
Not so much, really. I do suggest, however, that before you go too much further you consider whether you want to implement mike_s' scripted upgrades methods. Not only does his method allow for in-situ upgrades, but it also allows an easy recovery if /var gets wiped, which can happen from time to time. It also allows for a larger / and /var, making space for more applications and for backup files. Before attempting to implement his partition changes, I would say it is just about mandatory to use a regular Linux boot. I highly recommend it in any case, but trying to hand copy and update a partition map without dual windows (one showing the existing map and the other creating the map) would be an exercise in total frustration. It's not that creating a partition using pdisk is difficult, but errors are extremely easy, and without the ability to cut-and-paste... well, I certainly would not like to try transcribing all those long strings of numbers with no commas by hand. I made enough mistakes even with cut-and-paste.

Originally Posted by
Soapm
My next attempt will be creating a drive using [URL="puffdaddy" http://www.dealdatabase.com/forum/showthread.php?63369-Extending-MFS-Tools-For-the-TiVo-Premiere-%28Support-Thread%29&p=308364[/url] tools to create the image and try jfms to expand it out. I don't know about all that deleting partitions and stuff but hopefully that was optional and not required. I figure using his tools would allow me to hack the drive then I can begin filling her up and see what happens.
OK, you are asking my advice, so I will give it again. I think you are headed in the wrong direction. I suggest you create a small Linux boot. I like Debian, but Ubuntu will work, and so should any other Linux distro with a 2.6.26 kernel or newer. Take a stock TiVo image and either work from it or else create a new partition map by hand using pdisk. Doing so, you can create a partition map that looks something like this:
Code:
HD_LivingRoom:/# pdisk -l /dev/hda
stat: mode = 060660, type=Block
size = 0, blocks = 0
HDIO_GETGEO: heads=255, sectors=63, cylinders=51329, start=0, total=824600385
Partition map (with 512 byte blocks) on '/dev/hda'
#: type name length base ( size )
1: Apple_partition_map Apple 63 @ 1 ( 31.5K)
2: Ext2 Hack 1 524288 @ 64 ( 256.0M)
3: Image Kernel 1 8192 @ 524352 ( 4.0M)
4: Ext2 Root 1 524288 @ 532544 ( 256.0M)
5: Ext2 Hack 2 524288 @ 1056832 ( 256.0M)
6: Image Kernel 2 8192 @ 1581120 ( 4.0M)
7: Ext2 Root 2 524288 @ 1589312 ( 256.0M)
8: Swap Linux Swap 262144 @ 2113600 ( 128.0M)
9: Ext2 /var 524288 @ 2375744 ( 256.0M)
10: MFS MFS application region 589824 @ 2900032 ( 288.0M)
11: MFS MFS media region 216747008 @ 3489856 ( 103.3G)
12: MFS Second MFS application region 589824 @ 220236864 ( 288.0M)
13: MFS Second MFS media region 268617728 @ 220826688 ( 128.0G)
14: MFS Third MFS applicatioon region 4096 @ 489444416 ( 2.0M)
15: MFS Third MFS media region 1465144320 @ 489448512 ( 698.6G)
16: Apple_Free Extra 975684336 @ 1954592832 ( 465.2G)
minus partitions 14 and 15, and of course with much more free. Note the increased sizes for partitions 2, 4, 5, 7, and 9. You can insert Jamie's kernel into both partitions 3 and 6 using dd. After creating the file systems on partitions 2, 4, 5, 7 , and 9 using mkfs, you can mount them and copy all the same data into partitions 4 and 7 to allow for easy recovery during the process using cp. If you decide to go this route - it really isn't difficult - we can guide you with help on the syntax. I might be available this weekend for phone support.
In either case, once you have all the hacks working, then you can try applying WinMFS or jmfs to expand. If you have a somewhat smaller drive - say 300G - you can get all the hacks onto it and then expand to a 2T drive using one of the expansion tools.
By the way, here is the partition map of my TiVoHD:
Code:
TiVo_HD:/# pdisk -l /dev/hda
stat: mode = 060660, type=Block
size = 0, blocks = 0
HDIO_GETGEO: heads=255, sectors=63, cylinders=56065, start=0, total=900684225
Partition map (with 512 byte blocks) on '/dev/hda'
#: type name length base ( size )
1: Apple_partition_map Apple 63 @ 1 ( 31.5K)
2: Ext2 Hack 1 524288 @ 64 ( 256.0M)
3: Image Kernel 1 8192 @ 524352 ( 4.0M)
4: Ext2 Root 1 524288 @ 532544 ( 256.0M)
5: Ext2 Hack 2 524288 @ 1056832 ( 256.0M)
6: Image Kernel 2 8192 @ 1581120 ( 4.0M)
7: Ext2 Root 2 524288 @ 1589312 ( 256.0M)
8: Swap Linux swap 262144 @ 2113600 ( 128.0M)
9: Ext2 /var 524288 @ 2375744 ( 256.0M)
10: MFS MFS application region 589824 @ 2900032 ( 288.0M)
11: MFS MFS media region 137630712 @ 3489856 ( 65.6G)
12: MFS MFS application region 2 589824 @ 141120568 ( 288.0M)
13: MFS MFS media region 2 171919990 @ 141710392 ( 81.9G)
14: MFS MFS App by Winmfs 2048 @ 313630382 ( 1.0M)
15: MFS MFS Expanded by Winmfs 1639874560 @ 313632430 ( 781.9G)