My Humax Forum » FAQ » PVR 9150T, 9200T, 9300T


HumaxRW v1.15 and HumaxCheck 0.10

(1 post)
  1. super-admin


    senior admin
    Joined: Feb '11
    Posts: 568


    This HumaxRW program is an alternative to HummyReadFiles and HDC. Its main function is to provide a means to transfer the files from an old hard disk to a new disk when upgrading. It can also be used to backup files to/from a host computer (if say a reformat becomes necessary). It does not perform defragmentation as such, but if you copy all the files onto a host drive, reformat, then copy all the files back, the drive will then be defragmented. The disadvantage is that it is very much command line driven.

    It can operate in one of three modes:

    1. Copy files to/from the Humax disk onto the host computer.
    2. If two Humax disks are connected to the host computer it can transfer the files directly from one to the other.
    3. Recovery mode - used if the record list is missing/corrupt - list and retrieve recordings

    * List recordings
    * Copy recordings to the host computer
    * Copy previously saved recordings back from the host to the Humax disk
    * Copy recordings between two 9200T formatted disks
    * Read the additional information about a programme
    * Delete a programme
    * Backup all programmes
    * Recovery mode - list and retrieve recordings if the record list is missing/corrupt

    When copying a recording from the Humax disk it will create the .ts file and three other files (.hre, .elu & .epg). These files contain all the information about the recording from the Humax disk. In order for the Humax to be able to play back the ts file when it is written to a new disk, some of these files must be present. They are as follows:

    * .hre: Record list entry - this contains PID information about the ts file and must be present.
    * .elu: This contains timing information. If it is missing the timebar may be incorrect and the (front panel) elapsed time indicator may run at the wrong speed.
    * .epg: Additional information about the programme. This is not always present.

    Therefore it is not possible to copy a .ts file onto the Humax disk without its associated .hre file.

    It is now possible (using the utility ts2hrw in version 1.09) to create hre files using just the ts files (with some dummy information). See here for some details of the hre file format.

    Do not allow Windows to "Initialise" the disk in disk/device manager. The disk should not appear under "My Computer". If this is done accidentally use the "-p" option to HumaxCheck to fix the partition table.

    The usual disclaimers and copyright applies, the author, poster, and host sites of this program hold no responsibility what so ever. Since this program is able to write to the 9200T hard disk there is a slim possibility that some as yet unforeseen form of corruption could cause the program to make the disk unreadable - use it very much at your own risk.

    See README.txt in the downloaded archive.


    humaxcheck is a tool to help with diagnosis of 9200T HDD faults. It is currently beta and the user interface is very basic. It can operate in read-only mode to see the effect of the options before making changes to the disk. It is run from a command prompt in a similar way to HumaxRW. Note that the output does need some user interpretation which means beginners shouldn't get too alarmed by some of the messages. It is best to seek advice before reformatting.

    e.g. humaxcheck 2:
    should produce a listing showing all the files on the video partitions and their status.

    To direct this output to a file
    humaxcheck 2: > 9200disk.txt

    Typical output:
    3.elu : OK, Frag: 2, size: 407040
    1.av : Buf Contig. size: 1539903488 Alloc fat 7896000, dir 7896000

    3.av : OK, Contig. size: 1201273856
    2.elu : OK, Frag: 2, size: 528896
    5.elu : OK, Frag: 2, size: 396800
    22.av : OK, Contig. size: 1077682176
    4.elu : OK, Contig. size: 706560

    This first section lists the files on partition 0. The numbers 1.av, 2.av etc. do not correspond to the index numbers in the standard humaxrw listing or to that of the 9200T (use humaxrw -l -x to view a listing with the av filenames). The .av files are the same as the .ts files transferred by humaxrw. The elu and epg files (see later) are also transferred as is, by humaxrw. The files 0.av and 1.av are the live buffers and are typically 4GB each. The size value will change depending on the amount stored but the allocated size should not change. The number of fragments is also shown, or whether the file is contiguous. The 'alloc' numbers shown above are the number of sectors allocated (each sector is 512 bytes). The sizes shown are the actual file sizes in bytes. Sometimes a buffer around 32K will appear (e.g 32768.av) This may be a temporary buffer which has not been deleted but I am not sure.

    78.elu : OK, Frag: 2, size: 1426432
    78.av : Err Frag: 27, size: 1043598336 Alloc fat 3554704, dir 1528064
    Allocation error: (fat blocks allocated != sizea)
    File End error
    Warning - File size error
    2697 cross-linked blocks found in file 78.av

    79.elu : OK, Contig. size: 613376
    79.av : OK, Frag: 21, size: 1290931200
    80.elu : OK, Contig. size: 34272
    0.av : Buf Frag: 56, size: 15400960 Alloc fat 7896752, dir 7896000
    Allocation error: (fat blocks allocated != sizea)
    2697 cross-linked blocks found in file 0.av

    Here file 78.av has become cross linked with the buffer 0.av and the number of blocks allocated in the FAT does not correspond with the size allocated parameter in the directory entry.

    81.elu : OK, Contig. size: 568320
    81.av : OK, Frag: 4, size: 1075991040

    148 blocks allocated in orphan chains taking up 56983552 bytes
    Humax calculated free space count: 857063424 bytes
    Total free space count incorrect
    Actual free space based on allocated blocks: 839737344 bytes

    The number of orphans is shown. These are blocks which are allocated but not in use by any file.
    The free space count is incorrect

    _RECORD_LIST_ : OK, Frag: 2, size: 24325
    _RL_BACKUP_ : OK, Contig. size: 24325
    5.epg : OK, Contig. size: 332
    17.epg : OK, Contig. size: 660
    2.epg : OK, Contig. size: 332
    4.epg : OK, Contig. size: 660
    6.epg : OK, Contig. size: 332
    80.epg : OK, Contig. size: 332
    81.epg : OK, Contig. size: 988

    577 blocks allocated in orphan chains taking up 9453568 bytes
    Humax calculated free space count: 257212416 bytes

    Partition 1 is a similar format to partition 0. The file _RECORD_LIST_ contains the the record listing shown on the screen. It is the concatenation of all the hre files. This partition shows no size errors.


    humaxcheck takes a memory copy of all the disk structures. There are some command line options which can be used to repair this memory copy and see the result in the listing. The final write back is only enabled when the -w option is used.

    The options are:
    -a (all) equivalent to -d -f and truncate all files (use with care!)
    -c cleans up orphans by releasing the allocated space (can make fragmentation worse)
    -d fix directory & FAT
    -f fixes the free space count. (The Humax has a tendency to break it again very quickly!)
    -p repair the partition table (useful if other operaing systems decide to initialise the disk)
    -t used to truncate files - can be used to fix cross-linked files.
    -w write any changes back to the disk


    The -c option will free any blocks used but not allocated to a file on the disk (orphans). However, the Humax has a tendency to allocate small areas on disk but not use them. Since these areas are quite small new files created after this cleanup operation has been performed may well end up fragmented. Therefore it is best to use this option sparingly i.e. only when a significant amount of space would be freed (say at least 1GB).


    1. humaxrw-1.15-linux.tar.gz (32.4 KB, 253 downloads) 2 years old
    2. (10.8 KB, 478 downloads) 2 years old
    3. (36.2 KB, 744 downloads) 2 years old
    Fri 23 Sep 2016 20:02:29 #1 |

RSS feed for this topic

Topic Closed

This topic has been closed to new replies.