MFS Tools 3.2

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

  1. Sep 19, 2016 #461 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016

    Advertisements

    Both docks purportedly support 6TB drives.
     
  2. Sep 20, 2016 #462 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    Motty99 -

    I get same error except for the drive designation.

    "copy target: Internal error opening partition /dev/sdc38654705664 for writing."

    Notice the number after the drive is the same as your error.

    I used the the following command for the copy:

    "mfstool copy -ai /dev/sda /dev/sdc

    I am using my mac so drive c is my target drive.

    What is your set up?

    I have used 2 different computers. The only commonality is I am using USB 3.0 ports.

    Mike
     
  3. Sep 20, 2016 #463 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    Well it was a learning experience, but I was able to get MFSTools 3.2 running on my Mac Mini.

    Bad news is the errors are the same for the target drive.

    MFSTools cannot read the header.

    When I run "mfstool info /dev/sdd"

    I get:

    "info: Input/output error reading volume header.
    info: /dev/sdc10: (null)."

    By the way I get the same error when I try "mfstool info" on the boot drive.

    I tried the copy anyway and got the same error as I got on my laptop.

    "copy target: Internal error opening partition /dev/sdc38654705664 for writing."

    I used the the following command for the copy:

    "mfstool copy -ai /dev/sdd /dev/sdc

    I am using my mac mini so drive A is my internal drive and drive B is the USB stick and drive C is my target 4TB.

    The only commonality is the USB 3.0 ports, could that be the source of the problem?

    When I use "mfstool info /dev/sdd on the source 1TB drive, I get the standard zone information, estimated hours and that I can expand the volume 4 more times.

    Also, I noticed that just before I posted my difficulty that Motty99 posted that he had the exact same error, except for drive designation.

    I posted a response to Motty99 asking about his set up.

    I may try initializing the drive with the Tivo, I think that it will then be recognized by the mfstools.

    Any thoughts?


    Mike
     
  4. Sep 20, 2016 #464 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    OK, I just got a virgin out of the box 4TB Toshiba drive.

    And all of the exact same errors.

    Since I have changed everything else I begining to believe that it may be the USB 3.0 ports
     
  5. Sep 20, 2016 #465 of 1995
    jmbach

    jmbach der Neuerer

    3,198
    482
    Jan 1, 2009

    Advertisements

    MFSInfo will give you that error if the drive does not have an MFS image on it.


    I am not sure why you are having a write error on the drive.

    Remind me again what is the original image you are working with.

    Try a copy to a sub 2TB drive and see if you get the same error.
     
  6. Sep 20, 2016 #466 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    jmbach,

    I have 1TB Bolt drive as the source.

    I can try a copy to 1.5T and let you know what happens.

    Any thought on letting Tivo format my drive so MFStools can recognize it?

    Mike
     
  7. Sep 20, 2016 #467 of 1995
    jmbach

    jmbach der Neuerer

    3,198
    482
    Jan 1, 2009
    The target drive should be blank. However, if you let the Bolt self format the drive and MFSInfo cannot read it, then something is amiss. My first guess would be that the dock does not support large drives. However if you have the same issue with the copy command on sub 2TB drives then I will recheck the images to make sure they are not corrupt.
    Are you using the ISO or the USB version of MFSTools image.
    I don't think it is USB3 issue as I use that myself.
     
  8. Sep 20, 2016 #468 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    jmbach,

    I have used both the iso (laptop) and the usb (mac mini) and had the same problem.

    The "fdisk - l" command correctly identifies the sizes of the drives each time.

    Not sure that means anything though.

    Before I try the Tivo I will try the 1.5 TB drive.

    Mike
     
  9. Sep 20, 2016 #469 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    jmbach,

    OK I tried yet another USB 3.0 drive bay with the 4TB same error on copy.

    Also, I zeroed out my 1.5TB drive and tried it and got the same error on copy.

    Mike
     
  10. Sep 20, 2016 #470 of 1995
    jmbach

    jmbach der Neuerer

    3,198
    482
    Jan 1, 2009
    Same numbers with the error message?
     
  11. Sep 20, 2016 #471 of 1995
    jmbach

    jmbach der Neuerer

    3,198
    482
    Jan 1, 2009
    Can you run this copy command mfstool copy -i /dev/sdX /dev/sdY

    Also try running the dd command to see if you can copy the source image to the 4TB with your setup.

    I have not experienced that issue before. I am not the developer of the program but I will look at the source code to see if it gives me my clues as to why it is not working.

    One thought is that you can run the ISO in a virtual box inside Windows and see if you still get the errors. I have use VirtualBox with this ISO without issue.
     
  12. Sep 20, 2016 #472 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    Yes, all the same except drive designation.
     
  13. Sep 20, 2016 #473 of 1995
    rtoledo

    rtoledo Member

    100
    4
    Feb 18, 2008
    Los Angeles...

    Jim thank you for your answers to us newbies. Frontier seems to be a sad little company. I tried re-pairing the card and it did not work.

    after coming back relaxed from my motorcycle ride with my wife, I climbed up on the closet and re-hooked the 2tb external drive , put the plug back in and it's back working.

    I think I wil wait a couple of weeks and order a 2.5" drive , copy the original drive into the new one and start this process all over again, when I do it, I will post back in here and let all of you know , how it went for me.

    thank you again for your dedication
     
  14. Sep 20, 2016 #474 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    jmbach,

    I tried "mfstool copy -i /dev/sdX /dev/sdY" and got the same error on the copy as with "mfstool copy -ai /dev/sdX /dev/sdY"

    I am running dd now:

    dd if=/dev/sdc of=/dev/sdd bs=2048

    I tried the Virtual Box on my laptop but I abandoned it before it got anywhere. If dd doesn't work I will give it a shot.


    Mike
     
  15. Sep 20, 2016 #475 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    I meant to ask on my last post, when this dd copy finishes, will this drive be done, such that I can put it in my Bolt?
     
  16. Sep 20, 2016 #476 of 1995
    jmbach

    jmbach der Neuerer

    3,198
    482
    Jan 1, 2009
    You can put it in your Bolt but it will be only have the same recording space as the original.

    The purpose of running dd is to make sure the OS can copy and write to the drive when both the source and target are present.

    The error is something I have not seen and using dd to try to isolate the problem and rule out an OS, USB, Dock issue. So if the drive boots in your Bolt without causing it to auto format the drive, then it isolates it to the MFSTool program or the dependencies used to compile and run the program with your hardware.

    I would try to run it inside a virtual machine and see if it works that way. It will insulate the program from the hardware. If it runs in the virtual machine, the the program and its dependencies have issue with the hardware.
     
  17. Sep 21, 2016 #477 of 1995
    Motty99

    Motty99 New Member

    7
    0
    Jun 26, 2014
    I tried to run this on three different MBs (I have a barebones setup for testing) and it gave me that error...i had my drives hooked up directly to the SATA ports...

    but somehow my original drive got clobbered, so I lost everything and just placed the new drive into the Bolt...other than having to rebuild passes, etc, it is running well...

     
    Last edited: Sep 21, 2016
  18. Sep 21, 2016 #478 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    The copy is still running on dd.

    I will let you know if it boots the bolt when it finishes.

    Regarding HW, I have seen this in my laptop and my mac mini.
     
  19. Sep 21, 2016 #479 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    jmbach,

    The dd copy on the 4TB drive successfully booted my tivo.

    I made the copy on my mac mini.

    I again tried to mfstool copy from the 1TB to the now nearly identical 4TB drive.

    I got the same error as my previous attempts.

    I plan on trying the virtual box you suggested.

    Can you tell me how you configured your VB?

    Memory allotments etc.

    Thanks,

    Mike
     
  20. Sep 21, 2016 #480 of 1995
    manderson96

    manderson96 Member

    35
    1
    Jul 11, 2016
    jmbach,

    I have installed VirtualBox on my Mac Mini and I successfully installed MFStools 3.2.

    I can see all of the drives, however I still get exactly the same error when I try "mfstool copy".

    I am not sure how to proceed from here.

    Is there anyway I can expand the 4TB drive now that I have the 1TB disk image copied?

    Mike
     

Share This Page

spam firewall

Advertisements