TiVo Community
TiVo Community
TiVo Community
Go Back   TiVo Community > Underground Playground > TiVo Upgrade Center
TiVo Community
Reply
Forum Jump
 
Thread Tools
Old 06-04-2015, 09:28 PM   #1
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
MFS Tools 3.2

Announcing the release of MFS Tools 3.2!

"MFS Tools 1.0 was evolutionary in the TiVo upgrade process. MFS Tools 2.0 may prove to be revolutionary." I'll let you can choose your own adjective for MFS Tools 3.2.

Highlights
  • Supports Series 1 through Roamio (and perhaps beyond).
  • Backwards compatible with MFS Tools v1 and v2.
  • Supports 8 TB on Premiere (perhaps more, tested with dual 4 TB drives).
  • Supports 8 TB on Roamio (perhaps more, tested with dual 4 TB drives).
  • Backup and restore (or drive-drive using mfscopy) single or dual drive setups, and preserve recordings if you choose.
  • Supersize the drive, which can be reversed even after GSOD.
  • You can include the alternate boot/kernel/root partitions (useful for customized partition layouts).
  • Automatically includes required loopset files (you no longer need to use the -f flags during backup) when not including recordings (truncated backup)
  • Automatically prunes recordings when a truncated backup is done (sets the MFS flags to cleanup, so the unit will scan objects on startup)
  • Works on drives that have been marked for cleanup (GSOD).
  • Creates a new MFS structure, so drives that have been expanded by adding pairs can be consolidated to just two pairs, just like the original.
  • Restore to drives smaller than the original.

Overview
MFS Tools v3.2 is a set of utilities that allow one to backup/restore/copy/supersize a TiVo drive, without losing recordings, and to expand recording space to take advantage of larger drives. Additionally, there are options that allow more advanced features and finer grain control over the TiVo drive. For example, there are options to revalidate the drive to the Linux kernel, so the partitions can be mounted or copied. The ability to increase/decrease swap, var, SQLite partition sizes on restore. Limit the amount of used space of the drive, limit media partition size, add app/media partition sets, convert between 32-bit and 64-bit MFS layouts, etc, etc, etc. Please take the time to review all of the utilities and their options to fully appreciate what the tools have to offer.

Thanks
A special thanks to Tiger, the original pioneer of MFS. And to all those that contribute here and on other sites that have helped me get the most out of my TiVo units.

History (unverified)
Tiger released the original closed source project in 2001, followed by 2.0 in 2002. In 2004, he released the source code under GPL, and made it available on sourceforge, and announced that he had no plans to continue work on it. He hen returned for a three month period in 2005 and a two month period in 2008 to work on a major update to version 3, with some ambitious new functionality and 64-bit MFS support for the TiVo HD. It has remained in this untested, almost functional, but overlooked state since then.

I received a some anonymous patches that fixed a few bugs, added Premier handling, and got things mostly working one. Since then, I've refined the Premiere support, added Roamio support, added some new utilities, deprecated a few options and added a few more, and cleaned up and debugged the code a bit.

Although there are several new tools, features, options, etc., available in 3.2, there was a fundamental change in the the way the MFS is handled. A simplified explanation is that in v1, the MFS is treated as a whole, and the entire structure is duplicated based on the used blocks. In v3, the inodes and data is copied individually, and during restore the MFS structure is recreated, the inodes and data blocks are allocated, and the inode and data is copied to the new locations.

The downside is that v3 backup/restore is not quite as fast as v1. The upside is that the MFS Media Partitions can now be re-sized, which is a pretty big advantage. Because v1 copied all MFS pairs, the number of times a drive could be backed/restored and then expanded to take advantage of additional disk space was limited. With v3, the restore process creates a drive with only two MFS app/data pairs, just like the original drive, no matter how many pairs the original drive had. And yes, you can now restore to a smaller drive than the original drive (provided the smaller drive has enough space for the recordings or you truncate it).

