2TB Disk Installation Blog - Revision history

Ezra pound at 12:34, 4 October 2019

2019-10-04T12:34:52Z

2019-10-04T12:10:59Z

2019-10-04T12:07:46Z

2016-02-01T20:22:52Z

‎Installing a Drive Larger Than 2TB - Possible?

2016-02-01T20:22:00Z

2016-01-30T15:28:12Z

2016-01-30T15:23:58Z

2014-03-18T17:03:12Z

2013-09-11T10:30:07Z

2012-08-07T14:57:01Z

← Older revision		Revision as of 12:34, 4 October 2019
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
−
	{{Note\|This Blog was written prior to the release of the 1.03.xx firmware, When running 1.03.xx firmware the Humax is capable of formatting and 4K aligning a new 2TB hard drive }}		{{Note\|This Blog was written prior to the release of the 1.03.xx firmware, When running 1.03.xx firmware the Humax is capable of formatting and 4K aligning a new 2TB hard drive }}

← Older revision		Revision as of 12:10, 4 October 2019
Line 1:		Line 1:
	__NOTOC__		__NOTOC__

−	{{Note\|This Blog was written prior to the release of the 1.03.xx firmware, When running 1.03.xx firmware the Humax is capable of formatting and 4K aligning a new 2TB hard drive, }}	+	{{Note\|This Blog was written prior to the release of the 1.03.xx firmware, When running 1.03.xx firmware the Humax is capable of formatting and 4K aligning a new 2TB hard drive }}

@@ Line 1: / Line 1: @@
 __NOTOC__
 I've just replaced the hard disk in my Humax HDR Fox-T2 with a 2TB drive
 as my original factory-fitted 1TB drive has recently suffered from a bad
@@ Line 34: / Line 38: @@
 could cause other issues and any reversion to standard Humax firmware
 would be problematic.
 Also, the Humax firmware can neither partition nor format an internal

← Older revision		Revision as of 20:22, 1 February 2016
Line 267:		Line 267:
	===Installing a Drive Larger Than 2TB - Possible?===		===Installing a Drive Larger Than 2TB - Possible?===

−	Yes, work is being done on this front. Please take a look at [[Very_Large_Hard_Drive]]	+	Yes, work is being done on this front. Please take a look at how to fit a Humax HDR-Fox T2 with a [[Very_Large_Hard_Drive\|very large hard drive]].

@@ Line 264: / Line 264: @@
 The only significant change is to the number of inodes allocated to the AV partition.
 ===Installing a Drive Larger Than 2TB - Possible?===
-Yes, however:-
+Yes, work is being done on this front. Please take a look at [[Very_Large_Hard_Drive]]

@@ Line 268: / Line 268: @@
 ===Installing a Drive Larger Than 2TB - Possible?===
-Yes, however:
+Yes, however:-
-*This requires custom firmware 3.10 or above;
+*This requires custom firmware 3.10 or above
-*You will be unable to use stock firmware. In fact, loading stock firmware may well destroy the drive contents (note1);
+*You will be unable to use stock firmware. In fact, loading stock firmware may well destroy the drive contents (note1)
-*It has only been tested with a 4TB Seagate Video drive (ST4000VM000);
+*It has only been tested with a 4TB Seagate Video drive (ST4000VM000)
-*Higher capacity drives generally use more power and take longer to become ready;
+*Higher capacity drives generally use more power and take longer to become ready
-*it has only been tested up to 4TB (although there is no reason it should not work for larger drives);
+*it has only been tested up to 4TB (although there is no reason it should not work for larger drives)
-*it has only been tested a drive that advertises a 512-byte logical sector size (I'd expect more kernel work to be required for a drive advertising a 4K size).
+*it has only been tested on a drive that advertises a 512-byte logical sector size (I'd expect more kernel work to be required for a drive advertising a 4K size)
 note 1  Careful selection of the MBR guard partitions should be able to prevent this from corrupting actual recordings making it recoverable.

← Older revision		Revision as of 15:23, 30 January 2016
Line 264:		Line 264:

	The only significant change is to the number of inodes allocated to the AV partition.		The only significant change is to the number of inodes allocated to the AV partition.
		+
		+
		+	===Installing a Drive Larger Than 2TB - Possible?===
		+
		+	Yes, however:
		+
		+	*This requires custom firmware 3.10 or above;
		+	*You will be unable to use stock firmware. In fact, loading stock firmware may well destroy the drive contents (note1);
		+	*It has only been tested with a 4TB Seagate Video drive (ST4000VM000);
		+	*Higher capacity drives generally use more power and take longer to become ready;
		+	*it has only been tested up to 4TB (although there is no reason it should not work for larger drives);
		+	*it has only been tested a drive that advertises a 512-byte logical sector size (I'd expect more kernel work to be required for a drive advertising a 4K size).
		+
		+
		+	note 1 Careful selection of the MBR guard partitions should be able to prevent this from corrupting actual recordings making it recoverable.

@@ Line 108: / Line 108: @@
 [[File:4kblocks.png]]
-The first part is easy - ext3 has a default block size of 4096 bytes so maps nicely onto a 4K disk sector. However, just using a 4K file-system block size isn't enough. In the diagram above, file-system block A is not aligned with a disk sector so when block A is changed sectors X and Y must be updated using a read-modify-write sequence including an additional platter rotation. The complete solution requires that partitions are aligned with disk sectors.
+The first part is easy - ext3 has a default block size of 4096 bytes so maps nicely onto a 4K disk sector. However, just using a 4K file-system block size isn't enough. In the diagram above, file-system block A is not aligned with a disk sector so when block A is changed sectors X and Y must be updated using a read-modify-write sequence including an additional platter rotation. The complete solution requires that partitions are aligned with disk sectors. There's a good article on IBM's web site (http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/) on the performance impact of misaligned sectors.
 To achieve this, I used the GNU Fdisk (gfdisk) utility which is built into Custom Firmware 2.12 and above. The ''u'' command changes the input units from cylinders to sectors. I then just ensured that the start sector of each partition was divisible by 8.

← Older revision		Revision as of 14:57, 7 August 2012
Line 1:		Line 1:
		+	__NOTOC__
	I've just replaced the hard disk in my Humax HDR Fox-T2 with a 2TB drive		I've just replaced the hard disk in my Humax HDR Fox-T2 with a 2TB drive
	as my original factory-fitted 1TB drive has recently suffered from a bad		as my original factory-fitted 1TB drive has recently suffered from a bad