• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

How do I replace internal hard drive

martinr said:
I recently replaced the hard drive on my Foxsat with a WD AV-GP 1TB and had to put a jumper across pins 5 and 6 to slow the data transfer rate (as advised in the AVforum). When it comes to replacing the hard drive in the Fox T2, I haven’t seen any similar advice. Does that mean there is no requirement for the use of a jumper with a Fox T2 HDR?. (I run the Custom Firmware on both boxes.)
Click to expand...

The Foxsat-HDR was designed to use Sata 2.0 drives, the latest Sata 3.0 drives have much faster data transfer speeds. The Hdr FOX-T2 is a much newer design so should work with the newer drives. If I remember correctly the HDR FOX T2 comes with a Seagate Pipeline Drive which doesn't have jumpers.
 
Anyone have any feeling on fitting SSD drives ? I was wondering about trim support and any advantages or disadvantages of doing so.
 
Don't bother. No speed advantage, expensive, fairly small, reliability questionable.
Seagate Pipeline is the way to go if you need a new HDD.
 
Trev said:
Don't bother. No speed advantage, expensive, fairly small, reliability questionable.
Seagate Pipeline is the way to go if you need a new HDD.
Click to expand...
Yeah - I read the thread BH posted. Shame I was looking for - faster - cooler. I might just get a HUGE spinning disk, so It takes years to fill it. I am always having to format it when it gets full. It seems to take ages to delete them one at a time.
 
Looking to replace a failing drive with a 4tb, but the 'Pipeline' drives seem to be hard to come by. IronWolf (NAS) and SkyHawk (Surveillance) seem to be Seagate's current offering. Anyone have any experince of either?
 
I don't have any experience of the HDDs that you mention. However, one of my HDRs now has a Western Digital 4TB EURX drive fitted. As BH states in the previous post, you will have to use the special custom firmware format facility.
 
My original 1TB is showing errors, currently running the fixdisk but have ordered the 2TB ST2000VM003 anyway. Anyone know if the partitioning/gfdisk/inode tweaks in the wiki.hummy.tv/wiki/2TB_Disk_Installation_Blog are worth doing?
 
You need to know that the 2TB installation process was documented when the standard Humax firmware was unable to initialise a 2TB disk. With 1.03.xx firmware you can (if you wish) just fit it and initialise using the standard menus.
 
Robobunny said:
Anyone know if the partitioning/gfdisk/inode tweaks in the wiki.hummy.tv/wiki/2TB_Disk_Installation_Blog are worth doing?
Click to expand...
As Black Hole says you can just go ahead and format it but there is some merit in doing the file system creation yourself because you will end up with a much smaller inode count which gives much quicker fixdisk times and some other optimisations. I used the wiki instructions when installing a 2TB drive and have been very happy with the result.
 
Robobunny said:
Anyone know if the partitioning/gfdisk/inode tweaks in the wiki.hummy.tv/wiki/2TB_Disk_Installation_Blog are worth doing?
Click to expand...
The inode tweaks are. I would leave it as MBR rather than going GPT.
The simplest way to do this is to let the Humax partition and format. Then go in to Maintenance mode and re-format the partitions as per the guide.
 
OK Job done, physically straightforward (it was easier to unscrew the drive holder from the base, then pull the SATA connector off the drive). I noted after a full reboot, the drive is /dev/sdb, and in Maintenance mode it's /dev/sda. Let the box reformat - the start sectors of each partition were already all divisible by 8:
humax# gfdisk -lu /dev/sdb
Device Boot Start End Blocks Id System
/dev/sdb1 8 2104510 1052226 83 Linux
/dev/sdb2 2104512 3886043166 1941969330 83 Linux
/dev/sdb3 3886043168 3907024062 10490445 83 Linux

In Maintenance mode, I had to "umount /dev/sda1" (and 2 & 3) before I could run the three mentioned "mkfs.ext3 ..." commands. Comparing the "tune2fs -l /dev/sdb1" (and 2 & 3) parameters before and after, the 5% reserved has gone, and the tweaks mentioned are all in place. The box was happy with the partitions after it was all done. Schedule was remembered, the full webif (and packages) needed reinstalling but was prompted to do that via the initial webif. Currently copying the old disk over via a USB adaptor, looks like it will take about 12 hours for 600GB (disable auto power down!). Thanks for the advice and the excellent custom firmware.
 
Clearly, as I'd swapped the disk ;) - I added that to give others that may be cautious of a disk replacement (as I was) more confidence that's it's straightforward. All you need is a medium cross-head screwdriver. While I'm here - if you haven't got a USB <-> SATA adaptor, but do have enough spare hard drive space on your PC, and your Humax is on the same LAN, you can use the Samba service to back up your recordings before removing the drive, and copy them back to the new drive later. On mine the USB transfer speed was ~128Mbit/s and the LAN averaged ~85Mbit/s (it's a 100Mbit/s NIC inside). WiFi would work, but would take days if you have hundreds of Gigs. Keep up the good work!
 
Robobunny said:
... I noted after a full reboot, the drive is /dev/sdb, and in Maintenance mode it's /dev/sda. ...
Click to expand...
This happens if you have a virtual disk package installed (CF), or a USB storage device plugged in that starts more quickly than the internal disk.
 
Just replaced my ailing 1TB drive on the HDR-Fox T2 with the 2TB replacement recommended here (In stock on Amazon). Removed the drive and put it into a dual drive external copier. Once removed, plugged it into my Win 10 PC, downloaded Partition Manager 17 (Freeware) and extended the partition to the full 1.8TB capacity. Returned it to the Humax and now works a treat. I took the precaution of removing the encryption and copying to an external drive before proceeding. I specialise in computer disaster recovery, so I couldn't do it any other way, really :).

Thanks for all the above assistance, especially the comment regarding the fan plugged into the motherboard. Hastily had to lift the lid to plug it in (oops) but no harm done.
 
You must log in or register to reply here.
Back
Top