Notes
Every effort has been made to keep these tools as robust as possible. I have done limited testing (confirmed boot/operation, but not filled drives to capacity) on units from Series 1 through Roamio. The tools can still backup/restore using the original v1 backup format, and should work with existing backups.

I have deprecated several options, and will probably deprecate more to reduce the number of options for novice users. Some of the deprecated options (and additional debug options) will still be available with custom builds.

I have only tested with drives up to 4 TB, but there's been mention of Roamios supporting larger drives with 20.4.6 or later. I was able to setup a Premiere with 8 TB (dual 4 TB drives), but had to limit the media partitions to 2 TB max. This unit passed a forced MFS fsfix scan (GSOD) without issue.

Todo
I still have a few things I would like to add, such as adding SW version, original swap/var/db size to the backup header (extrainfo). I would also like to do some testing with larger drives and additional units.

Known Limitations
Currently, the largest boot drive supported is 4TB (Premiere and newer, 2TB for THD). Backups of drives with the either of the first two app/media partitions is not supported.

Attachment
The iso image has been removed from sourceforge temporarily to address some of the issues reported in this thread regarding large drives.
Please go to sourceforge for the latest release.


Last edited by jkozee; 06-24-2015 at 10:03 PM.
jkozee is offline   Reply With Quote
Thanks For This Post:
Old 06-04-2015, 09:28 PM   #2
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
mfstool
Code:
Usage: ./mfstool <function> <args> or <function> <args>
Available functions:
  backup    Backup TiVo drive fast and small.
  restore   Restore mfstool backups to TiVo drive.
  copy      Copy TiVo drive to a new drive.
  add       Add partitions to your TiVo MFS volume.
  ck        Perform a simple consistency check on MFS.
  mls       List files in the MFS volume.
  supersize Supersize a TiVo drive.
  d         Dump raw data from MFS volume.
  info      Display information about MFS volume.
For help on a particular function: ./mfstool <function> -h
backup
Code:
Usage: ./backup [options] Adrive [Bdrive]
Options:
 -h        Display this help message
 -o file   Output to file, - for stdout
 -1 .. -9  Compress backup, quick (-1) through best (-9)
 -v        Do not include /var in backup
 -d        Do not include /db (SQLite) in backup (Premiere and newer)
 -s        Shrink MFS in backup (implied for v3 backups without -a flag)
 -F format Backup using a specific backup format (v1, v3, winmfs)
 -q        Do not display progress
 -qq       Do not display anything but error messages
 -t        Use total length of stream in calculations
 -T        Backup total length of stream instead of used length
 -a        Backup all streams
 -i        Include all non-mfs partitions from Adrive (alternate, custom, etc.) 
Available in deprecated/debug build only
 -f max    Backup only fsids below max
 -L max    Backup only streams less than max MiB
 -D        Do not force loopset and demo files to be added
restore
Code:
Usage: ./restore [options] Adrive [Bdrive]
Options:
 -h        Display this help message
 -i file   Input from file, - for stdin
 -k        Optimize partition layout with kernels first
 -r scale  Override v3 media blocksize of 20480 with 2048<<scale (scale=0 to 4)
 -q        Do not display progress
 -qq       Do not display anything but error messages
 -v size   Recreate /var as size MiB (Only if not in backup)
 -d size   Recreate /db (SQLite in source) as size MiB (if not in backup)
 -S size   Recreate swap as size MiB
 -l        Leave at least 2 partitions free
 -b        Force no byte swapping on restore
 -B        Force byte swapping on restore
 -w 32/64  Write MFS structures as 32 or 64 bit
 -c size   Carve (leave free) in blocks on drive A
 -C size   Carve (leave free) in blocks on Drive B
 -m size   Maximum media partition size in GiB for v3 restore
 -M size   Maximum drive size in GiB (ie lba28 would be 128)
Available in deprecated/debug build only
 -P        Do NOT optimize the partition layout
 -z        Zero out partitions not backed up
