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

MFS Tools 3.2

Discussion in 'TiVo Upgrade Center' started by jkozee, Jun 4, 2015.

  1. Sep 9, 2015 #121 of 955
    ggieseke

    ggieseke Well-Known Member

    4,508
    206
    May 30, 2008
    If you do, I'd like to see it too. ;)

    Up to 4TB, mfsr uses a fairly standard layout (two app partitions and two media partitions), but adjusted to keep the media partitions under 2TiB. For larger drives it creates one combined app partition and three media partitions.

    Either way, I scrap the MFS zones and start over from ground zero to properly align the app and inode zones for 4K drives.
     
  2. 21364guy

    21364guy New Member

    52
    0
    Oct 20, 2007
    Fingers crossed... I have MFS Tools 3.2 running now to copy stuff from my current 500GB drive (Roamio) onto a new 3TB WD drive. It's 3% done now and claims just under 4 hours to complete. I am wondering if HBO is still going to work, or if I need verizon to reinitialize the cable card in some way.
     
  3. Tweak42

    Tweak42 Member

    32
    9
    Mar 14, 2007
    Los...
    Can anyone clue me in where to find the MFS Tools 3.2 iso image?

    mfslive.org is down, and that's the only site where all google search keep linking back to. Sourceforge only has the old mfstools2 iso.
     
  4. 21364guy

    21364guy New Member

    52
    0
    Oct 20, 2007
    In the end I built it from source myself, though I believe some forum members have unofficial ISOs.
     
  5. 21364guy

    21364guy New Member

    52
    0
    Oct 20, 2007
    So I had mixed success with 3.2 and trying to move from a 500GB disk (Roamio Plus) to a 3TB drive. The command I used was:

    sudo mfstool copy -a /dev/sdX /dev/sdY
    [for me X=a and Y=b]

    My recordings seem to have made it, which is great. Also the cable card, incl. HBO is still working. But the box seems confused in other ways. My channel list is gone and in menus the box refers to itself as "UNKNOWN." At first it said it had run out of show data and needed to connect. But that didn't resolve anything and now it's redoing guided setup.

    Hopefully that will clear things up. But I'm wondering if I did something wrong or if folks typically need to rerun guided setup? I still have the 500GB drive if it's a question of rerunning mfstool with some additional arguments...
     
  6. ggieseke

    ggieseke Well-Known Member

    4,508
    206
    May 30, 2008
    Confused. :confused:

    A Plus should have come with a 1TB drive.
     
  7. jmbach

    jmbach der Neuerer

    2,046
    105
    Jan 1, 2009
    I am not sure but this sounds like you are trying to install an image from another TiVo. In the system information section is the TiVo serial number correct?
     
  8. 21364guy

    21364guy New Member

    52
    0
    Oct 20, 2007
    My mistake, the original drive was 1TB. I had never really used it since I immediately upgraded to a 2TB WD drive. But that just failed under warranty so I pressed the 1TB drive into service while waiting for the replacement. WD sent me a 3TB replacement which is what I ran as the target for mfstool copy.

    Any thoughts on why mfstool copy -a had trouble?
     
  9. jmbach

    jmbach der Neuerer

    2,046
    105
    Jan 1, 2009
    Is the serial number in the system information section correct?
     
  10. 21364guy

    21364guy New Member

    52
    0
    Oct 20, 2007
    I believe so. After repeating guided setup everything is fine as near as I can tell. But I'm not sure what went wrong in the copy operation. Recordings are there, season passes too. But immediately after installing the 3TB drive I had no channels, listings, etc. plus that odd UNKNOWN behavior as noted here:

    http://www.tivocommunity.com/tivo-vb/showthread.php?t=490126

    Also the cable card is still working fine, including protected content.
     
  11. jmbach

    jmbach der Neuerer

    2,046
    105
    Jan 1, 2009
    Since no working ISO has not been posted yet, I will post what I have made temporarily until the developer posts his version or someone else makes a better one. I am not a Linux expert so the ISO is not nice and small but it works for me. It is made with SUSE Studio using openSUSE x64 base and I have made an ISO, USB, VMDX and VHD version.

    Please read complete post before downloading and using these images. It might answer some questions.

    01/14/18 So I believe I have fixed MFSTools 3.2 to work on copying Bolts up to 4TB drive without breaking any previous functionality. I need a few brave souls who would like to test this version. Whoever tries this at this time runs the risk of losing all recordings. So if you want to test this, you must be okay with that. I say that because for when people used MFSTools to copy their Bolt drive previously and ran it in their Bolt, the Bolt promptly reformatted it. It was the right thing for the Bolt to do because MFSTools at that time did not create the correct partition table. However, when people put their original drive back in, the Bolt, I think, deleted the recordings as I do not remember anybody having to redo guided setup or lost CableCARD pairings. So try at your own risk. PM me if your are interested and willing and I will PM you a link back with a link to the test image. As soon as I have enough people try this out and verify functionality, I will release it to the general public.

    10/7/2017 It appears the UAS issue is fixed. More testing on different systems will be the telltale sign. Also I think the image is now bootable under EFI as well.

    9/2/2017 You can use MFSTools to add an external drive to a Bolt successfully. You still cannot use it to copy/backup/restore Bolt images.

    4/5/2017 It seems that on a Roamio with the OS 20.7.x, if you copy the image to another drive, you may experience the RSoD stating that the OS could not be installed. The fix is to do a cold restart of the Roamio and run a Kickstart 58. It will tell you it is installing an update, followed by rebooting to the green screen telling you that a serious error has occurred and it is trying to fix it, then will reboot up normally. If you do a Kickstart 57 instead of a 58, you may be stuck in a green screen loop.

    03/26/2017 It seems that Linux distros have a problem with using USB3 attached drives as USB Attached SCSI (uas) devices including the Linux Distro that this ISO is made from. It appears to be more of a write issue than a read issue with large amounts of data. Looking into a way to prevent the distro from using uas until this bug has been fixed. There are some reports that this is fixed but I have issues with writes when using USB3 that do not happen when I use the same dock but with eSata connection. This is not an issue if the USB3 dock is connected to an USB2 port.

    11/5/16 MFSTools 3.2 has issues working with Bolt images and is not recommended to be used on any Bolt images.

    MFSTools 3.2 ISO
    Live ISO

    MFSTools 3.2 USB/HD
    Use dd in Linux or something like HDD Raw Copy Tool in Windows to copy the uncompressed file to a USB or hard drive.

    MFSTools 3.2 VHD
    For use in Hyper-V.

    MFSTools 3.2 VMX
    For use in VMware/VirtualBox

    Please note, these images should support UEFI booting but if not it will require you to boot in legacy BIOS mode via CSM (Compatibility Support Module) which would need to be activated in your BIOS settings.

    You will login with username 'root' and with password 'tivo'. Logins from previous versions of the images have been deleted as well as auto login function.

    There are no warranties or guarantees with these images and I take no responsibility for anything that happens using these images. You are logged in as root so you could do dangerous things to your system if you are not careful.
    If there are any issues with these files let me know and I will see what I can do.


    Modifications from SourceForge source code as of 12/5/2015 download which has not been incorporated into the SourceForge code as of yet.
    - Made modifications to handle images with a coalesced partition 12 with the original partition 12 at the beginning of the coalesced partition in restore.c. (Will not handle a coalesced partition 10. Other coalesced combinations should be okay. Will need further testing and confirmation to be sure.)
    - corrected declaration of variable skipdb in copy.c

    Additional modifications from SourceForge source code as of 4/5/2017 which include previous modifications and has not been incorporated into the SourceForge code as of yet.
    -Added missing declaration in macpart.h to prevent 64 bit integer being converted to 32 bit.
    -Added missing declarations in several .h files to correct implicit declarations of functions during compile.
    -Added missing include statements in several .c files to resolve compiler warnings about implicit function declarations.

    Added ddrescue to the image so you should not need another disc to try to recover your image if it is damaged.

    Added a couple of tools should only be run on a Premiere image.
    -apmfix - Its purpose is to take the partition pair MFSAdd placed on the drive and coalesce them into one partition so that the Premiere will have the added recording space. If you do not coalesce the partition pair, the TiVo will divorce the media partition but keep the application partition. This will give the appearance of having the full recording space but will error if it tries to access that space because it no longer exists. This program will convert the APM from 32 bit to 64 bit, prune off any Apple_Free partitions at the end of the drive, and then coalesce partition 15 and 16 if present and meets criteria.
    -8TBprep - Its purpose is to prepare a 6TB image on an 8TB drive to accept another expansion by MFSAdd in order to use the full 8TB recording space. For this program to work, partitions 12 and 13 must be contiguous and in order and the image currently has 15 partitions. (Which it should since it currently has a 6TB image on it.) This program will convert a 32 bit APM to 64 bit, prune off any Apple_Free partitions located at the end of the drive, and then coalesce partitions 12 and 13 if they meet criteria.

    Of course these tools would not be needed for MFSTools to be able to use drives larger than 4TB if TiVo would fix their code that causes a 64 bit number to be saved as a 32 bit number when it is adding up the MFS partitions. This is the reason why MFS partitions are limited to 2TiB.

    Added a tool to be run on a Series 5 and later TiVo.
    -bootsectorfix If you run MFSTools on a Series 5 or later TiVo and get an error that states something like "Can not determine primary boot partition from boot sector", then running this program on that drive will attempt to fix the boot sector to resolve that error.

    This post maybe helpful if you are trying to mount a location to save a backup of your image.
    If you want to save recordings as well, add 'a' to the command line.
     
    Last edited: Jan 14, 2018
    meingraham, Shagger, Zack411 and 2 others like this.
  12. HerronScott

    HerronScott Well-Known Member

    5,327
    489
    Jan 1, 2002
    Staunton, VA
    Thank you!

    Scott
     
  13. Johnny1138

    Johnny1138 Nude Member

    33
    0
    Mar 14, 2003
    TX
    thanks jmbach!

    what issues (if any) have you run into with your builds?

    if anyone would like some feedback, i have a roamio and a few 4TB and 6TB drives that I can use for testing/debugging.
     
  14. Anotherpyr

    Anotherpyr Active Member

    228
    27
    May 6, 2015
    Is 3.2 source even available?
     
  15. Anotherpyr

    Anotherpyr Active Member

    228
    27
    May 6, 2015
    Actually you're just user tivo (uid 1000) not root (uid 0).
    You're in the root group, but you're not root and thus lack those privileges.
     
  16. jmbach

    jmbach der Neuerer

    2,046
    105
    Jan 1, 2009
    Perhaps that is a good thing. Thanks for the clarification.
     
  17. jmbach

    jmbach der Neuerer

    2,046
    105
    Jan 1, 2009
    Yes. The OP has a link. The only modification I made was to handle images that have been modified by coalescing partition 12 and 13 together since that was a method to expand a premiere image to 4TB before MFSTools 3.2 came out.
     
  18. jmbach

    jmbach der Neuerer

    2,046
    105
    Jan 1, 2009
    If you need root. Password is still tivo.
     
  19. Anotherpyr

    Anotherpyr Active Member

    228
    27
    May 6, 2015
    Didn't work for me.

    So the issue I'm having is that it appends the number 10 to the drive device, but since it doesn't recognize the partition table on the TiVo drive, it doesn't create the partition entries, just the disk entry. So all mfstool commands fail. I thought I'd try creating the entries with mknod and see if I could list the TiVo drive, but I get authorization denied when I try su - root and the password tivo.

    I'm using an Acer laptop with 2 USB to SATA adapters with a 320GB Premiere drive as the source and a 3TB WD drive as the destination.
     
  20. Anotherpyr

    Anotherpyr Active Member

    228
    27
    May 6, 2015
    Thanks. I was looking under files. Didn't notice the code tab (doh). Built it on Ubuntu and it appears to work. Doing the copy right now. Still added 10 to the device, but now it works. Also required I run it as root. What could possibly go wrong? 😀 It isn't an important laptop so as long as it doesn't wipe the original TiVo drive I won't be upset.
     

Share This Page