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. Jan 29, 2011 #601 of 2843
    Gregor

    Gregor Active Member

    46,740
    14
    Feb 18, 2002
    I think the speed is going to be dependent on the slowest connection, ie the USB.

    I used 2 USB SATA adapters on my Macbook Pro and the copy took 10-12 hours, with a full 320 GB drive. I'll be upgrading the Woot Premiere sometime after Wed when I get the cablecard, and it will be empty when I copy it, so it should take a lot less time.

    In any case, I'm going to do that copy on an old windows laptop that I can let run for awhile.
     
  2. Jan 29, 2011 #602 of 2843
    richsadams

    richsadams Active Member

    8,893
    2
    Jan 4, 2003
    It's not a truncated copy so the time is dependent on the size of the drive (and the transfer speed), not data content. In other words, it doesn't matter if the drive is empty or full.
     
  3. Jan 30, 2011 #603 of 2843
    Gregor

    Gregor Active Member

    46,740
    14
    Feb 18, 2002
    Thanks, Rich, I'll plan accordingly!
     
  4. Jan 31, 2011 #604 of 2843
    comer

    comer New Member

    267
    0
    Aug 7, 2003
    I think Tivo looks for a specific ID string to enable eSata device. Unless someone can reprogram firmware in the enclosure, there is no way to make a generic solution to add an external drive without opening Tivo and pairing drives using external tools (jmfs)
     
  5. Jan 31, 2011 #605 of 2843
    jonja

    jonja New Member

    80
    0
    Feb 22, 2007

    I successfully comerized a 2TB HD for my Tivo Premiere over the weekend. I went with the WD20EURS.

    I found WinMFS to be a snap in the past but I had big trouble with JMFS. The interface was simple enough but the transfer speed was as bad as yours. It took about 10 hours on my iMac but it did work. I think Linux for some reason couldn't get a full USB 2.0 connection on the iMac and reverted to USB 1.1 speeds. It was painfully slow but I am a happy camper now.


    (Before the iMac, I tried my ThinkPad but it has USB 3.0 ports that won't work my new USB Enclosure. Later when I tried the single USB 2.0 port (hidden on the back), it worked).
     
  6. Jan 31, 2011 #606 of 2843
    richsadams

    richsadams Active Member

    8,893
    2
    Jan 4, 2003
    Per my post on TiVoitis' other thread, I can't recall...has someone with a TiVo HDXL (1TB HDD) used jmfs to upgrade to a 2TB drive? I can't see any reason it wouldn't work, but it would be good to have confirmation. TIA
     
  7. Jan 31, 2011 #607 of 2843
    jonja

    jonja New Member

    80
    0
    Feb 22, 2007
    Using the Linux CD (JMFS), I also tried to set some firmware settings on the WD20EURS using HDPARM.

    This website (http://www.rosswalker.co.uk/tivo_upgrade/) recommends:

    hdparm -k 1 -B 1 -M 128 -W 1 /dev/sda

    where sda may be sdb or sdc as the case may be.


    But most of the settings I tried, just gave me errors about not being supported. I couldn't even get hdparm -i (identify drive) to work over USB (though it did work over eSATA). Curiously, over eSATA I couldn't get hdparm -M to work (just wanted to verify the acoustic setting was 128), but over USB while '-i' didn't work, '-M' did work (yes it was acoustic 128).

    It was all very voodoo and I googled hdparm and found that sometimes when the scsi subsystem is used, hdparm doesn't fully function. As if I have anyway of controlling that.

    I also changed my mind about the -B 1 setting, which sets it for most aggressive power management, which sounded to me like Intellipark head parking to me. So I issued -B 254 instead, which forces it to be less power conserving (without turning it off). But honestly, both times it gave me an error about not being supported and I got the feeling it did nothing at all!

    The only setting that worked was -k (save the settings) and -W (write caching, which was already on!)
     
  8. Jan 31, 2011 #608 of 2843
    Fofer

    Fofer XenForo Rocks! TCF Club

    82,087
    286
    Oct 29, 2000
    Hmm. Well, I tried using hddscan (specifically to adjust AAM to 128) on a Windows 7 laptop, and the 2 TB hard drive connected via a SATA->USB bridge. It recognized the drive, but all of those options were grayed out. Like the previous poster, I wonder if this edit can't be done via USB?

    I have a new SATA multi-dock on the way, so I'll be trying again, but I'm wondering if the only way to do this is with a real SATA port on a desktop PC.
     
  9. Jan 31, 2011 #609 of 2843
    Fofer

    Fofer XenForo Rocks! TCF Club

    82,087
    286
    Oct 29, 2000
    Indeed, yours is already set to 128, as richsadams explained:

     
  10. Jan 31, 2011 #610 of 2843
    richsadams

    richsadams Active Member

    8,893
    2
    Jan 4, 2003
    Short answer is that HDDScan works for setting the AAM with a USB dock. I've done it a few times as have lots of others here. My only guess in your case is that the SATA bridge might be getting in the way. Try it with the fancy new Voyager dock and I'll bet it'll work.

    Now, here's the long story for anyone else that might question the results like I just did. I don't have a PC laptop (well, my wife does for work but I stay as far away from it as possible ;) ). However I do have Win7 Ultimate running on my spiffy new MacBook Air via Bootcamp. I just so happened to have a WD20EARS sitting here that I'm going to drop into our Premiere XL and it needed the AAM set. Thanks for the reminder! :up: I connected my BlacX dock to the MBA, inserted the WD20EARS and fired up HDDScan > Features > IDE Features.

    It showed that AAM was enabled (green "light" on) and the "Set" and "Disable" controls were active. As expected the AAM indicated that it was set to 254 in the LH window and the "Recommended" was 128 in the RH window. So I clicked on the slider and pushed it from the far RH side to the far LH side. Now both windows showed 128. I clicked on the "Set" button, closed it out, shut it down.

    Now here's an oddity. I reopened everything and it says that the AAM is back at 254! I tried it with a WD10EARS and the same thing. So I thought I'd try it on my dusty, er, trusty Dell PC using the USB dock. It showed the same results. I could set the AAM to 128, close it out, but when I opened it again it showed that it was back to 254. How is that possible? :confused: Soooo with your thoughts in mind I popped the Dell open and connected each drive directly to the SATA port on the MB. Surprisingly HDDScan said both drives were set to 128. That was very odd, but I'm happy that it worked. I've no idea why the "before and after readings" were different when it was attached via the USB dock.

    Bottom line, if you use a USB dock to change the AAM on a WD drive, it does work. :)
     
  11. Jan 31, 2011 #611 of 2843
    Fofer

    Fofer XenForo Rocks! TCF Club

    82,087
    286
    Oct 29, 2000
    Cool - good to know, and thanks. I'll try again with the new Voyager dock when it arrives.
     
  12. Feb 1, 2011 #612 of 2843
    brshoemak

    brshoemak New Member

    36
    0
    Nov 27, 2010
    I just finished an upgrade on a Tivo Premiere to a 2TB drive (WD20EARS). Did the wdidle3, ran extended test through WD Lifeguard tools, used Tivo boot disk (which was awesome). Didn't change AAM settings with hdscan - didn't research enough beforehand apparently. Did the whole Copy, Expand, Supersize.

    Two items:

    1) Will the stock AAM setting only affect sound or does it affect performance also. I have a media server right next to the Premiere with Caviar Blacks so that will drown out any noise the Green drive would make.

    2) I did the Supersize command, it said it completed successfully, but when I look at the Tivo Recording Capacity I only get 290 vs. 317 like many others do (ONLY is a relative term in this case). Has this happened to anyone else?

    Great work on the boot disk, that was about the easiest process I have ever seen.
     
  13. Feb 1, 2011 #613 of 2843
    ItsRounder

    ItsRounder New Member

    45
    0
    Feb 28, 2010
    My Premiere drive is starting to fail manifesting in stuttering, video artifacts, skipping huge chunks of time while fast forwarding etc. I'm currently using JMFS to hopefully get the drive cloned to a 500GB drive using a MacBook and two USB to Serial ATA enclosures and it's also painfully slow. I thought it was so slow because the drive is going bad which still may be the case but my experience seems to closely match your own. The average rate is currently just shy of 5000kB/s. Fortunately the original drive is a 320 and not something bigger but for those of you who haven't started yet, definitely go with pure SATA if possible. I've used both enclosures for backups and generally see somewhere around 30MB/s so there's something else going on here.
     
  14. Feb 1, 2011 #614 of 2843
    jonja

    jonja New Member

    80
    0
    Feb 22, 2007
    You are the third data point here using a Mac with JMFS and getting glacial transfers. But rest assured, it does work! I suspect the USB drivers on that Linux Live distribution used by JMFS aren't working with the Mac chipsets at full USB 2.0 speeds. The transfer looked to be at USB 1.1 speeds, and it took place on both enclosures I had, pretty much identically.

    Ironically, I wasn't even going to use my Mac for this but the peculiar incompatibilities around my ThinkPad's USB 3.0 ports made me switch to the Mac. I really wanted to use the ThinkPad because I have an eSATA port on it and an enclosure with an eSATA port. I got the eSATA port-based enclosure recognized but never got the USB Enclosure to work (it's new but I've only tested it on the Mac previously). Later, I recalled I had a dedicated USB 2.0 port off the back of the ThinkPad and indeed, after I had comerized the HD, I tested and found the ThinkPad did recognize the enclosure on that port. Good info for the future.
     
  15. Feb 1, 2011 #615 of 2843
    richsadams

    richsadams Active Member

    8,893
    2
    Jan 4, 2003
    TiVo's OEM hard drives are WD A/V GP drives so the AAM is already set to 128. Adjusting the AAM on non-A/V drives won't affect TiVo's performance one way or the other. So if you're happy with things as-is, there's no reason to worry about it.

    I've read about others experiencing the same issue. I haven't tried it, but you should be able to go back and set it again to get the full 317 hours. It shouldn't affect the existing data as it just reclaims the small amount of space reserved for TiVo Clips. I believe you can also do the same thing using winMFS or MFSTools as well.
     
  16. Feb 1, 2011 #616 of 2843
    DrTivol

    DrTivol New Member

    26
    0
    Feb 5, 2005
    sorry if the answer is buried in this thread somewhere, i've been reading and reading and thought i'd just ask.

    I just got a new tivo premiere and i'm upgrading to a 2TB WD20EARS. I'm going back and forth on whether i should do the wdidle3.exe and disable the intellipark.

    So here is the question: I have a Dec 2010 (330GB orig and 2TB upgrade). Won't the 330GB original have intellipark and has anyone looked at what it's set to?

    thanks!
     
  17. Feb 1, 2011 #617 of 2843
    ThreeSoFar

    ThreeSoFar FourNow...WaitFive

    5,419
    0
    May 24, 2002
    Baltimore
    This is exactly the upgrade I just did, and I did not need the wdidle3 at all, soft reboot is no issue.

    But Rich, would Acoustic Management help at all compared to how those shipped?
     
  18. Feb 1, 2011 #618 of 2843
    DrTivol

    DrTivol New Member

    26
    0
    Feb 5, 2005
    I'm going back and forth on this because many say it's not needed for the reboot issued, however if you read enough threads others talk about hitting the 300k parking limit at something like 3 months. Is this still a concern or not?
     
  19. Feb 1, 2011 #619 of 2843
    ThreeSoFar

    ThreeSoFar FourNow...WaitFive

    5,419
    0
    May 24, 2002
    Baltimore
    No idea what you mean by this limit, please elaborate.
     
  20. Feb 1, 2011 #620 of 2843
    DrTivol

    DrTivol New Member

    26
    0
    Feb 5, 2005
    Sure. I've read things like this:

    Quote:The problem is this: The Green Power is designed and marketed as a "green" drive, where power efficiency is the primary engineering concern. As part of this concern, the drive is designed to unload the read/write heads after approximately 8 seconds of inactivity. That in itself is not a bad thing — in fact, it's a common attribute of notebook drives, which have different reasons for saving power (battery life). However, certain software (notably, SpeedFan and some distributions of Linux) can cause issues because they access the drive regularly every 10 seconds or every minute or so. This causes a cycle of rapid loading and unloading that is stressful to the drive — far more stressful than "ordinary" use in which the drive is either working steadily or completely idle.

    It is worth noting that there are no actual failures attributed to this problem as yet — just a number of drives that are reporting rapid (and unusual) increases in load/unload cycles via the drive's SMART reporting feature. Some drives are approaching the rated specification of 300,000 load/unload cycles after less than a year of ownership. While the drives are extremely unlikely to give up the ghost right as the counter crosses 300,000, exceeding the specification indicates the point where the risk of failure begins to increase.

    In some ways, the solution is simple: Don't use software that accesses the drive every 10 seconds. However, for those who can't or won't deal with this on the software level, Western Digital offers a firmware update that either disables the head unload feature or modifies it so that the unload timer is set to longer than 8 seconds (up to 5 minutes is supported). A separate utility is used to control the feature once the new firmware is installed. In either case, the power saving gained by unloading the heads will be lost, but that's probably safer than dealing with potential drive failures down the road. More information about the firmware update (including a new, lower power spin up mode) can be found in this product change notice.

    and then you find the people that say don't disable it:

    **DO NOT USE** the wdidle3.exe /d command. This turns the timer off however many people have reported that the drives eventually slow down to a crawl and/or generate errors using this command. The best is to change the timer to 300 seconds.
     

Share This Page