Very Large Hard Drive - Revision history

Black Hole: /* Pre-requisites */

2019-02-17T13:19:04Z

‎Pre-requisites

Black Hole: /* Partitions tables */

2018-10-07T07:59:23Z

‎Partitions tables

Prpr: Add 4TB limit notes

2018-03-21T09:29:49Z

Add 4TB limit notes

Af123: /* Creating the GPT and formatting the disk */

2016-11-28T15:26:12Z

‎Creating the GPT and formatting the disk

Af123: /* Drives known to work */

2016-02-25T09:50:13Z

‎Drives known to work

Af123 at 09:45, 25 February 2016

2016-02-25T09:45:38Z

Af123 at 09:45, 25 February 2016

2016-02-25T09:45:03Z

Af123: /* Drives known to work */

2016-02-25T09:43:42Z

‎Drives known to work

Af123: /* Drives known to work */

2016-02-25T09:42:58Z

‎Drives known to work

Af123: /* Drives known to work */

2016-02-25T09:37:23Z

‎Drives known to work

@@ Line 27: / Line 27: @@
 ===Pre-requisites===
-Using a very large drive requires Custom Firmware 3.10 or above. The stock Humax firmware cannot read these drives at all (it will see them but consider them to have a zero size).
+Using a very large drive '''''requires''''' Custom Firmware 3.10 or above. The stock Humax firmware cannot read these drives at all (it will see them but consider them to have a zero size).
 ===Partitions tables===

@@ Line 31: / Line 31: @@
 ===Partitions tables===
-With these large drives, it is necessary to use a partitioning scheme called GUID Partition Table (GPT). When using a GPT, a legacy MBR containing a partition table is also created on the drive. This MBR generally contains a single partition of type ''EFI GPT'' (code 0xee) encompassing the entire drive, well as much of the drive as can be represented in an MBR partition - 2^32 sectors. This is known as a ''protective MBR'' since its main purposes is to prevent non-GPT-aware systems and tools from viewing the drive as empty or available. In the case of the Humax, it is necessary to create three partitions on the drive so that the Humax software sees these and considers the drive to be properly formatted.
+With these large drives, it is necessary to use a partitioning scheme called GUID Partition Table (GPT). When using a GPT, a legacy MBR containing a partition table is also created on the drive. This MBR generally contains a single partition of type ''EFI GPT'' (code 0xee) encompassing the entire drive (or as much of the drive as can be represented in an MBR partition - 2^32 sectors). This is known as a ''protective MBR'' since its main purposes is to prevent non-GPT-aware systems and tools from viewing the drive as empty or available. In the case of the Humax, it is necessary to create three partitions on the drive so that the Humax software sees these and considers the drive to be properly formatted.
 ===Creating the GPT and formatting the disk===

@@ Line 3: / Line 3: @@
 {{Warning|title=Work in progress|This page is a work-in-progress describing the process necessary to install a very large hard drive into a Humax HDR Fox T2.}}
-With the release of Custom Firmware 3.10 it is now possible to fit a Humax HDR Fox T2 with a hard drive having more than 2^32 sectors. In practice this means that drives over 2TB in size can now be used.
+With the release of Custom Firmware 3.10 it is now possible to fit a Humax HDR Fox T2 with a hard drive having more than 2^32 sectors. In practice this means that drives between 2TB and 4TB in size can now be used. Disks larger than 4TB have been found to cause problems with the Humax software reporting low amounts of free space.
 ===Drives known to work===

← Older revision		Revision as of 15:26, 28 November 2016
Line 34:		Line 34:

	===Creating the GPT and formatting the disk===		===Creating the GPT and formatting the disk===
		+
		+	Restart the Humax into Maintenance mode then use the telnet menu to do the work for you. Just choose the ''gptf'' option and confirm that you really want to reformat the disk.

	Menu version 1.20		Menu version 1.20

@@ Line 15: / Line 15: @@
 |-
 |   || Seagate || NAS 3.5" HDD SATA || ST4000VN000 || 4TB || 64MB || 5900 || 4096 || 512
 |}

@@ Line 19: / Line 19: @@
 {{Note|'''Always choose a specific Audio/Visual (AV) or Digital Video Recorder (DVR) drive if possible.'''
-Avoid drives which are designed for RAID use (e.g. WD Red and Purple drives) as they will have TLER (an error recovery option) enabled which can cause issues if there are problems with reading or writing to a sector. AV drives usually have this parameter disabled so that a failed write is just ignored and recording moves on. It can also cause complications when dealing with any problem sectors in the future as it causes some issues to be hidden from the host (the Humax in this scenario).
+* Avoid drives which are designed for RAID use (e.g. WD Red and Purple drives) as they will have TLER (an error recovery option) enabled which can cause issues if there are problems with reading or writing to a sector. AV drives usually have this parameter disabled so that a failed write is just ignored and recording moves on. It can also cause complications when dealing with any problem sectors in the future as it causes some issues to be hidden from the host (the Humax in this scenario).
+* WD Purple drives have a surprisingly low workload rating of 60TB/year and should be avoided.
-WD Purple drives have a surprisingly low workload rating of 60TB/year and should be avoided.
+* With any non-AV Western Digital disk, watch the disk stats to check if the load/unload count grows quickly which could indicate that automatic head parking after 8 seconds is enabled. This can (and should) be disabled using ''wdidle3''[http://www.storagereview.com/how_to_stop_excessive_load_cycles_on_the_western_digital_2tb_caviar_green_wd20ears_with_wdidle3]. }}
 ===Pre-requisites===

@@ Line 23: / Line 23: @@
 WD Purple drives have a surprisingly low workload rating of 60TB/year and should be avoided.
-With any non-AV Western Digital disk, watch the disk stats to check if the load/unload count grows quickly which could indicate that automatic head parking after 8 seconds is enabled. This can (and should) be disabled using [http://www.storagereview.com/how_to_stop_excessive_load_cycles_on_the_western_digital_2tb_caviar_green_wd20ears_with_wdidle3|wdidle3]. }}
+With any non-AV Western Digital disk, watch the disk stats to check if the load/unload count grows quickly which could indicate that automatic head parking after 8 seconds is enabled. This can (and should) be disabled using [http://www.storagereview.com/how_to_stop_excessive_load_cycles_on_the_western_digital_2tb_caviar_green_wd20ears_with_wdidle3 | wdidle3]. }}
 ===Pre-requisites===

@@ Line 10: / Line 10: @@
 {| class=wikitable
-! AV? || Vendor || Description || Model || Size || Cache || RPM || Physical Sector Size || Logical Sector Size
+! AV? || Vendor || Description || Model || Size || Cache || RPM || Physical Sector || Logical Sector
 |-
-| * | Seagate || Video 3.5" HDD SATA || ST4000VM000 || 4TB || 64MB || 5900 || 4096 || 512
+| * || Seagate || Video 3.5" HDD SATA || ST4000VM000 || 4TB || 64MB || 5900 || 4096 || 512
 |-
-|   | Seagate || NAS 3.5" HDD SATA || ST4000VN000 || 4TB || 64MB || 5900 || 4096 || 512
+|   || Seagate || NAS 3.5" HDD SATA || ST4000VN000 || 4TB || 64MB || 5900 || 4096 || 512
 |}