1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Premiere Drive Upgrade Instructions - with all-in-one jmfs Live CD

Discussion in 'TiVo Upgrade Center' started by comer, Sep 20, 2010.

  1. Mar 2, 2011 #741 of 2853
    MikeAndrews

    MikeAndrews Registered abuser

    14,222
    2
    Jan 17, 2002
    Northern...
    I just checked to see which drive in my NAS is the slow one and with a quick copy two different drives in the same enclosure have the problem. I'm not going to believe I have two bad drives. More checking is due.

    But lo! http://ubuntuforums.org/showthread.php?t=1297342&page=2
     
  2. Mar 2, 2011 #742 of 2853
    richsadams

    richsadams Active Member

    8,897
    2
    Jan 4, 2003
    I didn't get through all of the posts on that linked thread as well as another link within one of the posts, but did scan them...is there a consensus as to it being a batch of drives, Intellipark, etc.?

    The WD20EARS I used to upgrade my Premiere XL had a transfer rate of between 39 and 50MBs w/direct SATA/MB connections for both drives. I changed the AAM from 254 to 128 but did not tweak the Intellipark setting on the new drive prior to upgrading.
     
  3. Mar 2, 2011 #743 of 2853
    generaltso

    generaltso Member

    966
    0
    Nov 3, 2003
    Vermont
    I noticed that my stock Premiere XL drive has wdidle set to 8 seconds, but the stock drive from my non-XL Premiere has wdidle set to Disabled. I upgraded both of them to 2TB WD Green AV drives. I set the one in the XL to 5 minutes, and the one in the non-XL to Disabled. It's been about 2 weeks, and the XL has spontaneously rebooted once and hung with a spinning green circle twice. Do you suppose I would be less likely to have these problems if I pull the drive out of the XL again and change wdidle to Disabled?
     
  4. Mar 2, 2011 #744 of 2853
    MikeAndrews

    MikeAndrews Registered abuser

    14,222
    2
    Jan 17, 2002
    Northern...
    So far Googling finds me more than a few discussions of WD drives bogging down to 2Mbps on writes. I see 2mbs bursts followed by 2-3 second dead, dead nothing, lulls.

    I have actual graphic proof...I'll post anon.

    I didn't have a problem prior and these drives are several months old and were performing well right through the end of 2010. As above I need to try some more sleuthing although I've been hacking at it for several weeks.

    I can move the drives to different enclosures.
     
  5. Mar 2, 2011 #745 of 2853
    richsadams

    richsadams Active Member

    8,897
    2
    Jan 4, 2003
    My instincts tell me no, that it shouldn't make any difference one way or another...but then there's really not enough data to say anything for sure one way or another. You certainly could give it a try and see what happens...but only if you report back. ;)
     
  6. Mar 2, 2011 #746 of 2853
    richsadams

    richsadams Active Member

    8,897
    2
    Jan 4, 2003
    Curiouser and curiouser...
     
  7. Mar 2, 2011 #747 of 2853
    generaltso

    generaltso Member

    966
    0
    Nov 3, 2003
    Vermont
    I'll give it a shot. I can't imagine that it would make it any worse.
     
  8. Mar 3, 2011 #748 of 2853
    jbell73

    jbell73 Member

    86
    0
    Oct 31, 2006
    I'm of the mindset that if things are running fine for a while, and suddenly it stops acting "normal", then you have a problem. I fought the slow 2TB WD20EARS for 2 days straight trying every combination I could, and it was just slow. Nothing reported any errors. What I would do is simply RMA one of your drives, while you can still read from them, and copy the data to the new drive you get.

    My new drive worked the first try, without any issues. The same way the old one did when I first set it up. This tells me it can't be anything else than a bad drive.

    Regrettably this is the virgin drive I am copying for the second time. So it will require a visit from Cox to pair the cable cards again. Next time I will pair them with the factory drive, and then copy/clone so the pairing is part of the copied data. The new 2TB drive is up and running (with the new MFS Supersize) @ 317 HR capacity, and quite happy.

    -Jeff
     
  9. Mar 4, 2011 #749 of 2853
    Stuxnet

    Stuxnet Alien Infidel

    356
    0
    Feb 8, 2011
    I had to run WD's Lifeguard diagnostics for Windows and HDDScan to test and set AAM since WD's Lifeguard DOS CD couldn't find my WD20EARS. FWIW, Hiren's BootCD for WD diagnostics and WDIDLE3 also came up empty—I'm not sure if that was because of the USB connection, or because the HDD lacks a partition table.

    Since the drive mfr date is December 2010, I'm not going to bother w/intellipark unless the soft boot issue appears. That all said, will jmfs Live CD detect my Premiere drive and WD20EARS if they're both connected via individual USB/SATA? I'd prefer not to open up my PC to use the SATA cabling... of course if I'm without an alternative I guess I'll do that.
     
  10. Mar 5, 2011 #750 of 2853
    pruffy

    pruffy New Member

    32
    0
    Oct 20, 2003
    What I want todo

    Erase and llf current XL drive in premiere.
    Then take original drive and copy that to former XL drive then expand the drive to its full 2tb potential.

    So this way I would have a 2tb hdd with premiere software so it would now get program guide updates correctly. I don't really care about the shows on the hdd now but if they could be saved that would be neat.

    Haven't messed with any tivos for awhile, if anyone could help that would be great.
     
  11. Mar 7, 2011 #751 of 2853
    Stuxnet

    Stuxnet Alien Infidel

    356
    0
    Feb 8, 2011
    Thank you comer!

    Just upgraded to a WD20EARS... What a voyage. First, it turned out that jmfs couldn't find my drives mounted to a usb dock (strike one). So I tried again from my laptop (strike two). Went back to the desktop and pulled the sata connectors from my HDD and DVD. Ooops... no DVD, so I moved jmfs to a bootable usb thumb drive. Reboot. Found the TiVo HDD, but not the WD20EARS... arrrggghhh... oops... inadvertently pulled the sata connector from the mobo... 3 hours later, finished supersize :)

    Detached the TiVo HDD and reconnected the desktop DVD and set AAM to 128 with the Hitachi tool. Lastly wdidle3... but it wouldn't run from CD... so back to the bootable thumb drive... even though the WD20EARS is dated December 2010, reset intellipark from 8 sec to 300 sec. Installed new drive in Premiere, came up in 6 minutes w/o network... then soft reboot w/network... and (whew) all is well. Now I have to put the desktop pc back together.... Tomorrow, lol.
     
  12. Mar 8, 2011 #752 of 2853
    wesbc

    wesbc New Member

    83
    0
    Mar 16, 2003
    Ok, so I did take the suggestion to disconnecting network and it seems that the freeze / reboot problem went away and when I put in my network cable again, that after sometime freeze / reboot occurs. I did not have this problem with the original drive, so what have changed? More importantly what can be done to fix this?

    Tivo is connected to a wireless router that's bridged to the main router. Have had this setup for sometime and nothing changed recently.
     
  13. Mar 8, 2011 #753 of 2853
    richsadams

    richsadams Active Member

    8,897
    2
    Jan 4, 2003
    Our 2TB upgraded TiVo Premiere XL rebooted and froze two nights ago. It was recording two programs at the time and I accessed Netflix. The screen went black a moment after I clicked on "Netflix" and TiVo rebooted. In addition, once it came back it was completely unresponsive (for a time) to all remote commands. The green menu background appeared once it booted up, but without any text. The amber front panel light blinked each time a button was pressed on the remote, but no activity. I let it sit for about three minutes and tried it again and finally got back to TiVo Central. It's been fine since then but I haven't had time to try Netflix on our TiVo again.

    I ended up accessing Netflix on our Apple TV2 and it worked fine. I also downloaded an HD movie from Amazon VOD to our TiVo the next night and that worked fine (although I did see more macroblocking than normal).

    This and several other network-related problem posts is also making me wonder if there's a connection between upgraded TiVo's using the jmfs program and network induced issues. :confused:
     
  14. Mar 8, 2011 #754 of 2853
    Fofer

    Fofer XenForo Rocks! TCF Club

    82,904
    517
    Oct 29, 2000
    Were you using the HD interface? I have heard it can freeze/reboot with Netflix.

    I am sticking with the SD interface for now. The (incomplete, unstable) HD menus just piss me off. And the SD menus are blazing fast.

    That said, I have had instances where using the iPad app to start a show has "unfrozen" an unresponsive Premiere.
     
  15. Mar 8, 2011 #755 of 2853
    richsadams

    richsadams Active Member

    8,897
    2
    Jan 4, 2003
    I'm right there with you regarding the HD menus. I use SD menus exclusively. I switch to the HD menus now and then just to see if they behave any better than they used to, but get ticked off and go back to the SD menus. :mad:

    This was only the second time the Premiere had an issue since I upgraded a little more than a month ago. At that time I checked the connections and found the HDMI cable a little loose so attributed it to that.

    I'll have to try the iPad app if it freezes up again.
     
  16. Mar 8, 2011 #756 of 2853
    ThreeSoFar

    ThreeSoFar FourNow...WaitFive

    5,419
    0
    May 24, 2002
    Baltimore
    Doing a quick test with Netflix on one of our (jmfs upgraded) Premiere's now.

    Both tuners recording (two red dots), went into Netflix, menu comes up OK.

    Clicked Play on Serenity (HD). Playing fine.
     
  17. Mar 8, 2011 #757 of 2853
    richsadams

    richsadams Active Member

    8,897
    2
    Jan 4, 2003
    Thanks for checking. That's good news. Again, it may be a fluke, but since there are several reports of problems occurring that seemed to be network-oriented it's a bit of a worry, particularly since nothing like that ever happened with the OEM drive. Only time will tell I guess.
     
  18. Mar 9, 2011 #758 of 2853
    richsadams

    richsadams Active Member

    8,897
    2
    Jan 4, 2003
    I finally found time to try and recreate the reboot/freeze on our upgraded (2TB) Premiere XL when using Netflix that I posted about earlier.

    This time I had one recording in progress. From TiVo Central I once again headed to my Netflix Instant Queue. It opened and I was able to start playing back several movies and TV shows without any problem. HOWEVER when I backed out of Netflix and returned to the regular TiVo menus the background was black. I'm still using SD menus so no red, green, blue, etc. backgrounds, just text. Unlike before TiVo responded to the remote commands normally.

    HOWEVER Part II...when I tried playing several recordings the screen remained black. The progress bar showed on the screen initially as normal, but no video. I could FF or RW even, but the counter stayed at :00...nothing.

    I ended up performing a menu restart and TiVo booted back up and then acted normally afterward.

    I tried Netflix again, just as I had before and then backed out to the regular menus, played recordings, etc. and everything performed normally. I even went into other IP source materials including Amazon VOD, YouTube, etc. and all was fine.

    Soooo...I've no idea if this is a Netflix thing, a Premiere thing, an upgraded Premiere thing, a jmfs thing...or what. :confused: I know this never happened with the OEM hard drive. I also know that it's going to stick in the back of my mind now and I do NOT like having to worry if TiVo is going to perform properly or not. :(

    Going forward I'll probably just use our Apple TV2 to watch Netflix (in fact the PQ via the Apple TV is generally better than on the TiVo) but it bothers me that there may be some sort of network problem with TiVo's that have been upgraded using the jmfs program. It may be a coincidence but I've experienced it three times now and there are several other posts about similar issues here as well.

    If anyone runs into anything unusual...be sure to post so we can evaluate what it might be and hopefully figure out how to address it. TIA!
     
  19. Mar 10, 2011 #759 of 2853
    wesbc

    wesbc New Member

    83
    0
    Mar 16, 2003
    My freeze then reboot occurs even when I'm not accessing any network feature which is odd. It's mostly happens while I am watching a recorded show, don't recall if it happens while watching live. The symptom is it'll always freeze, then unfreeze for 2-3 sec, then freeze again follow by a reboot, all the while the tivo would not response to any remote command, no light register on the front panel. Once I caught it where it wouldn't response to the remote and I knew the freeze was coming and it did.

    So far with my bridge router shut off, I have not experience the issue. I'm really baffled by this. Could the supersizing of the drive taken up space that Tivo wants for their ads?
     
  20. Mar 10, 2011 #760 of 2853
    MikeAndrews

    MikeAndrews Registered abuser

    14,222
    2
    Jan 17, 2002
    Northern...
    You guys are running into exactly what I did with my 2TB upgrade. I could also tell the crash/reboot was coming on by drops, stutters, and remote no response.

    Rich, for one thing, the crash after NetFlix abort bug is what TivoJerry says is fixed in the new software update for the Series 3, so it may also be present in the S4TP.

    If there is some problem with the way that jmfs configures a 2TB drive, we need to know how many have been 100% OK.

    I think I had problems only when the new 2TB drive was nearly full with 100s of suggestions after 2-3 weeks of life, and it first made itself known with a network upload. I did get some rare audio drops and pixellation glitches from day 1 but they didn't concern me. I have had few to none since going back to the OEM drive and letting it settle.

    If there a way to view the system log - even if not over the network? Can I find it on the drive itself?

    I'm going to burn in/soak the failed 2TB drive if possible to see if it really is defective.
     

Share This Page