Recent content by leicray

For the sake of completeness, here is what people need to know if they wish to do a like-for-like replacement of the disk in an HDR Fox T2. The disk that was fitted to my T2 was a Seagate ST3500312CS. If you go onto eBay you will find that there are lots of these disks for sale, often described...

I think that you might be onto something there. The disks have date "codes" on their labels but not conventional dates. However, the clue is in post #30. The original disk firmware contains the string "Gen2 signaling speed (3.0Gb/s)" which is absent from the firmware of the replacement disk...

Comparison of the firmware parameters of the original and replacement disks reveals very little apart from the parameters that would be expected to differ: 6c6 < Serial Number: 6VVF72NK --- > Serial Number: 9VV70WSB 67d66 < * Gen2 signaling speed (3.0Gb/s) 86,87c85,86...

I have found the time to now try the "Custom Firmware with Debug Kernel" and my Hummy failed to boot with that CF. So, for the sake of clarity, my Hummy will only boot using the "Custom Firmware" irrespective of which disk is fitted.

I have NOT yet tried the CF based on the debug kernel, but I will try it tomorrow (Monday) evening when I again have time. To recap, irrespective of which disk is installed, my Hummy fails to boot using the "Custom Firmware with Stock Kernel", but does boot successfully with the "Custom...

My understanding is that there THREE versions of the CF, each based on firmware version 1.03.12. The "default" CF appears to be the one labelled as "Custom Firmware" on the download page. In addition there are two versions labelled "Custom Firmware with Debug Kernel" and "Custom Firmware with...

First, thanks to antipodean for these further thoughts. Could very well be the basis of the problem in spite of the disk labels claiming that both disks are running the same version of the firmware. I have done some additional checks and remain as confused as before: I allowed the reformatting...

Thank you to MartinLiddle and Black Hole for their explanations. I will start by downloading the standard kernel version of the CF, and go from there. I'll report back sometime tomorrow.

There's no need for the accusative tone. Instead, why not EXPLAIN why I might have more success with the standard and debug kernels? Is there some feature of the kernel compiled by af123 that might be preventing the disk being detected? I genuinely want to learn.

That's the output AFTER having deleted the only partition on the disk. Perhaps it's not so strange. I am now doing a complete reformat (exFAT) of the disk in Windows 10, but it's a slow process and I'll report back later. I remain of the opinion that the disk is defective in some way that's...

1. It is the usual version with the kernel compiled by af123: HDR_FOX_T2_1.03.12_mod_3.13.zip 3. The colons are exactly as seen in the output from running the command from the CLI using PuTTY to telnet in. Breaking news: I installed a smaller Seagate disk (80 GB) which was still formatted in...

Many thanks for the additional ideas. Answering them in order: 1. The CF is 3.13. 2. I deleted the partition and refitted the drive. Still not detected. 3. The output is: ls: /sys/block/s*: No such file or directory

Many thanks for the prompt reply. It's not a jumper issue: no jumpers on either disk. Both disks have the same firmware installed too.

The original HDD in my HDR-Fox T2 was accumulating errors and I had had to recover several defective sectors using the tools provided in the CF. I purchased a used replacement disk on eBay which had come from an upgraded Sky box. It's the identical make and model (Seagate Pipeline HD 2...

Thanks. That was the problem. In my defence, I'm new to HD on Freeview.