I have a Linux-based workstation that is already configured for my needs, but I also needed to replace the disk drive on my Tivo Series 3 (Model TCD652160) using MFSTools 3.2, which is a Linux-based OS designed to copy/create the new Tivo drive. The OS of the Tivo3/HD limits the maximum size of the drive to 2TB. It appears that the Romio has a 6TB limit.
Details and download links for MSFTools 3.2 can be found at this link to the MFSTools discussion at TivoCommunity.com. The images were created with OpenSUSE Leap 42.1 and the available images there are:
The MFSTools commands and options are detailed on this page. When I find some examples of how to use them, I'll link to them here.
If you just wish to make a bit-for-bit copy of your drive with updated status:
$ dd if=source_drive of=target_drive status=progress
Since a VirtualBox *.vmdk image is provided, I tried to use that image with VirtualBox, which is already installed on my workstation, creating a new VM named MFSTools_3.2. I had issues with the MSFTools vmdk file not being able to load it's initrd image. No problem, I just configured the VM to boot from the ISO image.
The problem was how to make the source and target disk drives available to MFSTools and keep MFSTools away from the workstation's disk drives. I can connect the source and target drives as USB devices, but I need them to be accessible as a raw disk device to allow MFSTools to work its magic. The solution is to make *.vmdk files that link to each drive in raw mode.
But before I do that, I added myself to the disk group in /etc/groups, logged out and then logged back in. This is necessary to use the following VBoxManage commands as a regular user. Otherwise, you will need to be the super user and run VirtualBox as the superuser which is not considered a good idea at all.
I used two USB drive adapters to connect the disk drives to my workstation. Watching the output of dmesg as I connected first the source drive and then the target drive revealed that they were seen on my system as /dev/sdk and /dev/sdl respectively. Your results will vary.
The *.vmdk files pointing to the raw disks are created as follows:
$ VBoxManage internalcommands createrawvmdk -filename /path/to/source_sdk.vmdk -rawdisk /dev/sdk
$ VBoxManage internalcommands createrawvmdk -filename /path/to/target_sdl.vmdk -rawdisk /dev/sdl
The path I used was the path to the MFSTools virtual machine I had created in VirtualBox using the downloaded MFSTools_3.2_openSUSE_Leap_42.1_JeOS.x86_64-1.0.4.vmdk (actually, I had to use the ISO image instead).
In the VirtualBox details, add source_sdk.vmdk and target_sdl.vmdk as hard drives.
Then start the VM which prompts you for a login and password, which will be root and tivo, respectively.
Your source disk will display partition information and other details if queried with
# mfsinfo /dev/sda
Your target drive, which is likely unformatted, will not display this information. This process will make certain that you have correctly identified which disk is the source and which disk is the target.
The current version of MSFTools will copy and expand all in one operation, so enter (in my case)
# mfstool copy -a /dev/sda /dev/sdb
and wait patiently as the process unfolds; it takes a while.
If you run into trouble, search the many posts about MFSTools at TivoCommunity.com.
As always, your comments are welcomed.
RESOURCES
Backup, Upgrade, Add, or Replace TiVo drive using MFSTools
Hinsdale How-to TiVo Upgrade - MSFTools 2.0
VirtualBox Tips and Tricks
Boot your USB Drive in VirtualBox
TivoCommunity
Tivo 2/3 Bad Power Supply Capacitors
WinMFS Quickstart Guide
How to Upgrade the HDD in your TiVo Series 3 with WinMFS
Reformat large (4TB - 6TB) Roamio drives
Details and download links for MSFTools 3.2 can be found at this link to the MFSTools discussion at TivoCommunity.com. The images were created with OpenSUSE Leap 42.1 and the available images there are:
MFSTools 3.2 ISO Live ISO
MFSTools 3.2USB/HD Use dd in Linux or something like HDD Raw Copy Tool in Windows to copy the uncompressed file to a USB or hard drive.
MFSTools 3.2 VHD For use in Hyper-V
.MFSTools 3.2 VMX For use in VMware/VirtualBox.This method is pretty simple if you have a dedicated machine. Just install the disk drives as hda/sda and hdb/sdb and use your CD drive at hdc/sdc, but I don't have that luxury.
The MFSTools commands and options are detailed on this page. When I find some examples of how to use them, I'll link to them here.
If you just wish to make a bit-for-bit copy of your drive with updated status:
$ dd if=source_drive of=target_drive status=progress
Since a VirtualBox *.vmdk image is provided, I tried to use that image with VirtualBox, which is already installed on my workstation, creating a new VM named MFSTools_3.2. I had issues with the MSFTools vmdk file not being able to load it's initrd image. No problem, I just configured the VM to boot from the ISO image.
The problem was how to make the source and target disk drives available to MFSTools and keep MFSTools away from the workstation's disk drives. I can connect the source and target drives as USB devices, but I need them to be accessible as a raw disk device to allow MFSTools to work its magic. The solution is to make *.vmdk files that link to each drive in raw mode.
But before I do that, I added myself to the disk group in /etc/groups, logged out and then logged back in. This is necessary to use the following VBoxManage commands as a regular user. Otherwise, you will need to be the super user and run VirtualBox as the superuser which is not considered a good idea at all.
I used two USB drive adapters to connect the disk drives to my workstation. Watching the output of dmesg as I connected first the source drive and then the target drive revealed that they were seen on my system as /dev/sdk and /dev/sdl respectively. Your results will vary.
The *.vmdk files pointing to the raw disks are created as follows:
$ VBoxManage internalcommands createrawvmdk -filename /path/to/source_sdk.vmdk -rawdisk /dev/sdk
$ VBoxManage internalcommands createrawvmdk -filename /path/to/target_sdl.vmdk -rawdisk /dev/sdl
The path I used was the path to the MFSTools virtual machine I had created in VirtualBox using the downloaded MFSTools_3.2_openSUSE_Leap_42.1_JeOS.x86_64-1.0.4.vmdk (actually, I had to use the ISO image instead).
In the VirtualBox details, add source_sdk.vmdk and target_sdl.vmdk as hard drives.
Then start the VM which prompts you for a login and password, which will be root and tivo, respectively.
Your source disk will display partition information and other details if queried with
# mfsinfo /dev/sda
Your target drive, which is likely unformatted, will not display this information. This process will make certain that you have correctly identified which disk is the source and which disk is the target.
The current version of MSFTools will copy and expand all in one operation, so enter (in my case)
# mfstool copy -a /dev/sda /dev/sdb
and wait patiently as the process unfolds; it takes a while.
If you run into trouble, search the many posts about MFSTools at TivoCommunity.com.
As always, your comments are welcomed.
RESOURCES
Backup, Upgrade, Add, or Replace TiVo drive using MFSTools
Hinsdale How-to TiVo Upgrade - MSFTools 2.0
VirtualBox Tips and Tricks
Boot your USB Drive in VirtualBox
TivoCommunity
Tivo 2/3 Bad Power Supply Capacitors
WinMFS Quickstart Guide
How to Upgrade the HDD in your TiVo Series 3 with WinMFS
Reformat large (4TB - 6TB) Roamio drives
Comments