HDR FOX T2 stops seeing the hard drive

ABMorley

Member
I'm posting this to the custom firmware forum, although in fact it started happening before I upgraded to custom firmware.

We were on the most recent OTA version (I forget 1.02.20 I think - mayeb 28).

The box had been operating nicely since it arrived in April 2011. However over the last few months we've had increased occurrences of the following:
  • If watching recorded material it suddenly stops and enters live TV
  • If watching live TV, pressing <Media> does nothing at all.
  • If watching live TV, pressing pause shows the "not allowed" symbol in the top right.
Once in this state, <Menu> --> Settings --> System --> Data storage is greyed out.
It's almost as if it's become an HD FOX T2.

This happened very occasionally but it has become more recent over the past few months. Now it's daily and the box is almost unusable. As standard the box has

First thing I did was upgrade to (standard) s/w 1.02.32. But that didn't stop it.
So I upgraded to custom s/w HDR_FOX_T2_1.02.32_mod_2.19.zip
Problem still happens, but at least I can have a go at diagnosis.

Obvious first step: Check the hard drive. fix-disk reported nothing untoward :

Code:
----------------------------------------------------------------------
Fix-disk run starting...
----------------------------------------------------------------------
 
 
Checking disk sda
 
Running short disk self test
 
No pending sectors found - skipping sector repair
 
Checking partition /dev/sda3...
Pass 1: Checking inodes, blocks, and sizes
/dev/sda3: |                                                        |  0.9% 
[...]
                                                                             
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/dev/sda3: |====================================================    - 92.0% 
                                                                             
/lost+found not found.  Create? yes
 
Pass 4: Checking reference counts
[...]                                                                             
Pass 5: Checking group summary information
/dev/sda3: |=====================================================  - 95.5% 
/dev/sda3: |======================================================  \ 96.0% 
/dev/sda3: |======================================================  | 96.4% 
/dev/sda3: |======================================================  / 96.9% 
/dev/sda3: |======================================================  - 97.3% 
/dev/sda3: |======================================================= \ 98.5% 
/dev/sda3: |========================================================| 100.0% 
                                                                             

/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda3: 13/655776 files (0.0% non-contiguous), 194554/2622611 blocks
 
Checking partition /dev/sda1...
Pass 1: Checking inodes, blocks, and sizes
/dev/sda1: |====                                                    |  7.8% 
/dev/sda1: |=========                                              / 15.6% 
/dev/sda1: |=============                                          - 23.3% 
/dev/sda1: |=================                                      \ 31.1% 
/dev/sda1: |======================                                  | 38.9% 
/dev/sda1: |==========================                              / 46.7% 
/dev/sda1: |==============================                          - 54.4% 
/dev/sda1: |=======================================                \ 70.0% 
                                                                             
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create? yes
 
Pass 4: Checking reference counts
/dev/sda1: |====================================================    | 92.3% 
                                                                             
Pass 5: Checking group summary information
/dev/sda1: |======================================================  / 96.9% 
/dev/sda1: |========================================================| 100.0% 
                                                                             

/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 14/65808 files (0.0% non-contiguous), 13543/263064 blocks
 
Checking partition /dev/sda2...
Pass 1: Checking inodes, blocks, and sizes
/dev/sda2: |                                                        |  0.1% 
[...]
/dev/sda2: |=======================================                \ 70.0% 
                                                                             
Pass 2: Checking directory structure
/dev/sda2: |=======================================                | 70.4% 
[...]                                                                            
Pass 3: Checking directory connectivity
/dev/sda2: |==================================================      / 90.1% 
                                                                             
/lost+found not found.  Create? yes
 
Pass 4: Checking reference counts
/dev/sda2: |====================================================    - 92.1% 
[...]                                                                            
Pass 5: Checking group summary information
/dev/sda2: |=====================================================  | 95.1% 
[...]
/dev/sda2: |========================================================| 100.0% 
                                                                             

