Separate names with a comma.
Discussion in 'TiVo Upgrade Center' started by Tivoitis, Jan 4, 2011.
What's the model number?
First, make sure the problem is the drive and not the power supply or the motherboard.
When you say HD, do you mean a TCD652160?
I can provide an image for that model (and a few others).
It was actually 11.0h that began the support (there was no 11.0i version, to avoid confusion). It got put in because WD was already launching DVR expansion drives that would have not worked without the change. So WD deserves some thanks for pretty much forcing TiVo's hand, by getting those out so quickly. I cannot elaborate further, as I am bound by a NDA that is stricter than the first two rules of Fight Club, and I'd rather get beat up by Tyler Durden, than face the broad scope of penalties the other can inflict.
Oddly enough, DVR_DUDE, ships 2TB drives for the HD & Premiere, that come with the prior-to-current factory-installed images, which are several major release revision numbers old, like version 9.___ for the HD and 14.___ for the Premiere. The Premiere upgrade also maps out like JMFS does, with one huge partition at the end of all the factory ones... I haven't been able to analyze the HD partition structure. The software version matter is explained as being necessary to insure that the user doesn't become unable to receive future upgrades. I don't buy most of what his scare-tactic invoking and myth-perpetuating advertising says. However, he keeps an unbelievably great customer satisfaction rating, which is why I bought one of each drive, out of curiosity, and then decided to keep them as they were, and use GNU dd_rescue, from the command line, to clone them to other new 2TB drives for testing. So far, so good. It's only annoying if you lose all your season passes and programs, the Season Passes can't be retrieved from a simple TiVo service connection, like you can if you don't require a software update first.
I have NOT had good luck (TiVo uptime before a GSOD reboot loop), just tacking one huge partition onto the end of a stock TiVo HD drive with JMFS. This issue has been reported time and time again by others, all over the forums, but it's seldom followed by much, if any, response. My best guess is that it all depends on the parameters of how the unit is used. If you have 100+ Season Passes, and the TiVo is always very busy, and never manually rebooted, it doesn't seem to take long for a TiVo HD to turn from "successfully upgraded" to "stuck in GSOD reboot loop". I had the same issues with every 2TB THD upgrade method before JMFS, as well.
My TCD652160 is acting up too. It was rebooting often, can still get through the whole boot process, but ends up stuck at a 480 gray screen with no text within a day.
The drive did pass all the Tivo SMART diagnostics, so I'm not 100% that it is the drive, but replacing the drive to me seems like an easier first step than trying to rule out other issues.
I don't have an image for the TCD652160 and can't trust the original drive. Any pointers on downloading a clean image would be very helpful.
Never mind. I got a unit off of craigslist for $35, the hard drive transplant was successful. Worst of it was re-activating the cablecard.
I just received a shipment of six WD20EADS-00S2B0 HARCHV2AA 2TB Western Digital hard drives, as replacements for some degraded/defective ones I sent back. They're factory recertified replacements, still sealed.
PM me if you'd like to make me an offer. If you'd like, I could pre-image them for either TiVo HD, or 2-tuner Premiere. I don't need them, because I already bought EURS AV-GP replacements, when Newegg had them on special.
I know some don't like/trust 4K drives, so I figured these 512-byte sector ones may be of interest to some of you.
So, to clarify, if my stock TivoHD is already running the latest software (11.0k?)
I can just use winmfs (not jmfs) to backup a truncated image (I don't care about shows) and then restore to a 2TB WD AV-GP EURS?
If so, do I just turn on supersize for the restored drive to get the full 318 hours?
(still confused - IIRC, winmfs by itself will only expand to 1.126GB even on a 2TB drive for the TivoHD)
Using jmfs to expand it should get you 99% of the available drive space. Supersizing it just gets the last few hundred meg that TiVo normally dedicates to the gold star ads.
It's far more than "the last few hundred meg". The default is about 10% of the drive. Supersizing reduces it quite a bit. On a 2TB drive, that means @17 additional HD hours of recording capacity.
Yes. After restoring the image do not expand. Then go to MFSADD and expand followed by supersize.
Just make sure you let WinMFS expand past 1TB when it asks you.
My bad. If we're truly talking about 17 hours of HD to record 20 minutes of infomercials I stand corrected.
Perhaps there was a time when it wouldn't go beyond 1.2, but now it just makes you check (or uncheck) an extra box.
Use WinMFS to mfscopy your current drive, shows, settings, and all, to the 20EURS.
When it finishes, it'll say something about extra space (unless your current drive is also a 2TB), and do you want to expand.
Tell it no.
I don't know why you need to do it that way, but that's the way that seems to work.
After you tell it no, select the new drive, the 20EURS, and click on mfsinfo just to make sure everything looks alright.
The partition map will probably show a large Apple Free partition at the end.
Close mfsinfo, and then click on mfsadd.
You should get the "do you want to use a partition bigger than 1.2TB" warning--tell it yes you do want to.
If you'd like to err on the side of caution, you could copy the current drive to the new one with WinMFS, check the new one with mfsinfo, then close out WinMFS, shut down the computer, disconnect the current TiVo drive, leaving just the new 2TB one hooked up, and start the PC and go back into Windows and WinMFS and then do the mfsadd.
Apparently it's the having 11.0k that lets the TiVo use a bigger than 1.2TB partition.
You can use that same method, running WinMFS, to stick a 2TB in an original S3 (the OLED version that jmfs couldn't do anything for), as long as it's running 11.0k
if i don't expand the new drive after mfscopy then winmfs sees the 2tb drive as a 160GB tivo 'series 2 or 3' drive, and mfsadd doesn't work.
ill try the mfslive cd next.
You can try to expand after copy. In my experience it hangs when I have tried that. Normally what happens is that a large Apple_Free partition is made taking up all the space after you copy and tell it not to expand. When you then go into MFSAdd, it converts the Apple_Free partition to two partitions - MFS app and MFS media. Could you post the MFSInfo output. Might be able to see what is going on. Also shut down WinMFS and only connect the 2TB drive and restart WinMFS. Make sure it is not confusing your original 160gb drive and your 2TB drive.
Got it to work!
Used mfscopy, wandered away, after copy finished WindowsXP downloaded an update and restarted automatically.
Relaunched winmfs, made sure supersize was on, and opened mfsadd.
Chose "no" when asked if I wanted to limit it to 1TB.
Got all 318 HD hours on the 2TB drive.
Just to add another datapoint (and resurrect this thread from the dead), I upgraded my other Tivo HD using JMFS as I did here:http://www.tivocommunity.com/tivo-vb/showthread.php?t=462179&page=8
the 500gig My DVR expander had gone south (or a least things got better when I divorced the drive), and the original 160gig was OK for a while but also started to get flakey (recordings would get weird, and sometimes wouldn't transfer) so I snagged another 20EURS and upgraded it as well. So far so good (the new drive has been in about a week.
Just providing another datapoint, this time with an Australian perspective.
Short story. Just upgraded from a 1TB to a 2TB on a TiVo TCD663160 (Australian TiVo HD).
Used WinMFS Beta9_3g which is apparently the Aussie compatible version.
Just loaded up the 1TB, copied it to the 2TB, with 1000MB swap, then said no to expand, then MFSAdd and extended the partion.
Seems good. I think.
The long store is my original July 2008 TiVo 160 was originally upgraded to 1TB with WinMFS. Then when we could finally add a second TB as an external I did that too.
Later the HDMI port went on the fritz. Was still able to get a signal by tickling it just so...
About 3 months ago, the HDMI port went totally. Fell back to using the Component, it was not perfect... would flicker.
3 weeks ago AV and component both died.
Bought a replacement second hand unit with good HDMI. This was an August 2008 TiVo.
Tried just connecting up the original 1TB internal harddrive (what the hell), well you know how that ended... C&DE, and then separate the external... and you know what. it seemed to work.
Still getting random reboots...
Swapped powersupplies... still getting random reboots...
Ordered the 2TB, I decided I wanted to increase the swap size as before I managed to get the TiVo in a situation where it wouldn't update the guide info when I had 275+ season passes and was only able to resolve it by removing season passes back below 100.
Anyway, truncated backups crashed it... Would just continually ask for the external to be removed.
Eventually decided eff-it, and started up JMFS. It was copying over 1TB of blank recordings, since I only had a few hours recorded by this stage, but having all the season passes makes it feel like my TiVo
After it had done 55GB... I decided... eff this... I'm going to just do the WinMFS copy.
Which only took about 5-10 minutes, and then the expand.
Seems to be working now...
So, in conclusion, is it okay to take a 160GB->1TB, and expand it to 2TB while increasing the swap with WinMFS these days?
It turns out that you can upgrade a Series 1, 2, or 3 original drive to a larger one, which adds a 3rd MFS pair of partitions, and then if you decide you want an even larger drive (limit seems to be 1TB for S1s and S2s, and 2TB for S3s running a version of the TiVo operating software from within about the last 5 or so years, 11.0h here in the states), WinMFS will do it by copying the bigger drive to the even bigger than that drive, and then expand not by adding another MFS pair (which exceeds the allowable limit of 16 partitions per drive), but by expanding that 3rd MFS Media partition.
Which I find very clever on spike's part to have written it that way, and for which I'm grateful.
And that means that it's not necessary to use jmfs on an S3 at all.