mfscopy
Code:
Usage: ./mfscopy [options] SourceA[:SourceB] DestA[:DestB]
General options:
 -h        Display this help message
 -q        Do not display progress
 -qq       Do not display anything but error messages
Source options:
 -t        Use total length of stream in calculations
 -T        Copy total length of stream instead of used length
 -a        Copy all streams
 -i        Include all non-mfs partitions from Adrive (alternate, custom, etc.)
Available in deprecated/debug build only
 -f max    Copy only fsids below max
 -L max    Copy only streams less than max MiB
 -D        Do not force loopset and demo files to be added
Target options:
 -s        Shrink MFS whily copying (implied for v3 copies)
 -k        Optimize partition layout with kernels first
 -r scale  Override v3 media blocksize of 20480 with 2048<<scale (scale=0 to 4)
 -v size   Recreate /var as size MiB and don't copy /var
 -d size   Recreate /db (SQLite in source) as size MiB and don't copy /db
 -S size   Recreate swap as size MiB
 -l        Leave at least 2 partitions free
 -b        Force no byte swapping on target
 -B        Force byte swapping on target
 -R        Just copy raw blocks (v1) instead of rebuilding data structures (v3)
 -w 32/64  Write MFS structures as 32 or 64 bit
 -c size   Carve (leave free) in blocks on drive A
 -C size   Carve (leave free) in blocks on Drive B
 -m size   Maximum media partition size in GiB for v3 restore
 -M size   Maximum drive size in GiB (ie lba28 would be 128)
Available in deprecated/debug build only
 -P        Do NOT optimize the partition layout
 -z        Zero out partitions not copied
supersize
Code:
Usage: ./supersize [Adrive [Bdrive]] [options values]
Options:
 -h        Display this help message
 -m        MaxDiskSize in KB (Default is 2147483647)
 -u        User SizeInKb in KB (Default is -1)
 -c        TivoClips SizeInKb in KB (Default is -1)
mfsadd
Code:
Usage: ./mfsadd [options] Adrive [Bdrive] [NewApp NewMedia]
Options:
 -h        Display this help message
 -r scale  Override media blocksize of 20480 with 2048<<scale (scale=0 to 4)
 -x        Create partition(s) on all drives
 -X drive  Create partition(s) on a specific drive
 -m size   Maximum media partition size in GiB
 -M size   Maximum drive size in GiB (ie lba28 would be 128)
 -f        Use with -m to fill the drive multiple media partitions
NewApp / NewMedia
  Existing partitions (Such as /dev/hda13 /dev/hda14) to add to
  the MFS volume set
mfsinfo
Code:
Usage: ./mfsinfo Adrive [Bdrive]
Options:
 -h        Display this help message
mfsck
Code:
Usage: ./mfsck [options] Adrive [Bdrive]
Options:
 -h        Display this help message
 -r        Revalidate TiVo partitions on Adrive [Bdrive]
Available in deprecated/debug build only
 -m [1-5]  Set volume header magic to OK, FS_CHK, LOG_CHK, DB_CHK, or CLEAN
 -e [1-3]  Set vol_hdr.v64.off0c to 0x00000010, TiVo, or Dish
mfsd
Code:
Usage: ./mfsd [options] Adrive [Bdrive]
Options:
 -h        Display this help message
 -f FSID  Dump a single FSID
 -F        Dump ALL FSIDs
 -i indoe  Dump a single inode
 -l log    Dump a single transaction log
 -s sector Read from sector, or from offset into file
 -c count  Read count sectors, where applicable
 -C        Perform consistency checkpoint before displaying data
 -H        Display in hex, no matter the format
 -b        Display in binary, no matter the format
 -x        Display formatted values in hex
 -z zone   Read from a single zonemap
 -Z        Dump ALL zonemap info
mls
Code:
Usage: ./mls [options] Adrive [Bdrive] <path|fsid>
Options:
 -h        Display this help message
 -l        long list (with size)
 -R        recurse