/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda2: 1070/60334080 files (23.6% non-contiguous), 129007877/241304332 blocks
 
----------------------------------------------------------------------
Fix-disk run ended.
----------------------------------------------------------------------

Looks to me to be OK.
 
Continued:
Next check the SMART results. Nothing untoward there. Trigger a long SMART test. Nothing untoward there either. Here's the smartctl logs:

Code:
humax# smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-11 by Bruce Allen, ----smartmontools.sourceforge.net
 
=== START OF INFORMATION SECTION ===
Model Family:    Seagate Pipeline HD 5900.2
Device Model:    ST31000424CS
Serial Number:    9VX162Q1
LU WWN Device Id: 5 000c50 02d6a8f1b
Firmware Version: SC13
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:  8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sat Nov 23 23:21:03 2013 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:      (  0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
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:        ( 219) 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  110  099  006    Pre-fail  Always      -      27237162
  3 Spin_Up_Time            0x0003  096  096  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  096  096  020    Old_age  Always      -      4266
  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0
  7 Seek_Error_Rate        0x000f  075  060  030    Pre-fail  Always      -      4335026032
  9 Power_On_Hours          0x0032  098  098  000    Old_age  Always      -      2256
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
12 Power_Cycle_Count      0x0032  098  098  020    Old_age  Always      -      2133
184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0
187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0
188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0
189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0
190 Airflow_Temperature_Cel 0x0022  065  044  045    Old_age  Always  In_the_past 35 (0 43 35 35)
194 Temperature_Celsius    0x0022  035  056  000    Old_age  Always      -      35 (0 17 0 0)
195 Hardware_ECC_Recovered  0x001a  046  037  000    Old_age  Always      -      27237162
197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0
198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0
199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      0
 
SMART Error Log Version: 1
No Errors Logged
 
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline      Completed without error      00%      2237        -
# 2  Extended offline    Completed without error      00%      2230        -
# 3  Short offline      Completed without error      00%      2227        -
# 4  Short offline      Completed without error      00%      2212        -
# 5  Short offline      Completed without error      00%      2212        -
# 6  Short offline      Completed without error      00%      2212        -
# 7  Short offline      Completed without error      00%      2212        -
# 8  Short offline      Completed without error      00%      2208        -
# 9  Short offline      Completed without error      00%      2202        -
#10  Short offline      Completed without error      00%      2202        -
#11  Short offline      Completed without error      00%      2156        -
#12  Short offline      Completed without error      00%      1046        -
 
SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    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.

Any clues? Doesn't look like a hard drive problem. Any ideas where to look next?

One clue. While we were messing around with the humax, the problem happened. I then tried to access the drive and we distinctly heard it spin up - despite the fact that we did not reckon it should have gone to sleep.

Another clue. In rag.log (what's that?) At first I see:
Code:
humax# cat rag.log
 
--------- Info for Modinit PID 384 ---------
384: Date:      Fri Nov 22 19:44:21 GMT 2013
384: MDEV:      sda1
384: ACTION:    add
384: Model:      HDR
384: Device:    /dev/sda1
384: Disk:      sda
 
384:22/11/2013 19:44: Waiting for disk to become ready...
384:22/11/2013 19:44:  disk ready after 0 seconds
384:22/11/2013 19:44: /dev/sda1 is formatted as ext2/3
384:22/11/2013 19:44: /dev/sda1 is NOT removable.
384:22/11/2013 19:44: Waiting for the disk to mount...
 
--------- Info for Modinit PID 400 ---------
400: Date:      Fri Nov 22 19:44:21 GMT 2013
400: MDEV:      sda3
400: ACTION:    add
400: Model:      HDR
400: Device:    /dev/sda3
400: Disk:      sda
 
 
--------- Info for Modinit PID 380 ---------
380: Date:      Fri Nov 22 19:44:21 GMT 2013
380: MDEV:      sda2
380: ACTION:    add
380: Model:      HDR
380: Device:    /dev/sda2
380: Disk:      sda
 
400:22/11/2013 19:44: Waiting for disk to become ready...
380:22/11/2013 19:44: sda2 is candidate for mod [/mnt/hd2]
380:22/11/2013 19:44: Waiting for disk to become ready...
380:22/11/2013 19:44:  disk ready after 0 seconds
380:22/11/2013 19:44: /dev/sda2 is formatted as ext2/3
380:22/11/2013 19:44: /dev/sda2 is NOT removable.
380:22/11/2013 19:44: Waiting for the disk to mount...
400:22/11/2013 19:44:  disk ready after 0 seconds
400:22/11/2013 19:44: /dev/sda3 is formatted as ext2/3
400:22/11/2013 19:44: /dev/sda3 is NOT removable.
400:22/11/2013 19:44: Waiting for the disk to mount...
384:22/11/2013 19:44:  /dev/sda1 mounted on /mnt/hd1
384:22/11/2013 19:44:  mounted after 0 seconds.
384:22/11/2013 19:44: Waiting for modinit to complete.
384:22/11/2013 19:44:  still waiting...
380:22/11/2013 19:44:  /dev/sda2 mounted on /mnt/hd2
380:22/11/2013 19:44:  mounted after 0 seconds.
380:22/11/2013 19:44: +++ Running modinit +++
400:22/11/2013 19:44:  /dev/sda3 mounted on /mnt/hd3
400:22/11/2013 19:44:  mounted after 0 seconds.
400:22/11/2013 19:44: Waiting for modinit to complete.
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
384:22/11/2013 19:44:  still waiting...
400:22/11/2013 19:44:  still waiting...
380:22/11/2013 19:44: +++ Modinit complete +++
380:22/11/2013 19:44: sda: Non-removable disk, skipping package scan.
384:22/11/2013 19:44:  completed after 13 seconds.
384:22/11/2013 19:44: sda: Non-removable disk, skipping package scan.
400:22/11/2013 19:44:  completed after 13 seconds.
400:22/11/2013 19:44: sda: Non-removable disk, skipping package scan.

So far no problem. Then the problem happened, about 20 minutes in:

Code:
400:22/11/2013 19:44: sda: Non-removable disk, skipping package scan.
 
--------- Info for Modinit PID 1389 ---------
1389: Date:      Fri Nov 22 20:04:16 GMT 2013
1389: MDEV:      sda2
1389: ACTION:    remove
1389: Model:      HDR
1389: Device:    /dev/sda2
1389: Disk:      sda
 
 
--------- Info for Modinit PID 1380 ---------
1380: Date:      Fri Nov 22 20:04:16 GMT 2013
1380: MDEV:      sda3
1380: ACTION:    remove
1380: Model:      HDR
1380: Device:    /dev/sda3
1380: Disk:      sda
 
1389:22/11/2013 20:04: Mount point: /mnt/hd2
 
--------- Info for Modinit PID 1416 ---------
1416: Date:      Fri Nov 22 20:04:17 GMT 2013
1416: MDEV:      sda1
1416: ACTION:    remove
1416: Model:      HDR
1416: Device:    /dev/sda1
1416: Disk:      sda
 
1380:22/11/2013 20:04: Mount point: /mnt/hd3
umount: can't forcibly umount /dev/sda3: Invalid argument
rmdir: '/mnt/hd2': Read-only file system
rmdir: '/mnt/hd3': Read-only file system
 
--------- Info for Modinit PID 1505 ---------
1505: Date:      Fri Nov 22 20:33:38 GMT 2013
1505: MDEV:      sdb3
1505: ACTION:    add
1505: Model:      HDR
1505: Device:    /dev/sdb3
1505: Disk:      sdb
 
 
--------- Info for Modinit PID 1497 ---------
1497: Date:      Fri Nov 22 20:33:38 GMT 2013
1497: MDEV:      sdb1
1497: ACTION:    add
1497: Model:      HDR
1497: Device:    /dev/sdb1
1497: Disk:      sdb
 
 
--------- Info for Modinit PID 1499 ---------
1499: Date:      Fri Nov 22 20:33:38 GMT 2013
1499: MDEV:      sdb2
1499: ACTION:    add
1499: Model:      HDR
1499: Device:    /dev/sdb2
1499: Disk:      sdb
 
1497:22/11/2013 20:33: Waiting for disk to become ready...
1505:22/11/2013 20:33: Waiting for disk to become ready...
1497:22/11/2013 20:33:  disk ready after 0 seconds
1505:22/11/2013 20:33:  disk ready after 0 seconds
1497:22/11/2013 20:33: /dev/sdb1 is formatted as ext2/3
1497:22/11/2013 20:33: /dev/sdb1 is NOT removable.
1497:22/11/2013 20:33: Waiting for the disk to mount...
1499:22/11/2013 20:33: sdb2 is candidate for mod [/mnt/hd2]
1499:22/11/2013 20:33: Waiting for disk to become ready...
1499:22/11/2013 20:33:  disk ready after 0 seconds
1505:22/11/2013 20:33: /dev/sdb3 is formatted as ext2/3
1499:22/11/2013 20:33: /dev/sdb2 is formatted as ext2/3
1505:22/11/2013 20:33: /dev/sdb3 is NOT removable.
1499:22/11/2013 20:33: /dev/sdb2 is NOT removable.
1505:22/11/2013 20:33: Waiting for the disk to mount...
1499:22/11/2013 20:33: Waiting for the disk to mount...
1497:22/11/2013 20:33:  /dev/sdb1 mounted on /mnt/hd1
1497:22/11/2013 20:33:  mounted after 0 seconds.
1505:22/11/2013 20:33:  /dev/sdb3 mounted on /mnt/hd3
1499:22/11/2013 20:33:  /dev/sdb2 mounted on /mnt/hd2
1505:22/11/2013 20:33:  mounted after 0 seconds.
1497:22/11/2013 20:33: sdb: Non-removable disk, skipping package scan.
1505:22/11/2013 20:33: sdb: Non-removable disk, skipping package scan.
1499:22/11/2013 20:33:  mounted after 0 seconds.
1499:22/11/2013 20:33: +++ Running modinit +++
1499:22/11/2013 20:33: +++ Modinit complete +++
1499:22/11/2013 20:33: sdb: Non-removable disk, skipping package scan.

It looks to me that the drive somehow got "removed" then, nearly half-an-hour later got added again. This latter bit coincided with the driver spinning up again.

The story repeats:

Code:
1499:22/11/2013 20:33: sdb: Non-removable disk, skipping package scan.
 
--------- Info for Modinit PID 4052 ---------
4052: Date:      Fri Nov 22 21:44:50 GMT 2013
4052: MDEV:      sdb3
4052: ACTION:    remove
4052: Model:      HDR
4052: Device:    /dev/sdb3
4052: Disk:      sdb
 
 
--------- Info for Modinit PID 4063 ---------
4063: Date:      Fri Nov 22 21:44:50 GMT 2013
4063: MDEV:      sdb1
4063: ACTION:    remove
4063: Model:      HDR
4063: Device:    /dev/sdb1
4063: Disk:      sdb
 
 
--------- Info for Modinit PID 4060 ---------
4060: Date:      Fri Nov 22 21:44:50 GMT 2013
4060: MDEV:      sdb2
4060: ACTION:    remove
4060: Model:      HDR
4060: Device:    /dev/sdb2
4060: Disk:      sdb
 
4052:22/11/2013 21:44: Mount point: /mnt/hd3
4060:22/11/2013 21:44: Mount point: /mnt/hd2
4063:22/11/2013 21:44: Mount point: /mnt/hd1
umount: can't forcibly umount /dev/sdb1: Invalid argument
rmdir: '/mnt/hd3': Read-only file system
rmdir: '/mnt/hd2': Read-only file system
rmdir: '/mnt/hd1': Read-only file system
 
--------- Info for Modinit PID 4140 ---------
4140: Date:      Fri Nov 22 21:45:01 GMT 2013
4140: MDEV:      sdc3
4140: ACTION:    add
4140: Model:      HDR
4140: Device:    /dev/sdc3
4140: Disk:      sdc
 
 
--------- Info for Modinit PID 4138 ---------
4138: Date:      Fri Nov 22 21:45:01 GMT 2013
4138: MDEV:      sdc2
4138: ACTION:    add
4138: Model:      HDR
4138: Device:    /dev/sdc2
4138: Disk:      sdc
 
 
--------- Info for Modinit PID 4133 ---------
4133: Date:      Fri Nov 22 21:45:01 GMT 2013
4133: MDEV:      sdc1
4133: ACTION:    add
4133: Model:      HDR
4133: Device:    /dev/sdc1
4133: Disk:      sdc
 
4140:22/11/2013 21:45: Waiting for disk to become ready...
4133:22/11/2013 21:45: Waiting for disk to become ready...
4133:22/11/2013 21:45:  disk ready after 0 seconds
4133:22/11/2013 21:45: /dev/sdc1 is formatted as ext2/3
4133:22/11/2013 21:45: /dev/sdc1 is NOT removable.
4133:22/11/2013 21:45: Waiting for the disk to mount...
4138:22/11/2013 21:45: sdc2 is candidate for mod [/mnt/hd2]
4138:22/11/2013 21:45: Waiting for disk to become ready...
4138:22/11/2013 21:45:  disk ready after 0 seconds
4138:22/11/2013 21:45: /dev/sdc2 is formatted as ext2/3
4140:22/11/2013 21:45:  disk ready after 0 seconds
4138:22/11/2013 21:45: /dev/sdc2 is NOT removable.
4138:22/11/2013 21:45: Waiting for the disk to mount...
4140:22/11/2013 21:45: /dev/sdc3 is formatted as ext2/3
4140:22/11/2013 21:45: /dev/sdc3 is NOT removable.
4140:22/11/2013 21:45: Waiting for the disk to mount...
4133:22/11/2013 21:45:  /dev/sdc1 mounted on /mnt/hd1
4133:22/11/2013 21:45:  mounted after 0 seconds.
4133:22/11/2013 21:45: sdc: Non-removable disk, skipping package scan.
4140:22/11/2013 21:45:  still waiting...
4138:22/11/2013 21:45:  /dev/sdc2 mounted on /mnt/hd2
4138:22/11/2013 21:45:  mounted after 0 seconds.
4138:22/11/2013 21:45: +++ Running modinit +++
4140:22/11/2013 21:45:  /dev/sdc3 mounted on /mnt/hd3
4140:22/11/2013 21:45:  mounted after 1 second.
4140:22/11/2013 21:45: sdc: Non-removable disk, skipping package scan.
4138:22/11/2013 21:45: +++ Modinit complete +++
4138:22/11/2013 21:45: sdc: Non-removable disk, skipping package scan.

So, for anyone who has followed so far.... Any ideas? Seen anything like it?

Thanks so much,

Andrew
 
I've never heard of anything like it on here. The disk is going away then coming back as the next device ID. So it starts as /dev/sda then becomes /dev/sdb then /dev/sdc. Everything about the disk looks fine though from what you've posted.

If you check the smarctl stats between these episodes, does it show an additional start/stop or power cycle?

Code:
humax# smartctl -A /dev/sda | egrep 'Start_|Power_'
  4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       3010
  9 Power_On_Hours          0x0032   096   096   000    Old_age   Always       -       4084
 12 Power_Cycle_Count       0x0032   098   098   020    Old_age   Always       -       3010

Unfortunately one of the things that might give more information, kernel logging, isn't present in the stock Humax kernel. It is possible to run a custom kernel with this turned on though. Might be worth a try - let me know if you want me to build one for you to try.

It does sound like a physical problem - the power cycle count should indicate whether it's likely to be power related.
 
They say that a watched kettle never boils. Well, a telnetted-into-hummy's drive never reappears. But it has at last. af123's suggestion followed:

Code:
Let's compare before and after smart data:
Before:
ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate    0x000f  114  099  006    Pre-fail  Always      -      65819927
  3 Spin_Up_Time            0x0003  097  096  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  096  096  020    Old_age  Always      -      4290
  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0
  7 Seek_Error_Rate        0x000f  075  060  030    Pre-fail  Always      -      4335219929
  9 Power_On_Hours          0x0032  098  098  000    Old_age  Always      -      2265
 10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
 12 Power_Cycle_Count      0x0032  098  098  020    Old_age  Always      -      2145
184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0
187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0
188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0
189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0
190 Airflow_Temperature_Cel 0x0022  079  044  045    Old_age  Always  In_the_past 21 (0 43 21 21)
194 Temperature_Celsius    0x0022  021  056  000    Old_age  Always      -      21 (0 17 0 0)
195 Hardware_ECC_Recovered  0x001a  045  037  000    Old_age  Always      -      65819927
197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0
198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0
199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      0

After:
Code:
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  114  099  006    Pre-fail  Always      -      66020056
  3 Spin_Up_Time            0x0003  096  096  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  096  096  020    Old_age  Always      -      4292  <--- +2
  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0
  7 Seek_Error_Rate        0x000f  075  060  030    Pre-fail  Always      -      4335220476
  9 Power_On_Hours          0x0032  098  098  000    Old_age  Always      -      2265  <--- Same
 10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
 12 Power_Cycle_Count      0x0032  098  098  020    Old_age  Always      -      2146  <--- +1
184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -      0
187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0
188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0
189 High_Fly_Writes        0x003a  100  100  000    Old_age  Always      -      0
190 Airflow_Temperature_Cel 0x0022  064  044  045    Old_age  Always  In_the_past 36 (0 43 36 36)
194 Temperature_Celsius    0x0022  036  056  000    Old_age  Always      -      36 (0 17 0 0)
195 Hardware_ECC_Recovered  0x001a  045  037  000    Old_age  Always      -      66020056
197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0
198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -      0
199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      0

A question: Would a soft power down (issued from computer) followed by a soft power up increment the power cycle counter, or does that only count hard (power disconnection) events?

Added: Why don't I look it up on Wikipedia? It says it is "count of full hard disk power on/off cycles". Implies to me power supply problems.

Full log in attached file - you can see it moved from sda to sdb.

Sounds like it might be time to reach for the screwdriver.

Thanks for all your advice.

Andrew
 

Attachments

  • Hummy posting 2.txt
    34.6 KB · Views: 4
Yes, I'd suspect an issue with the power supply. Hopefully something that can be easily repaired.
 
Firstly, Humax have graded (ie ex-demo or repaired) HDR FOX-T2s. Actually I've only just seen they've got both the 500Gb and 1Tb ones. Worth stocking up on. I've ordered one - unfortunately the 500Gb one because I hadn't spotted the 1Tb one. Hard drive swap planned.

Anyway, time for an update, especially as Humax's service department have just asked me what happened so I can cut 'n' paste.
What seems to happen is that when the product is working correctly, the 12v and 5v supplies to the hard drive come up. When in this fault condition the supplies either briefly come up and then fall back to 0v or they don't even come up at all.

My suspicion is that there is a problem with the power supply board and its hard drive rails are failing. However it is interesting that it is both the 12 and 5v rails for the HD that fail - so it could be a problem with the signal on the motherboard that generates the hard drive power supply enable signal. It appears that the main motherboard power supply is OK as I assume the whole system would fail if it wasn't.

So, either:
  • The power supply is failing on its HD outputs
  • Or there's a problem with the output on the mother board that drives the enable signal to the PSU
  • Or there's a dodgy connection.
I suppose it's possible there might be a hard drive problem that effectively short-circuits the PSU, but I doubt it. If I had the service manual I would be able to probe the enable signal.

Humax's service department say they offer an exchange/repair service. Be interested to hear what it costs. But in the meantime I now have one that works and, if their repair isn't to pricey, maybe two. What I'd really like is the service manual, of course.
 
My guess is £110. Ask if you can buy a power supply from them, it is an easy repair and will be a lot cheaper. Of course, this is a risk as it might not be the power supply.
 
Given I could have a graded one for £140 - http://www1.humaxdirect.co.uk/Direct/prod/e4cdfbf3-14c2-4f8f-ac60-b08241aeacef - I can't see myself paying £110. Yes, it'd be nice to be able to get spares. Hmmm. Wonder if eSpares (http://www.espares.co.uk/) would be interested in getting into consumer electronics. They've found specific parts for kitchen devices for me in the past.

Anyway, I'll see what Hummy's support person turns up next week.

BTW The new machines all come with new firmware, dated 10 Dec 2103.
 
Given I could have a graded one for £140 - http://www1.humaxdirect.co.uk/Direct/prod/e4cdfbf3-14c2-4f8f-ac60-b08241aeacef - I can't see myself paying £110. Yes, it'd be nice to be able to get spares. Hmmm. Wonder if eSpares (http://www.espares.co.uk/) would be interested in getting into consumer electronics. They've found specific parts for kitchen devices for me in the past.

Anyway, I'll see what Hummy's support person turns up next week.

BTW The new machines all come with new firmware, dated 10 Dec 2103.
Humax sold me a replacement front panel board a couple of weeks ago, if they have stock they will probably sell you a new power supply. You can pay over the phone with a card on 08446698800. No regular telephone number, I'm afraid.
 
Humax sold me a replacement front panel board a couple of weeks ago, if they have stock they will probably sell you a new power supply. You can pay over the phone with a card on 08446698800. No regular telephone number, I'm afraid.


Try tel:020 8326 6000 BUT DON'T select any options, wait for operator. They can then put you through to appropriate dept (support!).
I usually just say that "I need to talk to somebody about ..." rather than asking directly for "support".
 
MontysEvilTwin was nearly right - around £150 to repair or £130 to exchange. So the graded stock at £140 is something of a no-brainer and I'll swap the hard drive. Still, I might try calling them for a new PSU board anyway. My mum could do with a PVR....
Thanks all who offered advice. Case closed. I'm now reasonably convinced it's a PSU problem.
 
Here's how I got on. 020 8326 6000 was no use, even trying HarveyB's suggestion. They could send me a new board for £130. I wasn't at all sure they understood what I wanted.

But 08446698800 was the right number. For £20, inc VAT, P&P they sent me a new PSU board. That's excellent - and the availability of spares to the casual tinkerer puts me in a positive state of mind when it comes to any future purchases from Humax. What excellent customer service.

However the bad news is: Even with the new board the problem persists. I'm inclined to cut my losses.

I had been running auto-decrypt (or was it unencrypt - I forget). So swapping the HD into a different unit should do the trick..... I think?
 
If everything is decrypted, fitting the HDD into another HDR-FOX (or as an external USB drive) should be fine.
 
Even with the new board the problem persists. I'm inclined to cut my losses.

I had been running auto-decrypt (or was it unencrypt - I forget). So swapping the HD into a different unit should do the trick..... I think?
I had a similar problem to this in a PC at work a couple of years ago. It wasn't the PC that was at fault, it was the disk. It would intermittently just disappear from the controller for no apparent reason. Put a new disk in and no more problems with that machine.
 
Back
Top