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

Possibilites of a Series3/TivoHD upgrade beyond 2TB?

Discussion in 'TiVo Upgrade Center' started by CrashHD, Mar 1, 2014.

  1. CrashHD

    CrashHD I am the me.

    757
    0
    Nov 10, 2006
    MO, USA
    Presently, I have not seen anyone get any Series3 model past 2TiB.

    I think there are two expansion options with winMFS. One is to limit the expansion partition to 1TB in size, the other is to extend all the way to the end of the drive. The first option would not give you a substantial increase in usable space, and the second would likely be too much.

    I cannot say for certain, but I think possibly a 652 box may still have a limitation of 2TB of MFS address space, despite the fact it has a 64 bit MFS. There are more knowledgeable folks than me on this board with regard to that subject, and hopefully one of them will respond.
     
  2. jmbach

    jmbach der Neuerer

    1,544
    9
    Jan 1, 2009
    I am not sure anybody has tried to get beyond 2TB on a S3 HD yet. A S3 OLED cannot as I personally verified that. It can boot a drive larger that 2TB but the image on that drive has to be 2TB or less.

    Since you already expanded with WinMFS, you now have 15 partitions. Expanding again with WinMFS, I think, will expand the 15th partition up to 2TB and not give you another pair of partitions giving you a total of 17 partitions. If it does I expect the TiVo to divorce the partitions. If you use JMFS to expand, then you would have 16 partitions. It might be okay with that, I am not sure. The S4 series are not happy with 16 partitions and they divorce it.
    If the above doesn't work then I think the safest way to expand further would be to coalesce your current partition 14 and 15 into partition 14. Let the TiVo divorce partition 15. Then expand with JMFS to either 2TB or 3TB.
     
  3. backyard

    backyard New Member

    16
    0
    Jan 11, 2010
    Thanks to you both. Trying to get to 3TB just may be too technical for me. I'll be better off to get a 2TB drive and use the 3TB elsewhere. Thanks again.
     
  4. c-collins

    c-collins Member

    43
    0
    Sep 27, 2003
    Brick, NJ
  5. Cybernut

    Cybernut New Member

    42
    0
    Oct 1, 2013
    That thread is about Tivo Premieres (Series 4).
     
  6. murryamorris

    murryamorris New Member

    123
    0
    Feb 1, 2005
    I'll test a 3TB drive in my TivoHD. I have a 1TB in it currently and I just did a WinMFS truncated backup. I happen to have a new 3TB WD green drive that was going to be used for a Roamio I ordered but I repaired the bad cap in my S3 OLED so I sent back the Roamio to pay for some medical bills. I'll let you know if it works when I can get time to do it.
     
  7. jmbach

    jmbach der Neuerer

    1,544
    9
    Jan 1, 2009
    Is the 1TB drive native to the HD ( you have an HD XL) or one that was expanded from a smaller image. If it is the latter, then some prep work will need to be done based on how you expanded it the first time.
     
  8. murryamorris

    murryamorris New Member

    123
    0
    Feb 1, 2005
    It was expanded from using WinMFS. What do I need to do to prep it? So doing a truncated backup and restoring won't be enough? Do I need to use JMFS? If there is a specific thread, just point me there and I can read up on it. Thanks for letting me know before I tried it.
     
  9. jmbach

    jmbach der Neuerer

    1,544
    9
    Jan 1, 2009
    Since you expanded with WinMFS, you can restore to the 3TB drive that truncated image. Next I would put it in the TiVo to make sure it boots and operational. Then take the drive out. (BTW the best way to shut down the TiVo is go into the menu and choose to restart the TiVo and pull the plug as soon as you see the front LED flash indicating it is starting to boot back up) The next step would be to coalesce partition 14 and 15 into 14. You can read how to do it in my 4TB DIY writeup. If you have questions let me know. Once that is coalesced, put the drive back in the TiVo and let it divorce as it is getting rid of partition 15 information in the header. Once you verify it is operational, then remove the drive and use JMFS to expand. This will add back a partition 15 that is 2TB in length. Put it back in the TiVo and let us know how it goes.
     
  10. murryamorris

    murryamorris New Member

    123
    0
    Feb 1, 2005
    Thanks for the info. I saw that 4TB thread so I'll look it over. I looked at my old .tbk original is from 10-11-2007 and that may actually be my original backup so I am pretty sure it was WinMFS. I'll give it a try and let you know how it goes. May take me through the weekend to read up on the threads but should be educational. Last time I did all the upgrading was back in 2008 so I'm catching up again.

    Edit: I should be going to sleep (work nights) but thought I'd do a bit more. I restored the current backup with 11.0m from the 1TB I just made on 3/19/14. Dropped it in the Tivo and it rebooted once, then went to green screen for repair. I pulled it back out and decided to try my old backup from 10/11/2007 that has 9.1 on it and it booted fine and I'm now connecting to Tivo to get it updated to the new version. I'll see how that goes. In WinMFS, it only showed 14 partitions but maybe the 15th is added after booting in the Tivo. I'll see when it is done. Should probably work on this after I sleep.

    I think I read that JMFS can only add a 2TB partition so if this was my original image, I wouldn't get to 3TB. I'm off to sleep. I'll need to deal with this when I can think straight!

    Here was the map from the first restore from 3/19:

    Partition Maps
    #: type name length base ( size )
    1 Apple_partition_map Apple 63@1 ( 31.5K)
    2 Image Bootstrap 1 1@309550766 ( 512.0 )
    3 Image Kernel 1 8192@309550767 ( 4.0M)
    4 Ext2 Root 1 524288@309558959 ( 256.0M)
    5 Image Bootstrap 2 1@310083247 ( 512.0 )
    6 Image Kernel 2 8192@310083248 ( 4.0M)
    7 Ext2 Root 2 524288@310091440 ( 256.0M)
    8 Swap Linux swap 1048576@310615728 ( 512.0M)
    9 Ext2 /var 524288@311664304 ( 256.0M)
    10 MFS MFS application region 589824@312188592 ( 288.0M)
    11 MFS MFS media region 137630712@171920054 ( 65.6G)
    12 MFS MFS application region 2 589824@312778416 ( 288.0M)
    13 MFS MFS media region 2 171919990@64 ( 82.0G)
    14 Apple_Free Extra 4294967295@313368240 ( 2.0T)
     
  11. jmbach

    jmbach der Neuerer

    1,544
    9
    Jan 1, 2009
    In this case the 14th partition is a spacer and will have to be deleted if using JMFS as it does not handle Apple_Free partitions. If you are wanting to use the full 3TB you will have to start with a 1TB image. Because of the limitations of the partition map, the max partition size is 2TB.
     
  12. murryamorris

    murryamorris New Member

    123
    0
    Feb 1, 2005
    Thanks again for the info. I figured that out after after messing with it and seeing the partition map only using 2TB for that last one. It turns out my old 1TB is dying and was getting corrupted. I had all kinds of issues and the 1TB also gave me green screen but did repair enough to boot back up. I think that hosed my backups so I'm now adding a 2TB to get it running. I'll try again with the 3TB after this if Still have a 1TB backup that works. I had to go back to my original backup to get the 2TB to boot without errors. Looks like I still have a lot of reading to do.
     
  13. jmbach

    jmbach der Neuerer

    1,544
    9
    Jan 1, 2009
    If you tell WinMFS to limit the expansion to 1TB on your 2TB drive, you can backup that image and restore it to the 3TB drive. That will give you the ability to use the whole 3TB drive.
     
  14. murryamorris

    murryamorris New Member

    123
    0
    Feb 1, 2005
    It looks like there is a problem with the HD electronics, not just the drive, although the drive is back in it and boots up. It is failing, easy to hear but maybe it will hang in there for a while. I had a similar issue with my OLED but the HD doesn't appear to have any bad capacitors so I may just replace them all when I can find time.

    I tried a 1TB, 2TB, and the initial 3TB but none of them were successful, even to just copy the images without any expansion. Looks like I'll have to do some work on this one before I go back to testing the 3TB. Until then I'll use it for one of our computers. Maybe I should have just kept the Roamio, it would have saved me a lot of time.

    I just put the spare 2TB in my OLED and it went easy and quick, just expanded and supersized after testing in the Tivo and no problems. At least I have 318 hours on that now.

    I don't know how some of you guys find the time to figure all this out.
     
  15. unitron

    unitron Active Member

    16,387
    2
    Apr 28, 2006
    semi-coastal NC
    As I understand it, you have to be running at least 11.0h for the HD to handle a partition larger than 1.2TB, which was the barrier to using a 2TB drive.

    If you use WinMFS to restore an HD image, it'll put 160GB worth of partitions on the drive.

    If you allow it to expand, but tell it to limit partition size to no larger than 1.2TB, I'm pretty sure that you'll still have an Apple Free partition on the drive beyond that 1.2TB partition.
     
  16. murryamorris

    murryamorris New Member

    123
    0
    Feb 1, 2005
    I had 11.0m on the 1TB images. The only backup I got to actually boot without locking up was a 9.1 old backup. I was going to update it to 11.0m but the connection will not go through. I spent about 6 hours trying different current restores and trying to update the old one. None of these were ever expanded. I just restored and was testing them before expanding. I have one more thing to try before I either replace the caps or sell it for parts and get a Roamio in a few months when I have the money again.

    And yes, I believe it did show the large free partition the one time I tested expansion and limited it to 1TB. That locked up also but I figured it would since the unexpanded ones did also.

    Thanks for the info!
     
  17. jmbach

    jmbach der Neuerer

    1,544
    9
    Jan 1, 2009
    I haven't tried this since TiVo did something with their servers to fix the random reboot issues for the Roamios, but when I tried to use kickstart codes to update the software on my OLED S3 I would get this error.

    [​IMG]

    The only way I could update the OS was to let it boot up and force a connection several times (3 to 5) and then reboot the TiVo to apply the update.

    I don't know if this was your issue or if you had something else come up.

    (BTW I did not get this error on my S4)
     

    Attached Files:

  18. murryamorris

    murryamorris New Member

    123
    0
    Feb 1, 2005
    Mine is different. I don't get that error and if I do a network diagnostic check (or whatever that is called - I'm at work now). It goes through the entire process and says "done" under connection and doesn't fail there. Only when I do the forced connection to update and it gets to the section where it says "downloading", runs for a while and appears to be working then will say failed or lost connection. It also is taking much longer at the previous steps than my other Tivo bu might just be the difference in the units.

    I pulled my OLED 1TB drive (WD Blue), which is almost new as I just repaired the unit. I upgraded it to 2TB and am currently writing zeros to totally clear the 1TB. Should be done when I get off work. I'm going to run WinMFS off another computer to be sure it's not flaking out on that system. I'll try the 1TB image to that drive and see what happens. If still no go, I may try to mfscopy the old drive because if it can make it, the Tivo might be able to repair it if there are some errors. It did successfully repair the old drive when I put it back in. If that works, I can image the new 1TB drive and then work on the 3TB from that. I could at least then see if the 1TB to 3TB works, even if the network connections don't work on it. It may take me until my vacation in May, but I'll keep trying.

    EDIT: Things are looking slightly better. When I got home, the zero write on the newer 1TB was done. I restored the 1TB image from last week of the failing drive and decided to just mfsadd after that instead of putting in the Tivo then doing. It booted up all the way to the startup where the Tivo guy video came on and about halfway through it froze the video, rebooted and has now been on green repair for half an hour. Making me think it will do the repair and I may have a good drive to image a 1TB off of.

    So now, I am going to write zero's to the 3TB to clear it and start from there if the 1TB does actually work. Off to sleep....
     
  19. murryamorris

    murryamorris New Member

    123
    0
    Feb 1, 2005
    Finally, it is working again. The new 1TB drive repaired and I reconnected to my wireless network adapter. It is transferring a show from the other Tivo and a forced connection worked and is loading updates.

    Here is the new drives msfinfo. It looks like I'll be able to work on testing the 3TB after all. Just have to go back and read to figure out the easiest route.

    Mfsinfo (Drive 2)

    Boot Page
    Boot Page: root=/dev/hda4
    Active Boot Partition: 3 Active Root Partition: 4
    Backup Boot Partition: 6 Backup Root Partition: 7

    MFS Super Header
    state=0 magic=ebbafeed
    devlist=/dev/hda10 /dev/hda11 /dev/hda12 /dev/hda13 /dev/hda14 /dev/hda15
    zonemap_ptr=1121 total_secs=1950871552

    Zone Maps
    Z0: type=0
    map_start=1121 map_size=1 backup_map_start=589822
    next_map_start=263266 next_map_size=6 next_backup_map_start=589816
    zone_first=1122 zone_last=263265 zone_size=262144 min(chunk)=262144
    free=262144 checksum=a79b745a logstamp=40095193 num_bitmap=1
    Z1: type=2
    map_start=263266 map_size=6 backup_map_start=589816
    next_map_start=263272 next_map_size=34 next_backup_map_start=589782
    zone_first=589824 zone_last=138215423 zone_size=137625600 min(chunk)=20480
    free=11960320 checksum=9f292806 logstamp=40095428 num_bitmap=14
    Z2: type=1
    map_start=263272 map_size=34 backup_map_start=589782
    next_map_start=138219520 next_map_size=1 next_backup_map_start=138809343
    zone_first=263306 zone_last=589777 zone_size=326472 min(chunk)=8
    free=89224 checksum=60eee7a5 logstamp=40096146 num_bitmap=17
    Z3: type=0
    map_start=138219520 map_size=1 backup_map_start=138809343
    next_map_start=138481665 next_map_size=10 next_backup_map_start=138809333
    zone_first=138219521 zone_last=138481664 zone_size=262144 min(chunk)=262144
    free=262144 checksum=83de9a9a logstamp=40095193 num_bitmap=1
    Z4: type=2
    map_start=138481665 map_size=10 backup_map_start=138809333
    next_map_start=138481675 next_map_size=34 next_backup_map_start=138809299
    zone_first=138809344 zone_last=310718463 zone_size=171909120 min(chunk)=20480
    free=13414400 checksum=49d981af logstamp=40095428 num_bitmap=15
    Z5: type=1
    map_start=138481675 map_size=34 backup_map_start=138809299
    next_map_start=310728704 next_map_size=67 next_backup_map_start=310730685
    zone_first=138481709 zone_last=138809292 zone_size=327584 min(chunk)=8
    free=284192 checksum=1a92884c logstamp=40095193 num_bitmap=17
    Z6: type=2
    map_start=310728704 map_size=67 backup_map_start=310730685
    next_map_start=0 next_map_size=0 next_backup_map_start=0
    zone_first=310730752 zone_last=1950871551 zone_size=1640140800 min(chunk)=20480
    free=225587200 checksum=c9951228 logstamp=40095428 num_bitmap=18

    Partition Maps
    #: type name length base ( size )
    1 Apple_partition_map Apple 63@1 ( 31.5K)
    2 Image Bootstrap 1 1@309550766 ( 512.0 )
    3 Image Kernel 1 8192@309550767 ( 4.0M)
    4 Ext2 Root 1 524288@309558959 ( 256.0M)
    5 Image Bootstrap 2 1@310083247 ( 512.0 )
    6 Image Kernel 2 8192@310083248 ( 4.0M)
    7 Ext2 Root 2 524288@310091440 ( 256.0M)
    8 Swap Linux swap 1048576@310615728 ( 512.0M)
    9 Ext2 /var 524288@311664304 ( 256.0M)
    10 MFS MFS application region 589824@312188592 ( 288.0M)
    11 MFS MFS media region 137630712@171920054 ( 65.6G)
    12 MFS MFS application region 2 589824@312778416 ( 288.0M)
    13 MFS MFS media region 2 171919990@64 ( 82.0G)
    14 MFS MFS App by Winmfs 2048@313368240 ( 1.0M)
    15 MFS MFS Media by Winmfs 1640140800@313370288 ( 782.1G)

    Total SA SD Hours: 1040 Total DTV SD Hours: 908 13 % Free
    Software: 11.0m-01-2-652 Tivo Model: TCD652160
     
  20. jmbach

    jmbach der Neuerer

    1,544
    9
    Jan 1, 2009
    The easiest way is to coalesce partition 15 and 14 into 14, boot the drive in the TiVo to divorce partition 15 (in name only), and then run JMFS to expand again. There is a Linux script from marwatk that will allow you to copy and rearrange the partition locations to make the drive closer to a TiVo layout by placing the OS at the end of the 1TB image. The coalesce script will not work because it is made to allow for partition 14 on the S4 which is not a MFS partition but an sqlite partition. If you use his script, the partition order you want is 1,11,12,13,14,15,2,3,4,5 6,7,8,9,10. After you copy and rearrange the partitions, put it in the TiVo to make sure it boots. Then a manual coalesce, boot in TiVo, expand with JMFS, and back in the TiVo to see if it works.
     

Share This Page