Separate names with a comma.
Discussion in 'TiVo Upgrade Center' started by jkozee, Jun 4, 2015.
If you are working on a Roamio you will have to use MFSTools 3.2.
So I blanked the new drive, re-copied, put the 2tb in, and got the same results. This time, as recommended, instead of redoing guided setup, I did a C&D Guide Data.
I'm currently past hour two of being stuck at the C&D Guide Data screen, and I don't hear any hard drive thrashing. I'm going to give it a little bit more time, but I'm guessing that this is a bust as well.
I very purposefully waited for the new tools to be used on several Roamios before my own, so I knew they were mature and that I would have a good chance of making this work. I'm really disheartened here. Copying shows through the GUI is going to be a monster PITA if that's my only option now.
Does the ISO contain the stuff to mount partitions and look at the logs to see what's going on? Any advice on which partitions to mount AFTER a 3.2 mfscopy?
The ISO has whatever comes with a standard SUSEStudio ISO with compiled MFSTools 3.2. Since the \var partition is an ext3 (I think) partition, you should be able to mount it. Telemark probably can give you much better guidance than I can.
Does MFSTools read the drive you create okay? Might use MFSTools to check the image as well. Perhaps try the copy without the 'i' switch. Not sure why it is not working for you. This would be more of a jkozee question.
So unfortunately I completely screwed up, and instead of copying 6 log files out of /var, to a directory on my USB stick, I wrote over the same file on my USB drive 6 times. After that, I zeroed the header and let Roamio format it as a test for my backup plan. Today has not been my day.
All I can tell you is that in the tverr log, it repeatedly referenced a missing mfs file number that it was trying to delete, and 5 other file numbers indented under the first that it was also failing to find and delete. It repeated this for the 4 hours I let the C&D Guide Data run before I pulled the plug.
jmbach: The Linux ISO doesn't even acknowledge the partitions (they don't show up in /dev) unless I run a mfsck -r on the drive. Then they list. That was the only way I could mount the tivo /var partition - I had to run mfsck first for the partitions to pop up.
I'm currently investigating my backup plan, which was to get pyTiVo running and start backing everything up. If I can't figure out a working MFSCopy method, I'll have to zero the drive header, have the Roamio format the drive, redo GS and pairing all over again, and transfer everything back through pyTiVo. I'm really not looking forward to that, and my confidence that the metadata from some of my years-old shows will actually copy over is extremely low.
If anyone thinks the log files will help figure out my MFSCopy nightmare, I'll go through the 6-hour copy process again and pull the logs properly this time. If anyone has any other ideas (I know I'm running out), please let me know.
I can look through the logs. If you just want to do a quick copy, you can omit the -a to create a 'truncated' copy. This *should* include the minimum mfs data without the recording streams and should be rather quick.
Couple of other notes.
The -i flag incudes the 'alternate' boot/kernel/root set. Not required on the Roamio as the primary and alternate boot/kernel/root partitions live on the mmca. But, very useful for 'customized' partition layouts on hacked units.
The linux kernel is not aware of the TiVo modified Apple Partition format, so 'mfsk -r /dev/sdaX' is required to revalidate the drive to the kernel before you can mount it. This is similar to the 'tivopart r /dev/hdX' previously required.
TiVo migrates more items from the MFS to the SQLite partitions with each new SW version, so the -d option should be used with caution.
I don't think I've personally tested on anything later than 20.4.5c, but I do have a unit running 20.5.2b.RC1-USA-6, which is what you appear to be running, so I can see if I can reproduce your issue.
I don't mind trying to help troubleshoot, but I'd need some additional info and access to some of your files. I'll PM you.
Check your PM.
My sincere congratulations to all the MFSTOOLS developers for a job very well done. I've now successfully used MFS Tools 3.2 to
migrate two Roamio Basics to larger (2TB) hard drives, with no loss of recorded shows and no adverse impact to existing Cablecard
activation. It was relatively painless.
In both cases I used jmbach's posted 3.2 LiveCD ISO, which makes it quick and easy.
Both copies took ~3:15 to complete,using internal SATA-SATA.
The only adverse consequence I saw was the complete loss of Guide data in both cases, which was ultimately restored
with 3-4 trips to the mothership.
I haven't yet deduced why the Guide info is lost, as MFSTools seems to result in a complete bit-bit copy of the data on the hard disk.
...Perhaps someone wiser than I will enlighten me.
Hey txdmts, thanks for the info. Would you mind showing all of the command text of the code you used to do the drive to drive copy?
Also, how did you restore the Guide data?
As discussed, MFSTOOLS was used to migrate two Roamio Basics to larger drives.
In both cases, I zeroed the dest drives first (via WD Data Lifeguard 5.22).
On the first Roamio, choosing to err on the side of caution, I used the more generic command:
"mfstool copy -ai /dev/sdb /dev/sdc"
where (in my case) sdb-> source, and sdc->destination.
This worked great, but took two trips to the mothership to get guide data back.
On the 2nd Roamio, in light of jkozee's 11/16 comments in post #186, I chose
"mfstool copy -a /dev/sdb /dev/sdc"
This worked just as well, but it took 4 trips to the mothership to restore all the
guide data properly. We can speculate about the significance (or lack thereof)
of that result.
Whichever of the two copy commands you use, upon bootup the Roamio takes
awhile to sort things out, but it eventually does, then it asks to access Tivo,
which I let it do.
As for restoring the guide data, I chose the simple route. I just kept sending
it back to the mothership until the guide data was restored:
Settings>Network>Connect to Tivo Service Now
Eventually, this works.
Had that not worked, I'd have probably done this:
Settings & Messages>Settings>HELP>RESTART OR RESET->
->"Clear program information & To Do List"
As a last resort, I'd probably have repeated Guided Setup, which
supposedly doesn't affect existing cablecards/Tuning Adapters or recordings.
Settings & Messages>Help>Restart or Reset>-> Repeat Guided Setup
Good Luck -
May the Force Be With You
Thanks for the detailed drive copy info txdmts.
I'm going to try method one. My main objective is to avoid having to repair the cable card after the drive upgrade. It seems that both of your upgrades kept the cable card pairing data.
Apologies for this newbie question, but my home computer's a macbook pro. Can MFS Tools run in OS X?
MFS Tools runs in Linux from a boot CD or USB stick. It is OS independent the Question is can your Macbook boot from the Linux CD.
The MBP hardware can boot from a Win7 CD/DVD, so it's kinda 'universal' in that respect. Also, OSX is, essentially, a type of Linux; I suggest it's likely MFS Tools can boot. Easy enough to find out. Burn the disk, load it, hold down the Option key during boot, select the MFS Tools CD as the boot device. It either boots or it doesn't. There's no downside to trying it.
The bigger issue is, how are you going to hook two drives to it? Assuming it boots, you'll have to go USB since it's a certainty it won't support the Thunderbolt port. The newer MBP's have USB3 and that should be pretty fast, but it will take FOREVER if you have an older device that has USB2.
Same -- back up and running on a 2GB drive. Great forum. I might suggest modifying the original post in this thread to include the most common commands for quick cloning, and a valid link to the .iso if that is permitted.
Seems that the SQLite partition (/dev/sdx14) is not being included during a copy because I declared skipdb incorrectly in copy.c. It should be:
unsigned int skipdb = 0;
unsigned int skipdb = 0;
Does it mean we should hold off on using MFS Tools for now until the bug is fixed??
Can you update your ISO?
Yes I can. Won't be able to do it until tomorrow at the earliest. jkozee may have some other updates to incorporate as well.