Separate names with a comma.
Discussion in 'TiVo Series3 HDTV DVRs' started by tcfcameron, Aug 11, 2010.
Post retracted due to NDA and other contractual obligations.
Seriously? 10 duplicate posts and a new thread?
I was thinking the same thing. He must be on a mission.
And, oddly enough, his posts/replies don't benefit the community, yet he doesn't use PM.
It's probably quite good for the community to keep the image in circulation among people who will be willing to share it with others; it'd be a shame to let it just disappear.
My aploogies for all the duplicity. But, please, at least take into consideration that I just registered with TCF a few days ago & that there are MINIMUM post requirements here when you are new. The forums wouldn't let me do squat without 5 posts, then another 5 to gain more functionality, and I think another 5 more to become a fully functional member.
My duplicity was born more from getting those initial posts out of the way than anything else. If it weren't for that, I'd have posted in a maximum of three of most appropriate existing threads I could find.
How could I use PM, when the instructions from the OP (author of the hybrid image) were to put out a public request, and wait for somebody to PM back? Full send/receive PMing requires 10 posts when you are newly registered here.
I promise that once somebody PMs me the image, or how to get it, that I will go back and delete every single duplicious post (once I verify it is the real deal). If say, a week or two at most goes by with no luck, I'll delete them as well. Then, my minimum posts are done and over with, and I will use much better discretion. I promise everybody that will be the case.
It did not disappear.
Geeze, it is a shame when 157 hours from 1TB is just not enough!
Can someone please post the MD5 of the Broflovski TivoHD image so I know the file is correct? Thanks
You do know you don't need it anymore, right?
An 11.0.k or higher OS Tivo can now be upgraded to 2TB via WinMFS
ciper's not exactly brand new here, so I'm thinking he must be going through a masochistic phase or something to want to mess with it.
Unless getting a 2TB TiVo working isn't the end goal, or he's hoping to rescue recordings by repairing a drive already running that image with a hex editor or something.
I became recently aware of that step forward.
The partition size limit may have been removed but not the partition number limit. In other words you are still limited to a single expansion of the internal drive.
(at least without hex editing the partition table)
Using the hybrid image lets you start from a 1tb internal drive, then expand to a 2tb internal drive later on.
Lastly, call me old fashioned but I don't trust Tivo to implement this change properly so on the slim chance there is some weird bug that could pop up, I prefer to stay within the old boundaries.
It turns out that WinMFS can, for example, take a 648 image or 652 image and "up" it to a 1TB drive by adding partitions 14 and 15, and then take that 1TB drive and copy it to a 2TB drive, and then, *as a separate step*, expand partition 15 into the other 1TB.
First you click on mfscopy, and when it finishes and offers to expand, tell it no, then you should probably click on mfsinfo to make sure everything's okay, then you can click on mfsadd as a separate step to expand partition 15.
I think if you do mfscopy and then accept the offer to expand, it acts like it did, but actually didn't.
Note that this requires the TiVo to be running, I think, 11.0k or later--I'm not familiar with any versions earlier than k.
The partition number limit is not removed, but there is no requirement that MFS zones (which is really what TiVo cares about) maps 1-to-1 to partitions. You can basically add another MFS zone at the end of a drive and have partition 15 (from the previously expanded drive) expanded to include the new zone. So the MFS media zone partition 15 encompasses both the original and newly create MFS zones. 1 entry in the apple partition map, but multiple media zones added to TiVo.
To accomplish this do what unitron suggested.
as a pre-check, make sure the drive or image you are using is 11.0k or 11.0m, if not, upgrade first
mfscopy 1TB drive to 2TB drive, choose 1024mb for swap, do not expand to fill space
mfsadd (run as separate step), choose to ignore the 1TB limitation
mfs super size
This will result in a partition 15 that encompasses both the original and new MFS zones and your 2TB will be fully utilized. I just performed this a month ago on a dying previously expanded 750GB drive and expanded the second time onto a 2TB drive.
If you're a member of some strange religious cult that requires you to go from 1TB to 2TB by adding partitions instead of embiggening partition 15, the most recent version of jmfs, which I think is 1.04, can take that 1TB and copy it to the 2TB drive and add a single partition (thus using up the allowed number of 16) in the extra space, provided you don't have a little extra on the end of the 1TB that's been marked as an Apple Free partition.
That's on the HD, not the original S3.
I did one 652 that way over a year ago and it still works fine.
(I did a 2TB on a 648 with WinMFS and a really big partition 15, and it's working fine as well)
jmfs was designed to work with Premiere drives, but TiVo changed something in the HD from the previous drives that lets jmfs work with HD (and I guess HD XL) drives as well.
If you went from the 160GB to the 1TB with WinMFS, you shouldn't have an Apple Free partition, but if you used MFS Live, you might, in which case jmfs will work but the partition it adds will be #17, and the HD will see that as a screwed up external drive and want to remove it, and you'll be back to the 1TB image on the 2TB drive and the extra space will be unavailable.
unitron and sfhub: Very useful information. I knew there was no requirement for the partitions to be added in pairs, but I did not know Winmfs was able to do it. I'm surprised it works since Winmfs has not been updated since 2008 and Spike specifically said he would not enable the functionality of adding single partitions!
Edit: Please read a few posts in this link http://www.mfslive.org/forums/viewtopic.php?f=11&t=257&start=106
Sfhub is the large swap partition required for this expansion or just best practice to enable green screens to finish on the large drivespace?
I am planning to run a 2tb hybrid ssd. I am waiting for it to ship and in the meantime I will be running with a single 1tb drive. With this new information... I may be able to recover my huge season pass list from the paired 1tb drives that were being removed! Thanks to both of you for giving me a few more things to consider
Well technically he hasn't added adding single partitions. He has coalesced multiple zones into a single existing partition, but the existing partition is still part of its original app/media partition pair. There is no dangling unpaired 4th mfs media region partition.
Also, so there is no confusion, this behavior only happens if you run a separate mfsadd step. It won't occur if you choose the expand option during the mfscopy.
W/r/t swap space some people were complaining they have trouble doiwnloading large guide data with smaller swap and also with larger disks you tend to have more season passes to process, so I figured it just wasn't worth the effort to investigate whether those claims were true.
It was trivial to expand swap during the copy which I needed to do anyway and sacrificing 1sd hour of recording out of 2776 was a no-brainer
That makes more sense. I wonder then, could we now keep the original 160gb A drive and expand an "external" 2gb drive thus getting ~360 hours and an unmodified looking unit?
Dunno, might be possible on s3 HD with mfs64, but I have no idea on if there are drive model restrictions for the expansion drive as I have never tried an external expansion.
I know 2tb expansion won't work on OLED s3 because it is still stuck with mfs32 which limits TiVo's total MFS regions to 2tb, and 2tb external + 250mb internal would violate that limitation.
I thought it was 2TiB or 2.308TB which should still work for the OLED S3
I was playing loose with the binary/decimal so maybe you are right and it is just on the edge of fitting 2TB and 250MB into the 2TiB MFS32 limit.
Try it out and let us know.