Last edited by jkozee; 06-09-2015 at 04:48 PM.
jkozee is offline   Reply With Quote
Thanks For This Post:
Old 06-04-2015, 09:29 PM   #3
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
(reserved for usage examples)

jkozee is offline   Reply With Quote
Old 06-04-2015, 09:29 PM   #4
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
(reserved for no good reason, pictures perhaps?)

Attached Images
File Type: jpg Premiere-4+4.jpg (43.9 KB, 88 views)

Last edited by jkozee; 06-04-2015 at 09:36 PM.
jkozee is offline   Reply With Quote
Old 06-04-2015, 09:58 PM   #5
Keen
Registered User
 
Join Date: Aug 2009
Location: Minneapolis, MN
Posts: 236
Holy crap, the day is upon us! A tool to upgrade a Roamio drive without losing recordings?! Huzzah!

I look forward to upgrading my Roamio to a 6TB drive down the road.

Keen is offline   Reply With Quote
Old 06-04-2015, 10:16 PM   #6
unitron
Registered User
 
unitron's Avatar
 
Join Date: Apr 2006
Location: semi-coastal NC
Posts: 14,778
Will this work with .bak files created by spike's MFS Live cd?

Will this create .bak files that can be used by spike's MFS Live cd?

__________________
(thisismysigfile)


"I am altering the deal. Pray I don't alter it any further."

Darth TiVo, 14 February, 2011
unitron is offline   Reply With Quote
Old 06-04-2015, 10:26 PM   #7
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
Quote:
Originally Posted by unitron View Post
Will this work with .bak files created by spike's MFS Live cd?
Yes. The mfslive cd is a MFS Tools v2 variant. It will NOT work on WinMFS backups, as those backups use a different file format.

jkozee is offline   Reply With Quote
Old 06-04-2015, 10:53 PM   #8
jmbach
der Neuerer
 
jmbach's Avatar
 
Join Date: Jan 2009
Posts: 1,109
Cool beans.

__________________
"Delay is preferable to error" - Thomas Jefferson
"If I have seen further it is by standing on the shoulders of Giants" - Sir Isaac Newton
jmbach is online now   Reply With Quote
Old 06-04-2015, 11:19 PM   #9
jmbach
der Neuerer
 
jmbach's Avatar
 
Join Date: Jan 2009
Posts: 1,109
Does this 4k align the zones and inodes.

__________________
"Delay is preferable to error" - Thomas Jefferson
"If I have seen further it is by standing on the shoulders of Giants" - Sir Isaac Newton
jmbach is online now   Reply With Quote
Old 06-05-2015, 12:01 AM   #10
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
Quote:
Originally Posted by jmbach View Post
Does this 4k align the zones and inodes.
No, or least probably not. The partitions are aligned on 4k sectors, but I haven't had time to investigate alignment of the internal mfs structures.

My initial impression was that 4k alignment of zones more involved than just aligning the mfs partition to 4k boundaries. There are other tools that offer this feature, so porting it to MFS Tools v3.2 is a matter of collaboration or reverse engineering.

I made a quick attempt at investigating other tools, but I was not able to use them as my test unit is not running 20.4.6 yet.

jkozee is offline   Reply With Quote
Old 06-05-2015, 12:07 AM   #11
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
FYI, I have had some PM's that I cannot reply to directly, because I have not met the minimum number of posts yet. I will address them in this thread, provided they are not personal and seem appropriate to the general discussion of MFS Tools. Otherwise, I will respond to PM's when I am "allowed" to. I will not release any names, and if I offend anyone, please let me know and I will remove the post(s).

jkozee is offline   Reply With Quote
Old 06-05-2015, 12:22 AM   #12
jmbach
der Neuerer
 
jmbach's Avatar
 
Join Date: Jan 2009
Posts: 1,109
Sourceforge seems to only have the original MFSTools documentation. Is there supplemental documentation on your iso for the new changes?

