No internal disk found

Skeetman

New Member
Hi there fellow Humax users. I am new to this custom firmware game, so please bear with me.
I have an old HDR-FoxT2 which I have reconnected up to a TV. It boots up ok and appears ok, but wont play anything that is stored upon it. It just sits there with "Deleting" showing in the upper rh corner. I seem to remember that that is why we went out and got a new Humax.
Anyway, I have successfully downloaded and installed the 3.13 cfw, After booting the device back it shows as custom firmware 3.13 on the front screen. If I attempt to connect to the web interface (everything is LAN connected, not WiFi), I get the following:
upload_2017-11-17_10-34-59.png

Not quite knowing what to do next, I re-installed the official firmware and got back to the original "Deleting" issue.

Any thoughts as to what to do next, or what information I can provide to assist you in determining my problem?
Thank you in advance.
 
Reinstall the CF. Then go to Access Telnet Menu as shown above and reboot in to Maintenance Mode and then run the Fixdisk process. That will fix whatever is wrong with it, if it can be fixed. Otherwise you might need a new disk.
Given the above message though, it seems like it isn't seeing the disk at all. So it's either complete disk fail or motherboard-disk interface fail. The latter means it goes in the WEEE bin.
 
Thank you prpr.
I have re-instated the cfw 3.13 and re-booted. This time we have:
upload_2017-11-17_13-23-0.png
I used the handset to look at the videos screen and that indicated that "Deleting" was still taking place.
I was able to access BBC Sport through the Portal.
I clicked on "Download & Install the Full Web Interface" and got:
upload_2017-11-17_13-32-3.png
I then clicked on "Reboot System" and got the first screen (shown above) again.
I clicked on "Access Telnet Menu" and then entered the PIN when requested.
I then entered "maint" mode and confirmed it.
I then clicked on "Connect" and entered the PIN when requested.
I then ran "fixdisk" with no options selected.
This is where we are so far:
upload_2017-11-17_13-40-19.png

So I guess we wait and see and hope?
It was showing lots of films etc on there, so fingers crossed!
 
So I guess we wait and see and hope?
Yes. And when it asks you at the end whether you're having problems with a delete loop, answer 'y'.
Also, once it's done, it will be worthwhile selecting the 'cli' option and then entering this command:
Code:
humax# smartctl -a /dev/sda
and then posting the results (then 'exit' gets you back to the menu).
 
Thank you again for taking the time to read this prpr.

When the fixdisk completed, it did not ask anything about problems with a delete loop, so I continued as per your instuctions.

