Originally Posted by mdkrough
My plan is to update to a 2.0TB drive on my TCD648250. Use JMFS to move up in 2 stages (using a 1.0TB drive as an intermediate step) so that I don't exceed the 1.2TB partition size boundary or the 16 partition limit. But reading some other posts, it looks like TiVo has upgraded it's Linux to a kernel that doesn't crash on partitions bigger than 1.2TB. Is that correct?
If I use WinMFS, I can use MFSadd and create a 1.6TB partition. Will TiVo work correctly with this larger partition?
Does this same process work on still larger drives? A 3.0TB drive? 4.0TB drive?
I went down that road with my first 652 (S3 HD), but it's no longer necessary, as has been pointed out, as long as you're running at least 11.0h, and by now you should have been updated to k and then to m.
Use WinMFs to copy the current drive to the 2TB.
When it finishes (and it may appear frozen for a while before it does--just leave it be and it'll get there eventually), it'll say you've got extra space and ask if you want to expand.
Tell it no.
Seriously, do not tell it to expand at this point.
You will have selected the original drive in order to be able to copy it.
Go back and now select the 2TB drive.
Go to File, mfsinfo, and make sure everything looks okay.
You could hook the new drive up in the TiVo to test it if you wanted to and come back to expand later.
But if you want to go ahead and do it now, you have the 2TB selected and you just checked with mfsinfo, now go to File, mfsadd to expand.
Why does it need to be done as a separate step? I do not know. I do know that sometimes doing as the final part of the copy process appears to work but actually doesn't.