__________________
"Delay is preferable to error" - Thomas Jefferson
"If I have seen further it is by standing on the shoulders of Giants" - Sir Isaac Newton
jmbach is online now   Reply With Quote
Thanks For This Post:
Old 06-05-2015, 12:36 AM   #13
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
Quote:
If your tool creates a 14 partition image for 4TB, then you can easily take a premiere to 6TB by adding a 2TB coalesced partition at the end of the last partition and adding a 64bit entry to the APM to describe that partition. I think I am going to try that out.
A few things to address, and it will be from memory, so don't be surprised if I get it wrong and need to update this post later, or add some clarifications.

A coalesced partition is a single partition that masquerades itself as a app/media pair. It's been my experience that although this appears to work during the expansion, there is no guarantee that fsfix (GSOD) will complete, and from experience it will fail. So, from my experience, adding a coalesced partition is asking for trouble.

Additionally, adding a partition (or app/media pair) is not required for the initial restore. The entire drive will be used, and contain only 2 pairs, just like the original.

However, an unknown at this point is the 6TB drive. Indications are that the latest SW does not have limitations, but previous versions would not access a drive with partitions > 2TB, or at least did not begin above the 2TB mark.

MFS Tools 3.2 is aware of this issue, and will not create a media partition that begins above the 2 TB mark.

So, for example, with a 6TB drive will contain two pairs of app/media partions, but the first media partition will be < 2 TB to make sure that that second partition does not start above 2TB.

jkozee is offline   Reply With Quote
Old 06-05-2015, 12:39 AM   #14
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
Quote:
Originally Posted by jmbach View Post
Sourceforge seems to only have the original MFSTools documentation. Is there supplemental documentation on your iso for the new changes?
Nope, hence my request for help. However, all of the tools will report an accurate list of options, with at least some indication of what they do.

jkozee is offline   Reply With Quote
Old 06-05-2015, 12:39 AM   #15
ThAbtO
TiVoholic by the bay
 
ThAbtO's Avatar
 
Join Date: Apr 2000
Location: SF Bay Area
Posts: 5,499
TC CLUB MEMBER
Space! The final frontier! These are the voyages of MFSTools. To go boldly where no Tivo has gone before!

__________________
Series 2 (PLS, sold)
TiVo HD 1TB (157 HD Hrs, PLS, "652")
Roamio! Oh, wait, Its Juliet!
OTA! OTA! OTA!

~~~~~

The TiVo Apocalypse begins on Sat 2013 Feb 16 00:00 GMT!
ThAbtO is offline   Reply With Quote
Old 06-05-2015, 12:47 AM   #16
telemark
Registered User
 
Join Date: Nov 2013
Posts: 1,483
SourceForge is starting to die off.
http://www.itworld.com/article/29307...p-account.html
I'd suggest moving to a newer hosting company, perhaps github.

Welcome to the Roamio party.


Last edited by telemark; 06-05-2015 at 01:05 AM.
telemark is offline   Reply With Quote
Thanks For This Post:
Old 06-05-2015, 01:11 AM   #17
jmbach
der Neuerer
 
jmbach's Avatar
 
Join Date: Jan 2009
Posts: 1,109
Having an issue with the iso reading my 4TB correctly. It is seeing it as a 2TB. The drive is sitting in a USB dock connected to my laptop. My Linux Mint installation on the same computer reads it just fine. And it will not detect my 6TB drive at all whereas my Linux Mint installation does as well.

__________________
"Delay is preferable to error" - Thomas Jefferson
"If I have seen further it is by standing on the shoulders of Giants" - Sir Isaac Newton
jmbach is online now   Reply With Quote
Old 06-05-2015, 08:02 AM   #18
telemark
Registered User
 
Join Date: Nov 2013
Posts: 1,483
I'm hitting some bugs too, mostly around Roamio or large disk support.
Is there somewhere you want them reported, or somehow patched?


