Don't get me wrong. I applaud your spirit of adventure - I just wish you'd put that degree of effort into something of more use to the functionality of the box.fao: 'Jack616' - didn't 'JFK' make a speech about landing on the Moon not because it was easy but because it was hard?
I just wish you'd put that degree of effort into something of more use to the functionality of the box.
(I don't have immediate suggestions but there are issues I think).
The custom firmware kernel does have support for large sector disks and GPT/EFI partition tables enabled but the stock firmware doesn't.
I read this thread with great interest as I was seeking information on using a 4TB USB disk with my HDR-FOX T2.
Using a WD MyBook 4TB USB drive, I formatted using EaseUS Partition Master - with options MBR EXT3.
Connecting to the HDR-FOX T2 , the disk was loaded with the full 4TB as free.
Copying files from the HDD to the 4TB was as normal.
As expected, the same disk formatted with options GPT EXT3 did not work.
The Humax won't work with that disk as the kernel is not compiled with GUID/EFI support. Even if that support were enabled, which it could be, it is unlikely to work because the version of Linux in use doesn't support GUID partition tables on 4K sector disks properly.
A full fix would involve backporting the fix for the last issue from a later kernel version.
This is actually on my todo list (I want to try and get a 3TB internal drive working) so my box is currently running a custom kernel with GUID/EFI and large block device support enabled but I have not yet addressed the 4K sector issue.
Even though it's old, the post you've quoted still sums up the current situation. It never has made it to the top of my to-do list. Kernel support is enabled in CFW builds but as far as I'm aware nobody has tried it. GPT/EFI partitioning could be tried on a drive of any size so I may give it a go with one of my spare units (just 500GB disks though I think). There's still the potential issue with GPT partioning on AF disks but it should be possible to overcome..
....to 'af123' - so 2 years on, how did your experiment go? Are you still running it, or was it simply too much hassle to get GPT support to work in the end? (thanks).
...Still, big drives are getting cheaper so I may take the plunge and try an upgrade this year.
To 'af123' - further to our brief chat yesterday i can confirm GPT support isn't available, or at least not for me for external hard drive usage. (i'm on CF 1.03.12 - 3.03).Kernel support is enabled in CFW builds but as far as I'm aware nobody has tried it. GPT/EFI partitioning could be tried on a drive of any size so I may give it a go with one of my spare units (just 500GB disks though I think).
I only have the custom kernel from CFW 3.03 which does have the options for EFI enabled - the kernel configuration for that build can be read at https://rs.hpkg.tv/svn/firmware/kernel/etc/config - I plan to have a look at converting the internal disk on a spare unit to GPT over the weekend, time permitting..
But also, I read on a previous thread somewhere that 'af123' was using his own custom kernel with GUID/EFI support, which if true, i would like to test myself.
If you're interested, you could try my custom kernel with EFI support - it might see your 3TB disk.
http://hpkg.tv/fwx/HDR_kernels.zip
That contains two HDF files - one which will install the custom kernel and one which will revert to the stock one. Put the relevant file onto a USB stick as HDR_FOX_T2_upgrade.hdf and follow the usual firmware upgrade process.
No reason for it to be - the file system access routines should be blind to whether the mass storage unit in question is mounted by SATA or USB....but i think the support as mentioned is most probably for internal drives.
humax# fdisk -l /dev/sda
Disk /dev/sda: 500.1 GB, 500107862016 bytes
256 heads, 63 sectors/track, 60563 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 60564 488386583+ ee EFI GPT
humax# gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 976773168 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 7E7F2579-5C23-4181-ABB6-60BAB5041839
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4047 sectors (2.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 2099199 1024.0 MiB 8300 Linux filesystem
2 2099200 955801614 454.8 GiB 8300 Linux filesystem
3 955803648 976773134 10.0 GiB 8300 Linux filesystem
humax# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 21.4M 21.4M 0 100% /
tmpfs 60.9M 48.0K 60.9M 0% /tmp
tmpfs 60.9M 0 60.9M 0% /media
/dev/mtdblock1 2.0M 540.0K 1.5M 26% /var/lib/humaxtv
/dev/mtdblock2 2.0M 500.0K 1.5M 24% /var/lib/humaxtv_backup
/dev/sda1 1007.9M 34.9M 973.0M 3% /mnt/hd1
/dev/sda2 454.6G 198.2M 454.4G 0% /mnt/hd2
/dev/sda3 9.8G 150.6M 9.7G 1% /mnt/hd3
You think maybe it reads the file system type and if it does not match expectations just gives up?However, the Humax software says that the storage needs to be formatted and won't record