MFSTools 3.2 and "There was an error loading series data"

Discussion in 'TiVo Upgrade Center' started by jtwhipit, Jan 15, 2018.

  1. jtwhipit

    jtwhipit New Member

    2
    0
    Jan 17, 2007

    Advertisements

    Goal: To replace the fully functional original 1TB drive on a Roamio Plus (which has been behaving perfectly fine) with a 2TB Western Digital WD20EFRX before it starts to fail. I'm trying to keep all my recordings.

    Procedure: I used the MFSTools 3.2 ISO in message #131 of the "MFSTools 3.2" thread. I've tried both mfstool copy -ai /dev/sda /dev/sdc and mfstool copy -a /dev/sda /dev/sdc.

    Western Digital Data Lifeguard has reported no errors on the drive. I've also tried zeroing the entire drive using the tool.

    What works: TiVo boots new drive correctly. I can tune to HBO with my Cablecard. All my shows are intact.

    Problem symptoms: There is no guide data and I cannot retrieve any.
    • System Information shows the TiVo Service Level to be "A" when it should be "C". My service number is displayed correctly.
    • When I connect to the Mothership, I get "There was an error loading series data."
    • When I hit the Guide button, I get "Please activate service. Your service is not currently active. (T63)". There is a URL to activate service, but using that results in a message that the TiVo is already active.
    What I've tried, to no avail:
    • Connecting to the Mothership six times.
    • Letting the new drive run in the TiVo overnight, then attempting to connect to the Mothership.
    • Clear Program Information & To Do List.
    • Kickstart 57 - Results in endless reboot loop.
    • Kickstart 58 - Results in endless reboot loop.
    Can anyone offer any advice? I've spent my whole weekend on this. Thanks!
     
  2. jmbach

    jmbach der Neuerer

    3,130
    463
    Jan 1, 2009
    I would make a copy of your working drive using a drive duplicator or dd. Make sure it boots fine and works getting updates. then run KS 58. If it completes successfully then run KS 57. If that completes successfully then use MFSTools to copy over to your 2 TB drive.



    Sent from my SM-G950U1 using Tapatalk
     
    supasta likes this.
  3. supasta

    supasta Active Member

    3,029
    23
    May 6, 2006
    Colorado
    I have found myself in the same exact situation.

    I recently upgraded my failing TiVo Roamio Pro drive to a 4TB WD Red.
    I noticed that daily calls were failing. I forced connections several times. Each time it would get to 98% and then fail with the message "There was an error loading series data."

    I was out of town for a few days, so I disconnected the ethernet cable and let it sit for a few days to chew through the data, as TiVo suggests on their official help pages. Returned today, and cannot complete the connection.

    My symptoms are exact as the OP:
    • System Information shows the TiVo Service Level to be "A" when it should be "C". My service number is displayed correctly.
    • When I connect to the Mothership, I get "There was an error loading series data."
    • When I hit the Guide button, I get "Please activate service. Your service is not currently active. (T63)". There is a URL to activate service, but using that results in a message that the TiVo is already active. (I have only seen this once today).
    I am currently in an endless Kickstart 57 reboot loop.

    Any help is greatly appreciated! I will be re-installing the factory drive now and ensuring it updates and completed KS 58 and KS 57 on that drive, as suggested by jmbach.
     

    Attached Files:

  4. supasta

    supasta Active Member

    3,029
    23
    May 6, 2006
    Colorado
    Small update:

    I entered KS 51 in an attempt to grab the latest update, thinking that might be the cause of my problems (I have been reading some about the latest update causing issues, all of which I was also having: missing channel icons, missing artwork, skip missing, etc.)

    I saw a quick update screen, about 20 seconds. Then the unit went back into the reboot loop. During this time I read jmbach's post in another thread discussing the same issue where it is mentioned that a KS 58 fixed the problem. In my impatience, I threw a KS 58 at the unit during the next reboot in the loop. Well, it is not "stuck" at the GSOD. I have my fingers tightly crossed that this is the step that works. I would really hate to have to go back to step one.

    (ETA: Link to referenced post in another thread.)
     
    Last edited: Jun 16, 2018
    23adrock likes this.
  5. supasta

    supasta Active Member

    3,029
    23
    May 6, 2006
    Colorado

    Advertisements

    Second (hopefully final) update:

    KS 58 appears to have worked. The GSOD stayed for less than 60 minutes (guessing, I was watching a movie on the Chromecast and flipped back to check it and it was at the TiVo Home screen). This was far less than the 3 hours the message displays.

    The TiVo was about 60% through a connection. It hung at 99% for some time, then the magical word "Done" displayed. All appears to have been corrected. The TiVo has all guide data, and all of the other previous issues are corrected (channel icons, skip missing, artwork, etc.)

    As with the first upgrade, a big shout-out to jmbach for the endless information and help. Had I not read your post referring to KS 58, I would have been pulling the drive and starting the overwrite, and was considering a full reformat - something I was really wanting to avoid!
     
  6. whatnot27

    whatnot27 New Member

    3
    1
    Apr 23, 2018
    I failed to connect to mothership for 30 days following an -ai drive upgrade on the Roamio Plus from 1 TB to 4 TB. I was getting error S303. Guide data was still there, which is why I hadn't realized it wasn't connecting. Only other issue I had was a broken OnePass that didn't work and couldn't be deleted. I tried a KS 58 after much reading on here and it fixed all my issues. I never got a GSOD, only a screen about TiVo upgrading. Thanks to the community!
     
    supasta likes this.
  7. mmartz

    mmartz New Member

    17
    1
    Dec 17, 2007
    Every single detail was exactly the same for me:
    • Roamio Plus
    • used -ai flag
    • 1 -> 4 Tb
    • S303 error after 30 days
    • KS 58 - no GSOD, but a reboot and a message about installing an upgrade
    • Finally a successful connection
     
    Last edited: Jun 16, 2018
    supasta likes this.
  8. supasta

    supasta Active Member

    3,029
    23
    May 6, 2006
    Colorado
    I am curious if it is the -ai flag that is causing this, or if KickStart 58 should just be included in the standard Roamio upgrade procedure.

    My Roamio has been working flawlessly since my upgrade (nearly three months ago). It performs better, the menus are faster, reboots are faster (I had to do a few of those to get my Mini to play nice again), and nearly 100% of my stuttering video and audio dropouts have resolved.
     
  9. Oct 9, 2018 #9 of 11
    jerrythea

    jerrythea New Member

    2
    0
    Oct 5, 2018
    I had an almost identical issue.
    I had upgraded to a 3 TB WD Red (not Red Pro).

    Everything was perfect.

    Checked this morning, and it couldn't update software.

    I did a KS58, which took less than 5 minutes.

    Everything is perfect again.
     
  10. 23adrock

    23adrock New Member

    1
    0
    Mar 3, 2019
    Nearly identical for me too. Roamio 500 GB upgrade to WD Red 3GB. Kept recordings with MFStools -ai flag. S303 error and couldn’t connect to mothership. Fixed with kickstart 58. Thanks to everyone who posted this solution !!
     
  11. tkrotchko

    tkrotchko New Member

    12
    5
    Jun 7, 2007
    I upgraded my HD on a Roamio using MFSTools 3.3 and had the dreaded S303 error. I didn't realize I had it for over two weeks until we got the pop up that the schedule would not be valid in 2 days.

    I had a little trouble flipping it into Kickstart mode, but I finally managed to invoke a Kickstart 58 (instructions here: TiVo Kickstart Codes and Information) and it lasted, no exaggeration 3-4 seconds, it immediately went into a software update mode and then it tried itself to update. Loading two weeks of data took it quite some time, but eventually it worked.

    I'm not sure why it did the software update thing, but hopefully it's working properly now.
     

Share This Page

spam firewall

Advertisements