Last edited by telemark; 06-05-2015 at 08:12 AM.
telemark is offline   Reply With Quote
Old 06-05-2015, 08:54 AM   #19
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
Quote:
Originally Posted by jmbach View Post
Having an issue with the iso reading my 4TB correctly. It is seeing it as a 2TB. The drive is sitting in a USB dock connected to my laptop. My Linux Mint installation on the same computer reads it just fine. And it will not detect my 6TB drive at all whereas my Linux Mint installation does as well.
The boot cd is based on this distro. Perhaps there is an issue with th 32-bit build. Please try th 64-bit version there to see if it handles your drives correctly.

Also, you can copy the binaries off of the cd and try them on your Mint installation. Let me know the outcome.

jkozee is offline   Reply With Quote
Old 06-05-2015, 08:58 AM   #20
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
Quote:
Originally Posted by telemark View Post
I'm hitting some bugs too, mostly around Roamio or large disk support.
What issues are you seeing? Accessing the drive from the boot cd or the Roamio using the restored image?

What size drive are you using?

jkozee is offline   Reply With Quote
Old 06-05-2015, 10:03 AM   #21
telemark
Registered User
 
Join Date: Nov 2013
Posts: 1,483
Well I have a HDD library for development purposes so can test almost anything.
500GB, 1, 2, 4, 6TB.

I was testing a 4TB to 6TB internal Roamio expansion, but I guess that one is not supported out of the gate.

The other things are more minor:
Roamio formatted large disks are being rejected as invalid.
Roamio APM is being rewritten with deprecated fields.
pdisk* is overflowing 32bit values
segfault on missing args


Last edited by telemark; 06-05-2015 at 12:02 PM.
telemark is offline   Reply With Quote
Old 06-05-2015, 12:29 PM   #22
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
Quote:
Originally Posted by telemark View Post
I was testing a 4TB to 6TB internal Roamio expansion, but I guess that one is not supported out of the gate.
Restoring to a 4TB drive should work out of the gate, but I don't have a 6TB drive to test with. I've been told that it requires that the media partition not exceed 2TB, which would mean that it would take 3 app/media pairs to fill the drive. You would then need to coalesce the last pair to reduce the partition count to 15.

You could try limiting the restore to 2TB, then using mfsadd to add an aditional pair:
restore -m 2000 -i roamio.bak /dev/sdb
mfsadd -x -f -m 2000 /dev/sdb

You would then need to use pdisk to delete 15/16 and recreate 15 to include both partitions.
Quote:
Originally Posted by telemark View Post
Roamio formatted large disks are being rejected as invalid.
I've tested with 4TB drives, so I assume you mean that it is not recognizing drives created using mfsr. I'll have to update my Roamio to 20.4.7, so that I can take a look at the drives it creates. The first thing that comes to mind is that perhaps the inode/zone alignment is giving it troubles. Or perhaps I have wrong in the APM logic.
Quote:
Originally Posted by telemark View Post
Roamio APM is being rewritten with deprecated fields.
I'll have to take a look at this. I was mucking around with MAC_PARTITION vs TIVO_BIGPARTITION, so I may have gotten some things screwed up. What deprecated fields are baing written?
Quote:
Originally Posted by telemark View Post
pdisk* is overflowing 32bit values
I assume you're using pdisk_roamio for the drives. That comes from the TiVo pdisk64 source code. I'll take a look.
Quote:
Originally Posted by telemark View Post
segfault on missing args
Can you provide an example?

jkozee is offline   Reply With Quote
Old 06-05-2015, 12:42 PM   #23
Keen
Registered User
 
Join Date: Aug 2009
Location: Minneapolis, MN
Posts: 236
Quote:
Originally Posted by jkozee View Post
Nope, hence my request for help. However, all of the tools will report an accurate list of options, with at least some indication of what they do.
Is the current source uploaded anywhere? I haven't touched SF in forever, but it looks like it only has the source for MFS Tools v2.

