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. May 16, 2011 #901 of 2843
    unitron

    unitron Active Member

    16,387
    2
    Apr 28, 2006
    semi-coastal NC

    As for what you propose in your final paragraph, I hope someone who knows more than do I responds, but if I were going to roll the dice on this I'd restore to a different drive, and after making sure that the non-MFS partitions were the same size as the ones on the 2TB drive, I'd use dd or dd_rescue to copy the good new ones on top of the suspect ones, leaving the partition map and the MFS partitions on the 2TB drive untouched.

    But I haven't tried that particular experiment yet, so no guarantees whatsoever.

    As far as kickstart is concerned I think you need to read up on it a lot more. You don't access it from the TiVo menu, you get into it by interrupting the boot process at just the right moment.

    You could also ask someone more knowledgeable than am I whether trying the bootpage fix options in WinMFS is a viable idea in your case. I have no idea if WinMFS works with comer'ed drives or not, or even if it works with S4s or not.
     
  2. May 17, 2011 #902 of 2843
    richsadams

    richsadams Active Member

    8,893
    2
    Jan 4, 2003
    Welcome to the forum...sorry to hear its under such frustrating circumstances. It's possible that it's data corruption, although very unlikely anything to do with "software bugs". Corruption generally occurs either when the hard drive is unable to correct I/O errors or when there are physical problems such as power outages, spikes, brown outs, etc. Be sure your TiVo is always connected to a UPS and that you have a clean coax connection (never run it through a surge protector, etc.). As you mention, it's also quite possible that the unit has run into bad sectors on the hard drive, it happens.

    You should try running some of the Kickstarts before doing anything else. Your TiVo doesn't need to boot up fully to run them...in fact they won't run if it does. Have a look here, follow each one in the recommended order and see if things get better. (Note that the procedure for Premiere's is different than with other models...Premiere details are near the bottom of the post.)

    http://www.tivocommunity.com/tivo-vb/showpost.php?p=5643823&postcount=2

    If there are still issues try reinstalling the original drive and see if it runs normally. If so, a replacement hard drive is probably in order.

    Best of luck and let us know how it goes.
     
  3. May 17, 2011 #903 of 2843
    Wislander

    Wislander New Member

    14
    0
    Dec 3, 2008
    Monticello, IL
    Using a spare old computer motherboard (which only has 2 SATA connections) and case, 1 Gig of Ram, an old 2.7 Ghz AMD single core proc, an old 16x IDE CD drive, an old spare power supply, a PS/2 keyboard, and a CRT monitor no less, I was able to use this CD to upgrade/up-size my TiVo Premiere in about 2 hours.

    Even with the outdated scrap pile hardware listed above the CD worked perfectly without a hitch. Seriously, most of the hardware above is 4 - 10 years old and it still works just fine for this process. I am thinking of leaving the system configured and label it as TiVo Workstation.
     
  4. May 17, 2011 #904 of 2843
    unitron

    unitron Active Member

    16,387
    2
    Apr 28, 2006
    semi-coastal NC
    Sounds great as long as that isn't a GigaByte motherboard.


    Although for a moment I was wondering how you used an IDE cd drive on a board with only 2 SATA ports, until I realised you meant a board whose number of SATA ports was limited to 2, not a board whose number of drive ports was limited to 2, both of which were SATA.
     
  5. May 17, 2011 #905 of 2843
    ftballpack

    ftballpack New Member

    5
    0
    Mar 13, 2011
    Hey guys,

    So, I upgraded my Tivo Primere a few months back and installed a WD20EURs in the Tivo and everything had been working great.

    I had to run kickstart 57 a few months back on the original drive literally the day before I did the hard drive swap, just to fix a strange booting issue.

    Well, since I thought kickstart 57 was closesly related to checkdisk in Windows, I had been doing it somewhat frequently as a way to keep the new drive working at top performace.

    Last night I decided to put the drive (the WD20EURS) into kickstart 57 manually and after going to the (GSOD) green screen of death for about 15 seconds it kept rebooting. Little did I know that kickstart 57 could actually corrupt a good drive with a limited drive swap :(

    I still have my original drive and understand that all the files on my expanded WD20EURS are lost. My question is how to properly go about reformatting my WD20EURS using Comer's bootdisk? Do I have to use GParted Live to remove the current partitions on the WD20EURS and then use Comer's boot disk? Can I just use Comer's boot disk to reimage the original drive over the WD20EURS that I corrupted?

    Your help on this one is greatly appreciate guys.

    Thanks,

    ftballpack (Scott)
     
  6. May 17, 2011 #906 of 2843
    Wislander

    Wislander New Member

    14
    0
    Dec 3, 2008
    Monticello, IL
    Actually, it is an ECE Power Motherboard so not too much different than a GigaByte brand. Have people had issues with GigaByte boards and this CD?


    Yeah, I guess I could have explained that better. It has two IDE channels and only two SATA connectors or I could have used a SATA CD/DVD drive. It's more of a comment of a "barebones" system can do this operation.
     
  7. May 17, 2011 #907 of 2843
    unitron

    unitron Active Member

    16,387
    2
    Apr 28, 2006
    semi-coastal NC
    GigaByte boards with Express Recovery or Express Recovery II grab what they think is going to be your OS hard drive (and the OS they expect is Windows) and put a Host Protected Area (which is a sort of partition not recognized as a partition) on the end of it to make room for some sort of system backup file. This happens before they load any actual operating software from any boot source.

    Since they don't recognize the Apple Partition Map used on TiVo drives they think a TiVo drive is an empty drive and fair game for the HPA.

    It's also a really great way to hose a RAID array.

    The problem has nothing to do with what kind of cd you boot with, but with how they (GigaByte boards) screw up hard drives.

    If you boot with the MFS Live cd v1.4, you can run

    hdparm -N /dev/hd"x"

    where "x" is the IDE drive (or SATA drive connnected to an IDE port via an adapter) you want to know about,

    (and probably hdparm -N /dev/sd"x" for SATA drives on SATA ports )

    and it'll show you if all of your LBA blocks are accessible or not.

    If you're on a non-GigaByte board there's a way to undo the HPA (but not the damage it's done to your Tivo partitions) with hdparm (a very dangerous program if you don't know what options and switches to use and which to avoid like the plague), but on a GigaByte board the operation fails because the board blocks it.
     
  8. May 17, 2011 #908 of 2843
    Stuxnet

    Stuxnet Alien Infidel

    356
    0
    Feb 8, 2011
    Yes you can, but I'd suggest you download WD's diagnostic tool and fully test your drive before using Comer's jmfs program.
     
  9. May 18, 2011 #909 of 2843
    richsadams

    richsadams Active Member

    8,893
    2
    Jan 4, 2003
    I have one of those! Wife thinks it should go in the trash heap but every time I think about it...I decide to do another upgrade! ;)

    Congrats on your "new" TiVo BTW.
     
  10. May 18, 2011 #910 of 2843
    richsadams

    richsadams Active Member

    8,893
    2
    Jan 4, 2003
    Hi Scott. Sorry to hear about your issues with TiVo. Windows' checkdisk and KS57 are two different worlds. In fact Windows and the Linux/Apple OS (the basis of TiVo's architecture) are two different worlds. That's why there's no need to "defrag" or do any of the housekeeping that helps Windows run better. I know I made mention of Windows' checkdisk in my KS post so to avoid any confusion like this I removed the reference.

    It's difficult to say if KS57 corrupted your drive...odds are that's probably not the case but anything is possible. Running KS57 or KS58 should only be done when something is wrong. It won't make anything "better" otherwise.

    That said, did you try running KS58? That may be able to repair the problem as it does a bit more work. More here:

    http://www.tivocommunity.com/tivo-vb/showpost.php?p=5643823&postcount=2

    If that doesn't fix things it's possible that it's a data problem or it could be a drive problem. So as Stuxnet suggests, before re-imaging your drive running WD Lifeguard diagnostics (extended read/write/read) would be a good idea.

    Also as mentioned, you won't need to reformat anything...jmfs will take care of that.

    Best of luck and let us know how things go.
     
  11. May 18, 2011 #911 of 2843
    sliu2005

    sliu2005 New Member

    9
    0
    Nov 21, 2010
    Thanks unitron and richsadams for your suggestion. I am very sorry for my tardiness in replying since I am sick.

    I have re-read the kickstart post from richsadams (I have to delete the link in the quote since I have less 5 posts), so it looks like power cycle have the same effect as select "restart" from TiVo menu. I followed Premiere specific instruction at the bottom of the that post, however, TiVo does not seem to respond to PAUSE button. It just reboots too fast for me to enter the code.

    WD diagnostics tool reported S.M.A.R.T. failure, so it looks like bad sectors exists and the drive is about to fail. Called WD support for an advance replacement, when it arrives I will roll the dice and use jmfs to copy from old 2TB to new 2TB (probably takes forever), see if that works. If not, I'll research on dd_rescue and WinMFS. I was under the false impression that these tools do not apply to Premiere, hence comer's jmfs.

    Will report back how it goes. thanks again for your help.
     
  12. May 18, 2011 #912 of 2843
    Wislander

    Wislander New Member

    14
    0
    Dec 3, 2008
    Monticello, IL
    Ah.. yeah I turn all of the Express Recovery, BOIS Image, and Express Back-up tools that motherboard companies add to to their BIOS before I actually do anything with the system. Like you noted they always seem to cause more damage than they prevent in the long run. I actually worked on a Dell Dimension system once that placed a boot loader, in front of the Windows Boot loader and would not allow certain hardware upgrades to ever work. In this case it was a third party eSATA card.
     
  13. May 18, 2011 #913 of 2843
    unitron

    unitron Active Member

    16,387
    2
    Apr 28, 2006
    semi-coastal NC
    On the 2 GigaByte boards I acquired before I knew about this nasty tendency of theirs, there is no way to turn it off, and apparently they never released a bios update with the ability to do so enabled.

    Also, there's no warning about it except in the fine print of the owner's manual.

    Proprietary is one of the dirtiest words in the English language.
     
  14. May 18, 2011 #914 of 2843
    Stuxnet

    Stuxnet Alien Infidel

    356
    0
    Feb 8, 2011
    Well, that's what I thought when I initially tried the kickstart, but it turns out that the flash that occurs immediately upon start-up, is not the one you gotta catch. It's the next one several seconds later... at least on my premiere it worked that way. I must have tried to hit the first yellow flash a dozen times, before I stumbled into to the next one.
     
  15. May 19, 2011 #915 of 2843
    wluk

    wluk New Member

    28
    0
    Jun 10, 2008
    I am trying to upgrade my 1.5tb to 2tb WD EARS drive since last night. It took about 9 hours to copy the data over to the new (used) drive. However, when I tried to expand it, I got the unsuccessful message. So I ran the mfsadd.sh from command line and I got the following error.

    MfsAdd exception: Negative seek offset

    not sure what I should try next. I ran mfslayout on the new drive it shows the 215 HD hours (from my 1.5TB drive).

    Any help would be greatly appreciated.

    thanks!
     
  16. May 19, 2011 #916 of 2843
    wluk

    wluk New Member

    28
    0
    Jun 10, 2008
    I ran it with rev68 this time and I got more information on this screen.

    MfsAdd exception
    java.io.IOException: Negative seek offset
    at java.io.RandomAccessFile.seek(Native Method)
    at tivo.io.Utils.seekBlock(Utils.java:418)
    at tivo.io.Utils.seekBlock(Utils.java:410)
    at jmfs.MfsAdd.writeZones(MfsAd.java:221)
    at jmfs.MfsAdd.writeChanges(MfsAd.java:246)
    at jmfs.MfsAdd.add(MfsAdd.java:41)
    at jmfs:MfsAdd.add(MfsAdd.java:279)
    at jmfs.MfsAdd.main(MfsAdd.java:45)
     
  17. May 19, 2011 #917 of 2843
    Fofer

    Fofer XenForo Rocks! TCF Club

    82,092
    287
    Oct 29, 2000
    I was under the impression you couldn't upgrade an "already upgraded" drive like that. I thought you'd have to use the original drive and upgrade it directly to a 2 TB one.
     
  18. May 19, 2011 #918 of 2843
    wluk

    wluk New Member

    28
    0
    Jun 10, 2008
    for real? that's not good.

    I do have the original 320g image file. maybe I could restore the 320g image to the 2TB drive then run the expand that way. However, I will lose all my recording from my 1.5TB drive.
     
  19. May 19, 2011 #919 of 2843
    wluk

    wluk New Member

    28
    0
    Jun 10, 2008
    When I did the fdisk -l command. I got the following warning message. I don't know if it has any thing to do with my error.

    WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
     
  20. May 19, 2011 #920 of 2843
    retiredqwest

    retiredqwest Member

    164
    0
    Sep 7, 2010
    mfslayout.sh should tell you how many partitions are on the 1.5TB drive. If it is 16 then you can not copy and expand that drive as Tivo does not utilize more than 16. Don't know if that is causing the error.


    Googling that error message talks about maxing out a history file..... way over my head.
     

Share This Page