MFS Tools 3.2

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

  1. jmbach

    jmbach der Neuerer

    3,018
    421
    Jan 1, 2009

    Advertisements

    The copy process copies and expands at the same time.

    You might have gotten the target and source drives reversed. If b you get the error again, post a screenshot so I can see what led up to the error.

    Sent from my SM-G988U using Tapatalk
     
  2. Herb EN

    Herb EN New Member

    24
    0
    Sep 3, 2020
    I guess this is the best thread to put this in as it is an MFSTools 3.32 problem, I think. I apologize if I clogged up the other Bolt Upgrade thread with an MFSTools question.

    I am trying to upgrade my Bolt 1TB to 6TB. I downloaded
    MFSTools 3.32-devel USB/HD
    RAW image file to make bootable USB drives requires direct copy of file contents to USB drive.
    md5 hash for compressed raw file: 2a25613140dfa835b5b41a184ba54ac1

    I used the HDD Raw Copy Tool in Win10 to copy MFSTools 3.32-devel USB/HD to a 16 GB flash drive.

    I disconnected all my HDs from my PC, connected the TiVo Bolt 1 TB drive to the 0 MB SATA connector, and booted off the MFSTools FD. I did not connect the new target drive yet. Baby steps. Before the login I am getting error messages, I login in anyway, which works, and then try the "lsblk -o,name,size,vendor" command to verify where my TiVo original drive is and it does not work. See the screen shot.
    [​IMG]
    Did not go further without verifying the drive location. Can someone let me know what is happening and what to do?
    Hoping to make another attempt tomorrow night. I know zip about linux so I would really appreciate some input. Thanks in advance
     
  3. jmbach

    jmbach der Neuerer

    3,018
    421
    Jan 1, 2009
    Syntaxes looks wrong. Should be:
    lsblk -o name,size,vendor

    Does not look like what you typed (although it is a little blurry to me)

    Linux is very particular about syntax

    Sent from my SM-G988U using Tapatalk
     
  4. Herb EN

    Herb EN New Member

    24
    0
    Sep 3, 2020
    Thanks. Yes syntax. Put a comma after the "-o" should be a space. My bad. Will try again tomorrow night. Really appreciate the quick reply! Sorry about the blurry image. It looked clearer on a bigger screen. What about the error messages above it. The "read/64, error -110" error three lines, and the "device not accepting address 9, error -71" What do these mean? or Does it matter?
     
  5. jmbach

    jmbach der Neuerer

    3,018
    421
    Jan 1, 2009

    Advertisements

    What USB devices are plugged into the computer

    Sent from my SM-G988U using Tapatalk
     
  6. ClearToLand

    ClearToLand Old !*#$% Tinkerer!

    1,095
    167
    Jul 9, 2001
    Central Jersey
    Sizze?
     
  7. cardinals41

    cardinals41 New Member

    5
    0
    Feb 13, 2008
    jmbach, thank you for your prior responses.

    I've been trying to copy a 2TB drive to a new 3TB drive. I have not been able to get mfscopy -ai /dev/sdX /dev/sdY to work. I get the volume header error. When I use mfscopy -ai /dev/sda /dev/sdb it started to copy. Does that work the same and if not how do I get the same results as if I used sdX and sdY? Thanks
     
  8. jmbach

    jmbach der Neuerer

    3,018
    421
    Jan 1, 2009
    X and Y are just placeholders. You have to figure out your drive names and replace those with the correct drive name like you did with 'a' and 'b'

    Sent from my SM-G988U using Tapatalk
     
  9. ThAbtO

    ThAbtO TiVoholic by the bay TCF Club

    12,093
    1,014
    Apr 6, 2000
    SF Bay Area
    Using sdX and sdY will not work as these are just examples for the source and target drives. Since you would not have drives specified as sdx or sdy.(Hence the capitals.)
     
  10. Herb EN

    Herb EN New Member

    24
    0
    Sep 3, 2020
    MFSTOOLS COMMAND QUESTION
    I am upgrading my 1TB Bolt to 6TB.
    I have successfully copied the 1TB drive to the 6TB drive using the command "mfscopy -a /dev/sda /dev/sdb". The space went from 90% filled to 56%.
    I know I have to add 2 TB partitions using mfsadd and mfsaddfix.
    Please confirm that I add the partitions one at a time, i.e.
    mfsadd
    mfsaddfix
    mfsadd
    mfsaddfix​
    I have now again read the other thread "Bolt with 3TB, want to upgrade to 8TB or more" and in that thread the command to use was "mfscopy -am 2040 /dev/sdX /dev/sdY"
    What is the difference?
    Should I re-copy the 1TB drive to the 6TB drive using "am 2040" version of the command before trying to add 2 TB partitions.
    Should I use the "mfsadd -xm 2000 /dev/sdb" command where b is the 6TB target command, or simply "mfsadd /dev/sdb"?
    I am in the dark here. Also where can I get a complete set of current commands for the mfstools 3.32 I have downloaded from

    MFSTools 3.32-devel USB/HD
    RAW image file to make bootable USB drives requires direct copy of file contents to USB drive.
    md5 hash for compressed raw file: 2a25613140dfa835b5b41a184ba54ac1

    AS always, thanks in advance, really appreciate the assistance.
     
  11. jmbach

    jmbach der Neuerer

    3,018
    421
    Jan 1, 2009
    Can you post the mfsinfo -d on the drive.

    Generally speaking you should use am 2040 when doing the copy process. As mfstools does not copy correctly to anything over 4 TB so we have to limit the initial copy to 4 TB which is what the command does.

    Sent from my SM-G988U using Tapatalk
     
  12. Herb EN

    Herb EN New Member

    24
    0
    Sep 3, 2020
    Thanks again jmbach! I will just redo the copy using the "mfscopy -am 2040 /dev/sda /dev/sdb" command where "a" is the source, "b" is target. I copy overnight anyway so as not to interfere with normal use, it takes about 4 hours, no problem. I would rather not throw more variables into the equation than needed.

    Is there any need to wipe the target drive before redoing the copy? If so, how?

    Also, please confirm the command sequence for adding two 2TB partitions (to bring total up to 6TB) as:

    "mfsadd -xm 2000 /dev/sdb"
    "mfsaddfix /dev/sdb"
    "mfsadd -xm 2000 /dev/sdb"
    "mfsaddfix /dev/sdb"

    I thank you in advance. Herb
     
  13. jmbach

    jmbach der Neuerer

    3,018
    421
    Jan 1, 2009
    You can use the manufacturer diagnostic program to wipe the drive. A quick erase/wipe would be fine.

    Since the copy creates a 4TB image, you just need one iteration of the mfsadd/mfsaddfix. You can use 2040 parameter for the mfsadd command.

    Are you on TE3 or TE4?

    Sent from my SM-G988U using Tapatalk
     
  14. Herb EN

    Herb EN New Member

    24
    0
    Sep 3, 2020
    I am running TE4. I am just going to run the "mfscopy -am 2040 /dev/sda /dev/sdb" and then run
    "mfsadd -xm 2040 /dev/sdb"
    "mfsaddfix /dev/sdb"

    as you have instructed.


    If MFSTools is writing an image it should overwrite everything that previously been written. Correct me if I am wrong

    What difference does the TE4 vs TE3 version make?
    Thanks for all your help.
     
  15. jmbach

    jmbach der Neuerer

    3,018
    421
    Jan 1, 2009
    It should overwrite the drive. It is always better to erase it first.



    Sent from my SM-G988U using Tapatalk
     
  16. Herb EN

    Herb EN New Member

    24
    0
    Sep 3, 2020
    Hi again jmbach,
    Ok, so I ran, without cleaning the 4TB drive,
    "mfstools -am 2040 /dev/sda /dev/sdb"
    "mfsadd -xm 2040 /dev/sdb"
    "mfsaddfix /dev/sdb"


    I then put the drive back in the Bolt TE4, and got this death screen
    upload_2020-9-22_16-48-9.jpeg

    So, I then "cleaned" the 6TB drive using "diskpart"
    Ran
    "mfstools -am 2040 /dev/sda /dev/sdb" again (sda being the original 1TB drive)
    Re-installed the newly copied 6TB drive in the Bolt TE4 and all is well except, as expected, only 4TB storage shows up on the Bolt TE4.
    Now I want to add the next 2TB partition.
    Since I ran the "mfsadd -xm 2040 /dev/sdb" last time and got the red death screen, should I run
    "mfsadd -xm 2000 /dev/sdb" followed by"msfaddfix"
    instead or try the 2040 again? What is the difference, or is too technical which I get.
     
  17. Herb EN

    Herb EN New Member

    24
    0
    Sep 3, 2020
    further to my above post, with the 6TB drive (without runing the "mfsadd...") the Bolt TE4 says capacity is 701 HD, with the original 1TB drive it was 156 HD. 701 HD is more than 4 times as much but less than 6 times as much. I presume there it would not be exact as there is overhead data on the original drive which does not expand. What is the expected capacity with a 6TB drive?
     
  18. jmbach

    jmbach der Neuerer

    3,018
    421
    Jan 1, 2009
    I have on occasions got the Red screen of death. So far, every time I got one, a Kickstart 58 fixes it.

    Since you are doing 6 TB, you can run mfsadd -x /dev/sdb and not use the m 2040 or the m 2000 flags.

    Sent from my SM-G988U using Tapatalk
     
  19. jmbach

    jmbach der Neuerer

    3,018
    421
    Jan 1, 2009
    So when you use m 2040, it will create recording partitions that are larger than what would be created on a normal 4TB drive but still respects the 32 bit limit of the partition size ( which is 4294967295 blocks per partition).
     
  20. Herb EN

    Herb EN New Member

    24
    0
    Sep 3, 2020
    I cannot thank you enough, jmbach! used the"mfsadd -x /dev/sdb" and "mfsaddfix /dev/sdb" and all is UP AND RUNNING! Went from 90% full on the 1TB drive to 15% on the 6TB as is expected.

    Also, looked up the Kickstart codes since you mentioned "Kickstart 58," something I was unaware of. Interesting. Hope I never need to use them. Never want to see that Red screen of death. Scared me!

    I will now transfer everything to the Bolt, retire my Roamio (save it for someday when Bolt actually dies), and pay only one service fee. My wife also hated switching between boxes, even with an IR remote HDMI switch.
    Stay well, and thanks again Herb EN:)
     

Share This Page

spam firewall

Advertisements