Keen is offline   Reply With Quote
Old 06-05-2015, 01:10 PM   #24
jkozee
Registered User
 
Join Date: Jan 2006
Posts: 33
The HEAD branch on SF is still the 3.0 branch. I need to cleanup my patches a bit, then I will update the repo. Pretty busy this weekend, but I hope to have updated soon.

jkozee is offline   Reply With Quote
Old 06-05-2015, 01:33 PM   #25
telemark
Registered User
 
Join Date: Nov 2013
Posts: 1,483
bug test cases

Long boring data here.
Spoiler:
I was trying mfsadd but didn't think it was 4k alignment:
Nevermind, that is 4k aligned. I assumed the wrong unit.
Code:
  /dev/sdb15          1024            0 MiB
  /dev/sdb16    3907006464      1907718 MiB
I'll give it a go then.

This 4TB disk is the result of an automatic Roamio 20.4.5c formatting within the Tivo:
Code:
$ mfstool mfsinfo /dev/sdb
mfsinfo: Volume size (3510156288) mismatch with reported size (1).
$ mfstool mls /dev/sdb
mls: Volume size (3510156288) mismatch with reported size (1).
There is a mismatch due to Tivo's bug, but the Roamio still operates with it. Open question whether it make sense to ignore the mismatch.

Same disk under pdisk:
Code:
$ pdisk_roamio /dev/sdb
stat: mode = 060660, type=Block, size = 0, blocks = 0
BLKGETSIZE: size in blocks = 3519069872
HDIO_GETGEO: heads=255, sectors=63, cylinders=27649, start=0,  total=444181185
_llseek: pos = 4000787030016, blocks=7814037168
/dev/sdb
Command (? for help): p
Partition map (with 512 byte blocks) on '/dev/sdb'
 #:                type name                         length   base       ( size )
 1: Apple_partition_map Apple                            63 @ 1         
 2:               Image Bootstrap 1                       8 @ 4297720304
 3:               Image Kernel 1                          8 @ 4297720312
 4:                Ext2 Root 1                            8 @ 4297720320
 5:               Image Bootstrap 2                       8 @ 4297720328
 6:               Image Kernel 2                          8 @ 4297720336
 7:                Ext2 Root 2                            8 @ 4297720344
 8:                Swap Linux swap                  1048576 @ 4297720352 (512.0M)
 9:                Ext2 /var                        1572864 @ 4298768928 (768.0M)
10:                 MFS MFS application region      1638400 @ 4306633248 (800.0M)
11:                 MFS MFS media region         3504127120 @ 4309910048 (  1.6T)
12:                 MFS MFS application region 2    1638400 @ 4308271648 (800.0M)
13:                 MFS MFS media region 2       4297720240 @ 64         (  1.3G)
14:                Ext2 SQLite                      6291456 @ 4300341792 (  3.0G)
Command (? for help): quit
Is size field getting overflowed?



I'm not sure what some fields are, but I noted they were zero before being modified during mfsadd.
Code:
00001a00  4d 50 00 00 10 00 00 00  40 00 00 00 00 70 83 e8  |MP......@....p..|
00001a10  4d 46 53 20 6d 65 64 69  61 20 72 65 67 69 6f 6e  |MFS media region|
00001a20  20 32 00 00 00 00 00 00  00 00 00 00 00 00 00 00  | 2..............|
00001a30  4d 46 53 00 00 00 00 00  00 00 00 00 00 00 00 00  |MFS.............|
00001a40  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00001a50  00 00 00 00 00 70 83 e8  33 01 00 00 00 00 00 00  |.....p..3.......|
00001a60  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

