MFS Tools 3.2

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

  1. Keith A Heikkinen

    Keith A Heikkinen New Member

    20
    0
    Feb 10, 2019
    The Tivo is a series 3 with a few recorded programs on it. The drive was functioning without any indication of a problem. I just wanted to expand the drive to a two Terabyte NAS drive. How would I know if it was failing without any symtoms? The msfcopy ended with the "segmentation" statement, after the screen scrolling for about 3 to five minutes of Input/output error message.
    Thanks for the interest and the help.
     
  2. jmbach

    jmbach der Neuerer

    2,856
    390
    Jan 1, 2009
    More than likely a bad spot developed in a non-sensitive spot in the disk. These are usually recordings where you might see a slight glitch or something but MFSTools copies all. What I would suggest is copy the image to a spare drive with ddrescue. Then use mfscopy.
     
  3. Keith A Heikkinen

    Keith A Heikkinen New Member

    20
    0
    Feb 10, 2019

    It seemed as though something had happened and perhaps drive was copied, although time it took seemed quite short at perhaps 1-1/2 hours. Decided to plug in new drive and see what happened.
    To my surprise the "Welcome, Powering Up" yellow and balck screen showed up, and after a while the "Almost There. Just a few Minutes" screen. But, it then goes dark screen and starts again with the Welcome screen, Rinse, lather,repeat. I'm afraid this is in a loop.

    Has done the above now for about 20 minutes, and not sure where to go from here. No error messages, but never get past the initial boot screens. Clearly at least something got copied over, but not enough to make it work.

    Any ideas? Has this happened to others?
     
  4. jmbach

    jmbach der Neuerer

    2,856
    390
    Jan 1, 2009
    As a test, copy the drive using only -i in the mfscopy command. That copy should only take about 5 to 10 minutes. It won't copy recordings but if it copies without an error, then the issue is in the recording section of the drive.

    To be able to copy the recordings, the corrupt/bad area of the drive needs repair.
     
  5. Keith A Heikkinen

    Keith A Heikkinen New Member

    20
    0
    Feb 10, 2019

    Based on what was advise earlier this evening, I ran dd_rescue to a new WD black 1TB drive I had (brand new, never used). It seems to be copying the drive over at 7% right now and about 11 hours to go. showing 0 errors right now.

    I have no idea what the dd_rescue even is supposed to do? Its doing something. If this finishes, am I supposed to then try to MSFcopy this to the new WD red drive destined for the TIVO? No idea.

    Thanks for all the advise. Feeling like I have no idea what is happening or what to expect next.
     
  6. jmbach

    jmbach der Neuerer

    2,856
    390
    Jan 1, 2009
    ddrescue will try to recover a bad spot on the disk.

    MFSTools has no error correction/recovery code. It just blindly reads and the writers the data it sees. If it cannot make any sense of it, it scraps out.

    If mfscopy still craps out on your ddrescue copy, put that copy in your tivo and run a Kickstart 58. Tryvthe copy again. If it craps out, put it back in the TiVo and run a kickstart 57 and try the copy again.
     
  7. Keith A Heikkinen

    Keith A Heikkinen New Member

    20
    0
    Feb 10, 2019
    Thank you JM,

    The ddrescue has run through the night and has about 4 hours to go. Think it will make it.

    I'm curious, if the dd_rescue successfully copies disk, wouldn't it have made sense to just run that to the new drive, and skip the second step, or am I missing something? As I have no idea, I will follow the very good advise here, but interested to know.

    As for kickstarters, the only ones I'm familiar with concern motorcycles and I have honestly considered dragging the TIVO down the street, with a motorcycle, car or truck.
    I've seen the 58 and 57 referred to here from time to time, but not certain what either are, and now will need to at look around for what they are, do and if there are any related command lines I need to know.

    Thanks again, to any and all who have helped, to date. Really never imagined this was going to be quite this complicated.
     
  8. Keith A Heikkinen

    Keith A Heikkinen New Member

    20
    0
    Feb 10, 2019

    OK,
    The dd rescue finished with no errors. I went ahead and tried to run that in the TIVO, out of curiosity, but stuck at "Powering Up" and never even got to "Almost There......"

    So, now doing the dd rescue spare to the new WD Red again, via MFScopy. Don't have high hopes.

    I also put the original drive in the TIVO and it still works normally, so it is still viable.

    As I don't really need any programs on this box, is there an image file that can load to the new drive and bypass all this copy stuff, or am I still missing something??

    Thanks
     
  9. ggieseke

    ggieseke Well-Known Member

    5,531
    645
    May 30, 2008
  10. jmbach

    jmbach der Neuerer

    2,856
    390
    Jan 1, 2009
    If you do now need the recordings, run the mfscopy command without the 'a' in the command line (mfscopy -i /dev......) off your original drive to the new drive.

    Might want to run WD diagnostic quick erase/write on the new drive before running another copy to it.


    BTW did you run WD Diagnostic full read and write on the drive to "certify" it for use before running mfscopy?
     
  11. HomeUser

    HomeUser Active Member

    2,447
    13
    Jan 12, 2003
    A2 Michigan
    Drive images can be found Image for TiVo Series 3 you need the first 3 digits of the TiVo Service Number to identify the DVR model it should be 648, 652 or 658 for the Series 3 TiVo DVRs the TSN can be found on the back of the DVR.

    Strange that the copied drive would not boot what model revision level is the drive?
    dd_rescue makes an direct image copy of the source drive if it finished without error the copy should not be any different than the original.
     
  12. Keith A Heikkinen

    Keith A Heikkinen New Member

    20
    0
    Feb 10, 2019
    Thanks JM, I have to run out for a bunch of hours, but will get back to you on this later.

    Thank you again, I appreciate the support
     
  13. TSR

    TSR New Member

    5
    0
    Feb 19, 2019
    I have probably messed up the MBR on my tivo premiere drive - this is my fault

    Have an aging, full lifetime premiere that was starting to show hard drive issues. Discussed with a friend to make a copy through linux and suggested I setup a vm using hyper v in Windows 10 and connect the drives via USB dock. I did not format the drive but as I'm sure you can see where this is going, I've initialized them.

    Been reading through the forums today looking for the best fix. Googling often brought up so many old threads that I think my info is not correct.

    It looks like at one point you couldn't use MFStools on Premieres but with 3.2/3.3 it's backwards compatible.
    I can find instructions on how to do a bootfix using the older, outdated MFStools and Tivo versions 1-3

    I'm am not Linux knowledgeable and it's starting to show.

    I read about the bootsectorfix:

    -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.

    but since that's 5 and later, I don't want to run that as I assume I'll mess up my drive further. So I'm in a weird spot. I know with old MFStools I could address Tivo 1-3. And with the newer MFSTools I can address 5 and later.

    Is there anything for Premiere?


    PS - how can I verify MFStools is even seeing the connected drive. I saw this
    "Easy way to identify connected drives (thanks to 192bowler showing me this) - lsblk -o name,size,vendor"
    But it just brings up the CD-ROM drive

    thank you all!
     
  14. jmbach

    jmbach der Neuerer

    2,856
    390
    Jan 1, 2009
    Have you put in the original drive back in the TiVo to see if it boots? If it boots to any screen past the first boot logo before boot looping then windows probably did nothing to the drive.

    Was the drive original to the TiVo or was it replaced in any way shape or form?

    MFSTools 3.2/3.3 will work on Premiere images, just some of the ancillary tools do not.

    If 'lsblk -o name,size,vendor' only sees the CDROM, then MFSTools will only see the CDROM. Chances are you did not connect the drives to your VM.
     
  15. TSR

    TSR New Member

    5
    0
    Feb 19, 2019
    1) no, I will try that next

    2) not original drive, a friend replaced it a few years ago and only recently started to lock up

    3) is there a boot fix for premier on the cd?

    4) poor explanation on my part. I abandoned the VM idea, I completely neglected to mention that.

    I could not get the VM to see the docked drives. So I put the old TiVo drive and new blank drive into a tower (removed the Windows OS drive, so there were just the two aforementioned drives and a cdrom) and copied old to new using these steps

    A Guide to Upgrading Your Tivo Bolt, Tivo Premiere, Tivo Roamio, Tivo Roamio OTA, Tivo HD, Tivo Series 3 or Tivo Series 2 (Easily upgrade your Tivo Bolt, Roamio or Premiere to 300 Hours+ HD Capacity) - Also includes instructions on how to fix a broken Tivo.

    That Linux CD saw the drives and it took many hours for the copy to complete.

    Today I only tested the new copied drive in the tivo but I only get all the lights on the front of the TiVo flashing and it quickly resetting.

    Putting the hard drives back in the tower and using the mfstool CD, it mentioned it only saw the cdrom. So I don't understand what went wrong there when the other CD said it saw both drives just fine.

    Hope this all made sense
     
  16. unitron

    unitron Well-Known Member

    16,576
    41
    Apr 28, 2006
    semi-coastal NC
    The motherboard from which you disconnected the Windows drive, is it a Gigabyte brand board by chance?
     
  17. mstrbill

    mstrbill New Member

    9
    0
    Jul 3, 2017
    I would like to move the recording from my Bolt's 4TB 2.5in WD blue drive to a 8TB 3.5in Red drive. The blue drive is starting to fail at just short of a year.
    1. Will mfscopy copy and expand to 8TB for a Bolt? Or can I clone and expand somehow?(I have actually done the clone, and msinfo gives the same info both drives)
    2. Is there something I should run to stabilize the 4TB drive before copying?
    3. If I can use mfscopy and what options should be used?
    Thanks
     
  18. jmbach

    jmbach der Neuerer

    2,856
    390
    Jan 1, 2009
    TiVo still has not fixed the bug in their OS that allows larger than 2 TB partition sizes so you cannot use MFSTools to go to 8 TB directly.

    Follow the info in the 10 TB Roamio thread. Although it has not been tested, the method should work since Roamios and Bolts are very similar in most ways.
     
  19. tkrotchko

    tkrotchko New Member

    10
    5
    Jun 7, 2007
    For a speed comparison, I finished my 4th Tivo upgrade to 4TB from 2&3 TB drives. That is copying all content and expanding the drive

    In generally, I was seeing about 51-53 MiB/Sec using an i7 CPU, booted from the JeOS/Suse MFSCopy 3.3 DVD. Both drives were connected to independent SATA ports

    To copy a 2TB->4TB drive, it generally took 9-10 hours The 3TB->4TB transfer took about 12 hours.
     
    kpeters59, apsarkis and jmbach like this.
  20. stringham

    stringham New Member

    1
    3
    Feb 23, 2019
    I was able to successfully upgrade my Bolt from a 500GB to a 4TB drive and copy over my existing recordings and content. I'm really new to this and thought it might help someone else to know the steps I took in order to achieve this.

    First I tried cloning the 500GB drive content to the 4TB drive and then use mfsadd but that said that there was no more space to add, and the Tivo did not recognize that it was a larger drive.

    1. Made a backup of the 500GB drive that was in my Bolt (this step was not necessary, but I wanted to be careful)
    2. Downloaded MFSTools 3.3-devel USB/HD and saved to a usb drive and booted from it (I had to use the failsafe option when booting). Logged in with username: 'root' and password: 'tivo'
    3. Plugged in the (backup) 500GB and 4TB drives with USB adapters
    4. Determined the names of the drives with lsblk -o name,size,vendor (/dev/sdX is the source drive and /dev/sdY is the destination drive)
    5. Running mfscopy -a /dev/sdX /dev/sdY gave the error: "Cannot determine primary boot partition from boot sector"
    6. Ran bootsectorfix /dev/sdX
    7. Ran mfscopy -a /dev/sdX /dev/sdY and waited for it to finish copying
    8. Ran
    mfsadd -xm 2000 /dev/sdY and mfsaddfix /dev/sdY (I'm not sure if these were necessary)
    9. Put the new drive in the bolt and booted up. All content was successfully copied and there is now 639 HD hours.

    Thanks jmbach for your work on MFSTools!
     
    RyanG34, Rapt0r and V7Goose like this.

Share This Page