Code:
Humax HDR-Fox T2 (humax) 1.03.12/3.13
To return to the menu, type: exit
humax# smartctl -a /dev/sda
smartctl 6.4 2015-06-04 r4109 [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke,
=== START OF INFORMATION SECTION ===
Model Family: Seagate Pipeline HD 5900.2
Device Model: ST31000424CS
Serial Number: 5VX1ECMG
LU WWN Device Id: 5 000c50 02feca711
Firmware Version: SC13
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5900 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Sun Jan 3 21:05:41 1971 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 623) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 215) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103b) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 101 099 006 Pre-fail Always - 32976617
3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 099 020 Old_age Always - 1
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 085 060 030 Pre-fail Always - 0
9 Power_On_Hours 0x0032 061 061 000 Old_age Always - 34870
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 968
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 1428
188 Command_Timeout 0x0032 100 083 000 Old_age Always - 141736083489
189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 2399
190 Airflow_Temperature_Cel 0x0022 067 040 045 Old_age Always In_the_past 33 (Min/Max 33/41 #464)
194 Temperature_Celsius 0x0022 033 060 000 Old_age Always - 33 (0 12 0 0 0)
195 Hardware_ECC_Recovered 0x001a 048 035 000 Old_age Always - 32976617
197 Current_Pending_Sector 0x0012 084 084 000 Old_age Always - 677
198 Offline_Uncorrectable 0x0010 084 084 000 Old_age Offline - 677
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 1428 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 1428 occurred at disk power-on lifetime: 34868 hours (1452 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 ff ff ff ef 00 1d+17:18:33.888 READ DMA EXT
ec 00 00 9c 28 9c a0 00 1d+17:18:33.858 IDENTIFY DEVICE
25 00 08 ff ff ff ef 00 1d+17:18:32.524 READ DMA EXT
ec 00 00 9c 28 9c a0 00 1d+17:18:32.495 IDENTIFY DEVICE
25 00 08 ff ff ff ef 00 1d+17:18:31.110 READ DMA EXT
Error 1427 occurred at disk power-on lifetime: 34868 hours (1452 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 ff ff ff ef 00 1d+17:18:32.524 READ DMA EXT
ec 00 00 9c 28 9c a0 00 1d+17:18:32.495 IDENTIFY DEVICE
25 00 08 ff ff ff ef 00 1d+17:18:31.110 READ DMA EXT
ec 00 00 9c 28 9c a0 00 1d+17:18:31.081 IDENTIFY DEVICE
25 00 08 ff ff ff ef 00 1d+17:18:29.717 READ DMA EXT
Error 1426 occurred at disk power-on lifetime: 34868 hours (1452 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 ff ff ff ef 00 1d+17:18:31.110 READ DMA EXT
ec 00 00 9c 28 9c a0 00 1d+17:18:31.081 IDENTIFY DEVICE
25 00 08 ff ff ff ef 00 1d+17:18:29.717 READ DMA EXT
ec 00 00 9c 28 9c a0 00 1d+17:18:29.687 IDENTIFY DEVICE
25 00 08 ff ff ff ef 00 1d+17:18:28.384 READ DMA EXT
Error 1425 occurred at disk power-on lifetime: 34868 hours (1452 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 ff ff ff ef 00 1d+17:18:29.717 READ DMA EXT
ec 00 00 9c 28 9c a0 00 1d+17:18:29.687 IDENTIFY DEVICE
25 00 08 ff ff ff ef 00 1d+17:18:28.384 READ DMA EXT
ec 00 00 9c 28 9c a0 00 1d+17:18:28.355 IDENTIFY DEVICE
25 00 08 ff ff ff ef 00 1d+17:18:27.021 READ DMA EXT
Error 1424 occurred at disk power-on lifetime: 34868 hours (1452 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 ff ff ff ef 00 1d+17:18:28.384 READ DMA EXT
ec 00 00 9c 28 9c a0 00 1d+17:18:28.355 IDENTIFY DEVICE
25 00 08 ff ff ff ef 00 1d+17:18:27.021 READ DMA EXT
ec 00 00 9c 28 9c a0 00 1d+17:18:26.992 IDENTIFY DEVICE
25 00 08 ff ff ff ef 00 1d+17:18:25.668 READ DMA EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Selective offline Completed: read failure 90% 34831 1429958365
# 2 Selective offline Completed: read failure 90% 34831 1429958364
# 3 Selective offline Completed: read failure 90% 34831 1429958363
# 4 Selective offline Completed: read failure 90% 34831 1429958362
# 5 Selective offline Completed: read failure 90% 34831 1429958361
# 6 Selective offline Completed: read failure 90% 34831 1429958360
# 7 Selective offline Completed: read failure 90% 34831 1429956610
# 8 Selective offline Completed: read failure 90% 34831 1429956607
# 9 Selective offline Completed: read failure 90% 34831 1429956606
#10 Selective offline Completed: read failure 90% 34831 1429956605
#11 Selective offline Completed: read failure 90% 34831 1429956604
#12 Selective offline Completed: read failure 90% 34831 1429956603
#13 Selective offline Completed: read failure 90% 34831 1429956602
#14 Selective offline Completed: read failure 90% 34831 1429954850
#15 Selective offline Completed: read failure 90% 34831 1429954849
#16 Selective offline Completed: read failure 90% 34831 1429954848
#17 Selective offline Completed: read failure 90% 34831 1429954847
#18 Selective offline Completed: read failure 90% 34831 1429954846
#19 Selective offline Completed: read failure 90% 34831 1429954845
#20 Selective offline Completed: read failure 90% 34831 1429954844
#21 Selective offline Completed: read failure 90% 34831 1429951085
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 1429958364 1953525167 Completed_read_failure [90% left] (1429958364-1430023899)
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
humax#
 
The values of attributes 197 and 198 are a significant concern; you want the values that are currently 677 to be zero. Try running fixdisk again.
 
When the fixdisk completed, it did not ask anything about problems with a delete loop, so I continued as per your instuctions.
There are several things I don't like about those stats.
I think you would be well advised to: a) not record on it any more; b) run fixdisk to see if any of those sectors will repair; c) back up what you can; d) buy a new disk ASAP.
 
Seems like we have got someone here who asks first and buys later.:)
What a good idea.:laugh:
 
I am happy to attempt the disc change over.
Having now been able to load the web browser, I can see what we have on the disc and thereby work out what we would like to keep/transfer over to our FVP-4000T or our Netgear ReadyNAS (preference).

Am I better to click on OPT then Download on each file, or transfer using FTP? Or maybe some other method?

Thank you for your contribution MartinLiddle, (I didn't like the 677's either, they are now up to 711) but I will replace the disc.
 
Am I better to click on OPT then Download on each file, or transfer using FTP? Or maybe some other method?
You need to tell us whether the recordings are currently decrypted to get meaningful advice?
Thank you for your contribution MartinLiddle, (I didn't like the 677's either, they are now up to 711) but I will replace the disc.
I think that is a perfectly reasonable decision.
 
They are a mixture of SD and HD files, and therefore as I understand the details on this website, the HD files are encrypted. I am loathe to do anything further to write to this disc, so am happy to copy them off like that if I can either decrypt later or they will be playable on the FVP-4000T. Does that give you an understanding of my situation?
 
They are a mixture of SD and HD files, and therefore as I understand the details on this website, the HD files are encrypted.
Sorry you are misunderstanding; both SD and HD content is encrypted and only playable on the box that made them until the encryption is removed.
I am loathe to do anything further to write to this disc, so am happy to copy them off like that if I can either decrypt later or they will be playable on the FVP-4000T.
If the old drive is currently readable then the easiest way is to install the new drive and then connect the old drive via a SATA to USB converter (or a USB cradle) and copy all the files back to the Humax.
 
Then that is what I shall do.
Will order an appropriate 2TB drive this evening.
There must be a page on this site that explains how to resetup the OS on this new drive and off we jolly well go....
Thank you all for your help thus far.....I'm sure that I''l be back!
 
There must be a page on this site that explains how to resetup the OS on this new drive and off we jolly well go....
The OS is in flash, not on the hard disk. You will be no worse off than you were in post #1 having already installed the CF.
 
OK, new disk installed and formatted by the OS. The system has consumed 20GB of the 2TB.
I assume that all is good to go now, it still has the 3.13 firmware installed.

I need to connect up the old drive and copy overt the recordings as required.
Can I copy over complete folders, or do I need to create a folder on the new drive and copy over recordings individually?

Many thanks.
 
My first reaction is to say not to cross your bridges until you come to them, but in the spirit of cooperation: you will find the move/copy option is available on the OPT+ menu for folders, and of course there's always the WebIF media browser.

However, the HDR-FOX can get upset when asked to perform a big copy in one go, you might find it more productive to transfer smaller batches.

Here's a radical suggestion for you: leave the recordings where they are and play them from there.
 
Back
Top