Separate names with a comma.
Discussion in 'TiVo Upgrade Center' started by jkozee, Jun 4, 2015.
I don't understand the question.
Updated the settings per recommendation.
Created new Virtual box with the MFSTools iso marked as a Live CD, changed OS type to SUSE-32bit. Mounted ggieseke's Tivo HDD image, started the machine, attached the USB dock/new drive. Identified drive names.
Running mfstool copy /dev/sdb /dev/sdc
Still hitting the same error types as before:
percentage ticks up, then pauses for a while, then kicks out the following text before repeating the pattern:
[####.###...] usb 1-1: stat urb: killed, stream 0
Copying ### of m235 MiB (X.xx%) 1MiB/sec (ETA X:xx:xx)
Continuing to allow it to run, at just north of 9% now. Will update when it's done. Any ideas/help is appreciated.
That is apparently a Linux kernel error with the uas module and some chipsets when connected to a USB3 port commonly. (Although some USB2 can apparently have this issue.) Is the USB drive connected to a USB3 or a USB2.
It did, sadly, fail again.
The dock is sold as USB3.0, but my MacBookPro is only 2.0.
Micro Center - Computers and Electronics
MacBook Pro (15-inch, Early 2011) - Technical Specifications
So, it's at best a 2.0 connection, but it definitely could be an issue if the USB3 technology is not supported.
I'm not sure what would be the best next step. I'm not a hardware expert. Casual browsing shows the majority of available SATA/USB docks are now 3.0. I could try to rebuild another similar setup on my Mac mini, or the (loaned to me) Windows 10 laptop, but they are also USB2 max. Is it just a perfect storm of USB3 dock, my MBP chip, and another machine might fare better? Suggestions welcome.
Can you use a different computer?
There is a way of "turning" that module off. Let me do some research on that.
jmbach, things worked out great, thank you
I followed everything I had mentioned in post
MFS Tools 3.2
The only thing I had wrong was disk, it is fdisk
Took about 2.5 hours for the copy to complete
Thank you so much!
Yep. It's worth a try. I have a Mac (mini) running same OS, but a little older. Should have a slightly faster, and different processor (2.4 GHz Intel Core Duo, over 2.2 Intel Core i7); and a loaned Dell (running Windows 10). Can see if either of them have better luck/forgiveness with the USB3. Will probably get to try one of them tonight, but not both if unsuccessful.
The owner of my loaner PC also has a dock, allegedly both with USB3 and eSata. If I can borrow that, i think his laptop has eSata too, but may not be able to retrieve the hardware immediately.
If that doesn't work, my next ideas would be to try A) move over to DVRBARS software and try to restore the image using that instead. B)Use the dual-bay drive to try and clone the old (questionable) 320GB drive to the new 2TB one. (if I'm reading the forums right, there are other tools available to expand the drive afterwards), or C)try to find an older USB2.0-IDE/SATA adapter cable at retail.
If the different computers or Docks do not work, then we can try to disable the uas module.
I will have to work on updating the kernel it is compiled on as the issue is supposedly fixed on newer kernels.
Two changes to my setup:
re-created the same Virtual Box machine on the borrowed Windows 10 laptop, with one additional change, updated the Virtual machine's USB adapter settings for USB 3 (even though the computer doesn't have 3, i figured nothing to lose).
Ran copy the exact same way as before, and.... zoom. That counter went up like a rocket compared to prior attempts. None of those stream kill errors. It did take a long pause around the mid 70s % (right about where the prior attempts failed) but resumed and appears to have completed cleanly.
The new drive is installed in the Tivo, and so far so good. It wouldn't let me bypass Guided Setup or network selection, so it took a few hours to update, Clear & Delete, re-update, but aside from calling Verizon to re-pair the CableCard (to get premiums back) all was working as of late last night.
Urgency isn't really an issue for me at the moment, but I sincerely appreciate the offer to dig into the kernel and module. Considering all the help I got, I'd still like help figure out if it was the Mac, the USB setting, the dock, etc, but I will have to pick up another new drive for that. Long term plan is to upgrade my XL4 as well, so I'll probably give this another go in a couple of weeks. The fan in the (now working) box is old and noisy, so that'll be replaced soon too.
How do you decompress the USB/HD file in Linux. I use the command tar -zxvf MFSTools_3.2_i586.i686-0.0.33.oem.tar.gz and it left me with a file named MFSTools_3.2_i586.i686-0.0.33.raw.
What the heck is a .raw file and where do I go from here?
Use dd to copy the raw file to a USB or hard drive. The raw image is the actual drive image.
Sorry to be so dumb, but what is the command?
I tried dd if=/video/6tb/MFSTools_3.2_i586.i686-0.0.33.raw of=/dev/usb and it seems to copy but the usb drive doesn't work. By don't work I mean I can't boot to the USB drive.
The image is in /video/6tb and I have mounted the usb drive on /dev/usb
That should do it. Do you need to change BIOS settings to boot off of a USB drive?
Also you may have to allow legacy booting.
Looks like it was how I formatted and mounted the SD card. I ended up using Windows and all is working now.
I upgraded my Roamio Pro with a 6TB drive with msfr when it first came out, and the drive is now about 60% full since I use my Roamio as my main media server for movies. I'm interested to upgrade to a 8TB but don't want to lose all my recordings. Just so I correctly understand what MFS Tools 3.2 can do:
-I can back up my 6TB image to a new 8TB drive?
-I can then expand the 8TB backup to be able to use the full 8TB capacity when put in the Roamio Pro?
And on the Roamio side:
-If something goes wrong with the 8TB drive, I can still put original 6TB back in and all my recordings there will still be preserved?
-I won't need to re-pair my cable card when swapping between the 8TB and 6TB drives?
-The images are tied to that specific Roamio Pro, so I won't be able to put them in another Roamio if I have a hardware failure?
Until TiVo fixes the 64 bit bug in their OS, none of that can be done by MFSTools. The max it can go is 4TB. ggieseke is developing a program that will be able to do what you are wanting.
Yes you will be able to put back the 6TB and still have all your recordings. The cableCARD pairing should remain as long as you have not re paired it with another drive or booted the TiVo without the cableCARD inserted.
Since the Roamio auto formats the drive, you can reuse the drive in another Roamio, you will loose all recordings when you do.
Does anyone know how to set the file system so that it no longer triggers a GSOD at boot?
I had copied a 2TB to a 4TB back in September, however I just noticed that the guide data was not downloading at all. I tried a series of fixes and eventually did the old kickstart 57 which put me into a reboot loop. I still have the drive from September, but am attempting to preserve as much as I can. So far I don't see the disk as being bad based on the diagnostics.
On the MS OneDrive host for the ISO image is there a hard 30min timeout to finish the download? I was downloading on a slower connection and it consistently hung at around 94% (as in the server stopped responding). I ended up downloading the ISO from a faster connection remotely, then retrieving it from there.
Not that I am aware of.
I am trying to help a friend repair a Premiere with a failing 320GB HDD. I have purchased a WD Green 2TB drive for him. I was able to create a backup using dvrbars. I restored the backup to the new 2TB HDD. Can someone help me with the MFS Tools command to supersize the drive to use all of the 2TB? The only info I have found is how to do a copy from the source to a target (which I will do if this doesn't work). I was worried that the bad sectors on the 320GB HDD would fail the copy.