00001a00  4d 50 00 00 0e 00 00 00  40 00 00 00 00 70 83 e8  |MP......@....p..|
00001a10  4d 46 53 20 6d 65 64 69  61 20 72 65 67 69 6f 6e  |MFS media region|
00001a20  20 32 00 00 00 00 00 00  00 00 00 00 00 00 00 00  | 2..............|
00001a30  4d 46 53 00 00 00 00 00  00 00 00 00 00 00 00 00  |MFS.............|
00001a40  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00001a50  00 00 00 00 00 00 00 00  00 01 00 00 00 00 00 00  |................|
00001a60  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
Code:
$ export MFS_HDA=/dev/sdb
$ mfstool mls 
Segmentation fault (core dumped)


Last edited by telemark; 06-06-2015 at 12:54 AM.
telemark is offline   Reply With Quote
Old 06-05-2015, 01:47 PM   #26
ggieseke
Registered User
 
Join Date: May 2008
Posts: 3,328
Quote:
Originally Posted by jkozee View Post
Restoring to a 4TB drive should work out of the gate, but I don't have a 6TB drive to test with. I've been told that it requires that the media partition not exceed 2TB, which would mean that it would take 3 app/media pairs to fill the drive. You would then need to coalesce the last pair to reduce the partition count to 15.
Make that 14 partitions unless you know something that I missed. Premieres should be more flexible since AFAIK the eBay 4TB drives with 16 partitions still work, but Roamios are finicky. They seem to want 14 - no more, no less.

Cool project!

ggieseke is offline   Reply With Quote
Old 06-06-2015, 02:48 AM   #27
telemark
Registered User
 
Join Date: Nov 2013
Posts: 1,483
Ya no go.

Taking a non-expanded 4TB Roamio drive, copied to a 6TB drive, mfsadd for #15 + #16, and a custom mod of the APM to combine the two to #15.
Roamio OTA on 20.4.5c just erases the drive and starts over.

Was I suppose to mod the MFS partition list at the same time?

Very powerful toolkit though. Impressive.

telemark is offline   Reply With Quote
Old 06-06-2015, 06:20 PM   #28
aaronwt
HD Addict
 
aaronwt's Avatar
 
Join Date: Jan 2002
Location: Northern VA(Woodbridge)
Posts: 15,730
hmmm... I might try this out my Premiere. With a larger hard drive it could be a viable replacement for my GFs OLED S3 TiVos. Those 1TB drives I put in them have been running for over eight years now and it's only a matter of time until something happens.

__________________
Roamio Pro (5TB Red)
TiVo Mini x4
Roamio Basic OTA (1TB Red)
53TB unRAID2--38TB unRAID3--33TB unRAID1a
XBL/PSN: WormholeXtreme
aaronwt is online now   Reply With Quote
Old 06-06-2015, 06:47 PM   #29
HomeUser
Registered User
 
HomeUser's Avatar
 
Join Date: Jan 2003
Location: A2 Michigan
Posts: 2,332
THANKS! Will I be able to replace the expanded 2 drives back to one large drive in my old DVR's

__________________
VicW, Ex-Comcast customer ... And loving it!.
HomeUser is offline   Reply With Quote
Old 06-06-2015, 08:21 PM   #30
jmbach
der Neuerer
 
jmbach's Avatar
 
Join Date: Jan 2009
Posts: 1,109
Does the Copy command copy the image to the new drive while resizing to fit the new drive or does it do a straight copy of the image to the new drive.

__________________
"Delay is preferable to error" - Thomas Jefferson
"If I have seen further it is by standing on the shoulders of Giants" - Sir Isaac Newton
jmbach is online now   Reply With Quote
Reply
Forum Jump







Thread Tools


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Advertisements





TiVo Community
Powered by vBulletin® Version 3.8.5
Copyright ©2000 - 2015, Jelsoft Enterprises Ltd.
vBulletin Skins by: Relivo Media


(C) 2015 DBNet - All Rights Reserved. No information may be posted elsewhere without written permission.
TiVoŽ is a registered trademark of TiVo Inc. This site is not owned or operated by TiVo Inc.
All times are GMT -5. The time now is 11:07 AM.
Page generated in 0.18993211 seconds (71.16% PHP - 28.84% MySQL) with 19 queries