Separate names with a comma.
Discussion in 'TiVo Upgrade Center' started by jkozee, Jun 4, 2015.
You can follow the 6TB Premiere instructions to use MFSTools 3.2 or just use JMFS.
I'm in the process of copying my Premiere's previously upgraded 2TB drive to a 6TB drive.
I've been getting 28 MiB/sec on one machine with USB 3.0 (New MacBook Pro Using Parallels VM USB 3.0 enabled)
on another I've gotten 25 MiB/sec. (Dell Laptop with USB 3.0)
These speeds seem very USB 2.0-ish.
Has anyone validated that this ISO has USB 3.0 enabled on it?
What macOS version are you using? Are you using MFSTools of JMFSTools? I have been trying to get the drives recognized on JMFSTools under El Capitan inside of a VM but no luck so far.
I'm using the Same OS. I booted Parallels with the ISO from here: MFS Tools 3.2
Thank you. I will try MFS Tools as JMFS 1.04 is not helping at all.
It is inherently slower because it rebuilds the inodes when it copies because it expands the two original MFS media partitions. So if you started out with a 2TB Premiere image that was previously expanded using JMFS resulting in 15 partitions, the new image after an MFSTools copy would be 14 partitions.... as long as you stay at 4TB or less. When creating a 6TB Premiere image, you will end up with 15 partitions again.
I am not sure about the speeds, I know that it took 3 to 4 days to copy a completely full 2TB image to a 4TB drive via a USB3 dock.
I am pretty sure USB3 drivers are on that iso. Will have to check to be sure.
Ok, so anyone else having the same experience can know what I did. Turns out that we were using a Thermaltake USB 3 dock for our SATA drives as we wanted to have just one port used. It happens that particular device is not supported by the Linux distribution on the ISO image. Only one of the drives shows up as active at a time. The solution was to install a later version of Linux, in our case we decided on Ubuntu 16.10, and both drives then show up. Compile MFS Tools 3.2 from source and presto, the system works. We can now see both drives on a virtual machine, Parallels, Fusion or even VirtualBox running inside of macOS, no matter the version, even Sierra works. We are peaking at 33MiB/s . We are upgrading a Premiere 4 from the original 500 GB drive to a 4 TB drive.
Just a follow up as I was hoping to do a similar upgrade to my Roamio plus (500GB drive) to a larger drive. Had a couple follow up questions:
1) With the step by step copy commads described by dmark1867 on November 14, 2016 and confirmed by jmbach, will my recordings be copied from the original drive to the new drive?
2) What is the largest drive I can put into the Roamio while still keeping my existing recordings?
Thanks so much!!
As long as you use the -a switch your recordings will be copied.
The largest drive you can use in the Roamio using this method is 4TB.
Thanks for the response. Just to be clear for me as a noob with the tool. On the syntax I saw in the post I was referring to, he had an '-ai' switch. Is that really an 'a' and an 'i' as separate switches stacked up or is 'ai' a completely different switch than the 'a' and i should use just the 'a' you mention?
The switches are stacked. I use -ai because it includes everything. The -a is for all your recordings. The -i copies all non MFS partitions not just the necessary ones.
Thanks again jmbach. I hope last questions...
1) Will the syntax I saw earlier from dmark1867 that we have discussed the 'a' vs 'ai' switch also serve to let me use the full 4TB capacity of the new drive if I went with 4TB? (syntax I'm referring to: mfstool copy -ai /dev/sda /dev/sdb)
2) What is the consensus on the best WD drive these days as I have seen both the purples and reds mentioned here in the forum and online?
Either switch would work to let you use the full 4TB capacity. The only difference is that you include all non MFS partitions in the copy process with the -i switch which adds maybe 10 minutes to the copy.
I use only WD Red drives and have not had any issues in the 4 units I have.
jmbach, do I need to copy these non MFS partitions over for some purpose, or can I stick with the -a switch and call it a day? Appreciate the detailed responses so far!!
I am not sure. Some people has had some issues with guide data after a copy. I don't know if it is because they did or did not use the -i switch. I have used it for all my copies and had no issues. The issue clears up after deleting guide data and connecting to the TiVo servers a couple of times.
Curious, when I have mfsinfo print out the partition table on the stock 3TB drive it is able to do it.
When I try it on a 6TB drive that is formatted by the roamio pro (prior to mfsr reformatting), it comes back with a checksum error.
Is that expected behavior?
Yes. It is because of the bug in the OS. I hope I get this correct as it has been a while since I had discussed it with ggieseke, but when the TiVo boots, it calculates some values of the MFS and stores them. In a 6TB these should be all 64bit numbers but one of these are saved as a 32bit number. This is why you get a small recording space displayed on the System Information screen. Consequently, when MFSTools checks everything, it does not add up correctly and why MFSR is needed.
jmbach, I received my 4TB Red in the mail today and am performing the extended test on the WD Data Lifeguard software (which has 8 hours to go...joy). When I was looking on the WD support page for this drive, they also have this WD5741 utility as a firmware update that has the following description:
"This utility modifies the behavior of the drive to wait longer before positioning the heads in their park position and turning off unnecessary electronics. This utility is designed to upgrade the following hard drives: WD RED 3.5" Drive"
Is this something I need to run before doing the MFS Tools drive copy or is this not necessary for Tivo drive purposes?
Most Red drives don't need WD5741 these days, but I did get a 4TB Red several years ago that was set to 8 seconds. It was running NASWare 2.0 and I haven't seen any 3.0 drives that need it.
Ok. Thanks for getting back to me.
So if this is a recently manufactured drive and I've completed the extended data lifeguard test with no issues, I can just proceed with the copy process?