• The forum software that supports hummy.tv will be upgraded to XenForo 2.3 on Wednesday the 20th of November 2024 starting at 7pm

    There will be some periods where the forum is unavailable, please bear with us. More details can be found in the upgrade thread.

Graded stock shipping with strange filesystem format?

A

ABMorley

Member
I'm the guy from this thread:

http://hummy.tv/forum/threads/hdr-fox-t2-stops-seeing-the-hard-drive.4234/

But this has nothing to do with that. Instead it concerns the two refurbished (graded) HDR-FOX-T2 boxes. I only got the 500Mb ones as it happens.

Basically, in both cases they've arrived with the hard drive formatted in a way that makes fix-disk fail.

Despite this there are no symptoms visible via the normal consumer UI - they work fine. And both disks check out fine via SMART, though they're obviously old (around 2000 hours runtime).

I attach a ZIP file containing two log files - one huge - containing two different e2fsck -n -f /dev/sda2 runs.



I upgraded the first machine (hostname humax3) from OTA upgrade version (stock 1.03.12) to 1.03.12/2.22 a few weeks ago.

On running fix-disk I was surprised to see loads and loads of errors from e2fsck. In fact e2fsck died as it ran out of memory.

Thinking this might have had something to do with my messing around I reformatted the drive (via the standard Humax UI). But, even after that it still shows up with loads of errors. Logfile is attached - Disk check after reformat (via Humax UI).log. Actually I used e2fsck -n -f /dev/sda2 so as not to write any changes.

So: After a reformat, the disk is in a state that e2fsck is unhappy with.


I left the second machine untouched until a few hours ago. Wanting to see if this was an isolated incident I upgraded to CFW 1.03.12/2.22 and ran e2fsck -n -f /dev/sda2. Thus it should be pretty much as-shipped except for the custom firmware.

Disk check as shipped.log is from this machine (hostname human - unchanged form the default) I have only just upgraded to custom firmware. It was on the OTA upgrade version (stock 1.03.12) until a few hours ago.

I didn't run fix-disk on it - instead I ran: e2fsck -n -f /dev/sda2 so nothing would get changed.

Any idea what's happening?

Possibilities:
  1. Humax is now intentionally using a different tweak of the filesystem - ones that e2fsck is unhappy with. And we need to upgrade e2fsck.
  2. Humax is inadvertently shipping with a weird filesystem set-up. One that reformatting doesn't re-set (so the formatter must be weird too.
  3. Any other ideas?

As I say, physically (via SMART) the disks are fine. And the machine works fine too.


Thanks for any light anyone can shed!


Andrew
 

Attachments

  • Disk check logs.zip
    142.6 KB · Views: 6
Interesting observations. I am sure the real experts will be along soon. Could you post the SMART data for the disk (diagnostics>Hard drive in the custom firmware web interface)?
 
Ok, here they are, although I don't see much untoward.

Here's one:

Code: 
Humax HDR-Fox T2 (humax3) 1.03.12/2.22
 
To return to the menu, type: exit
 
humax3# smartctl -a /dev/sda
smartctl 6.0 2013-04-25 r11898M [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org
 
=== START OF INFORMATION SECTION ===
Model Family:    Seagate Pipeline HD 5900.2
Device Model:    ST3500312CS
Serial Number:    5VVEKNNA
LU WWN Device Id: 5 000c50 05c50996e
Firmware Version: SC13
User Capacity:    500,107,862,016 bytes [500 GB]
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 Mar 16 20:01:49 2014 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:        ( 110) 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  117  100  006    Pre-fail  Always      -      134594524
  3 Spin_Up_Time            0x0003  097  097  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  098  098  020    Old_age  Always      -      2434
  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0
  7 Seek_Error_Rate        0x000f  072  060  030    Pre-fail  Always      -      19808703
  9 Power_On_Hours          0x0032  098  098  000    Old_age  Always      -      2112
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
12 Power_Cycle_Count      0x0032  099  099  020    Old_age  Always      -      1217
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  089  089  000    Old_age  Always      -      11
190 Airflow_Temperature_Cel 0x0022  049  044  045    Old_age  Always  In_the_past 51 (0 4 54 33 0)
194 Temperature_Celsius    0x0022  051  056  000    Old_age  Always      -      51 (0 13 0 0 0)
195 Hardware_ECC_Recovered  0x001a  041  040  000    Old_age  Always      -      134594524
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  Extended offline    Completed without error      00%      2108        -
# 2  Short offline      Completed without error      00%      2106        -
# 3  Short offline      Completed without error      00%      2104        -
# 4  Extended offline    Completed without error      00%      2104        -
# 5  Short offline      Completed without error      00%      2095        -
# 6  Short offline      Completed without error      00%      2095        -
# 7  Short offline      Completed without error      00%      2093        -
# 8  Extended offline    Completed without error      00%      2076        -
# 9  Short offline      Completed without error      00%      2075        -
#10  Short offline      Completed without error      00%      2052        -
 
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.

And here's the other:

Code: 
Humax HDR-Fox T2 (humax2) 1.03.12/2.22
 
To return to the menu, type: exit
 
humax2# 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, http://smartmontools.sourceforge.net
 
=== START OF INFORMATION SECTION ===
Model Family:    Seagate Pipeline HD 5900.2
Device Model:    ST3500312CS
Serial Number:    5VVELDYT
LU WWN Device Id: 5 000c50 05c50cc2d
Firmware Version: SC13
User Capacity:    500,107,862,016 bytes [500 GB]
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:    Sun Mar 16 20:02:56 2014 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:                (  612) 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:        ( 104) 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  106  099  006    Pre-fail  Always      -      11031483
  3 Spin_Up_Time            0x0003  097  097  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  098  098  020    Old_age  Always      -      2802
  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0
  7 Seek_Error_Rate        0x000f  076  060  030    Pre-fail  Always      -      42374037
  9 Power_On_Hours          0x0032  098  098  000    Old_age  Always      -      2081
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
12 Power_Cycle_Count      0x0032  099  099  020    Old_age  Always      -      1401
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  096  096  000    Old_age  Always      -      4
190 Airflow_Temperature_Cel 0x0022  049  044  045    Old_age  Always  In_the_past 51 (0 119 55 50)
194 Temperature_Celsius    0x0022  051  056  000    Old_age  Always      -      51 (0 13 0 0)
195 Hardware_ECC_Recovered  0x001a  048  036  000    Old_age  Always      -      11031483
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  Extended offline    Completed without error      00%      2078        -
# 2  Short offline      Completed without error      00%      2074        -
# 3  Short offline      Completed without error      00%      2074        -
# 4  Short offline      Completed without error      00%      1906        -
# 5  Short offline      Completed without error      00%      1906        -
# 6  Short offline      Completed without error      00%      595        -
 
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.
 
Ok, here they are, although I don't see much untoward.

Here's one:

Code: 
Humax HDR-Fox T2 (humax3) 1.03.12/2.22
 
To return to the menu, type: exit
 
humax3# smartctl -a /dev/sda
smartctl 6.0 2013-04-25 r11898M [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org
 
=== START OF INFORMATION SECTION ===
Model Family:    Seagate Pipeline HD 5900.2
Device Model:    ST3500312CS
Serial Number:    5VVEKNNA
LU WWN Device Id: 5 000c50 05c50996e
Firmware Version: SC13
User Capacity:    500,107,862,016 bytes [500 GB]
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 Mar 16 20:01:49 2014 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:        ( 110) 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  117  100  006    Pre-fail  Always      -      134594524
  3 Spin_Up_Time            0x0003  097  097  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  098  098  020    Old_age  Always      -      2434
  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0
  7 Seek_Error_Rate        0x000f  072  060  030    Pre-fail  Always      -      19808703
  9 Power_On_Hours          0x0032  098  098  000    Old_age  Always      -      2112
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
12 Power_Cycle_Count      0x0032  099  099  020    Old_age  Always      -      1217
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  089  089  000    Old_age  Always      -      11
190 Airflow_Temperature_Cel 0x0022  049  044  045    Old_age  Always  In_the_past 51 (0 4 54 33 0)
194 Temperature_Celsius    0x0022  051  056  000    Old_age  Always      -      51 (0 13 0 0 0)
195 Hardware_ECC_Recovered  0x001a  041  040  000    Old_age  Always      -      134594524
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  Extended offline    Completed without error      00%      2108        -
# 2  Short offline      Completed without error      00%      2106        -
# 3  Short offline      Completed without error      00%      2104        -
# 4  Extended offline    Completed without error      00%      2104        -
# 5  Short offline      Completed without error      00%      2095        -
# 6  Short offline      Completed without error      00%      2095        -
# 7  Short offline      Completed without error      00%      2093        -
# 8  Extended offline    Completed without error      00%      2076        -
# 9  Short offline      Completed without error      00%      2075        -
#10  Short offline      Completed without error      00%      2052        -
 
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.

And here's the other:

Code: 
Humax HDR-Fox T2 (humax2) 1.03.12/2.22
 
To return to the menu, type: exit
 
humax2# 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, http://smartmontools.sourceforge.net
 
=== START OF INFORMATION SECTION ===
Model Family:    Seagate Pipeline HD 5900.2
Device Model:    ST3500312CS
Serial Number:    5VVELDYT
LU WWN Device Id: 5 000c50 05c50cc2d
Firmware Version: SC13
User Capacity:    500,107,862,016 bytes [500 GB]
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:    Sun Mar 16 20:02:56 2014 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:                (  612) 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:        ( 104) 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  106  099  006    Pre-fail  Always      -      11031483
  3 Spin_Up_Time            0x0003  097  097  000    Pre-fail  Always      -      0
  4 Start_Stop_Count        0x0032  098  098  020    Old_age  Always      -      2802
  5 Reallocated_Sector_Ct  0x0033  100  100  036    Pre-fail  Always      -      0
  7 Seek_Error_Rate        0x000f  076  060  030    Pre-fail  Always      -      42374037
  9 Power_On_Hours          0x0032  098  098  000    Old_age  Always      -      2081
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -      0
12 Power_Cycle_Count      0x0032  099  099  020    Old_age  Always      -      1401
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  096  096  000    Old_age  Always      -      4
190 Airflow_Temperature_Cel 0x0022  049  044  045    Old_age  Always  In_the_past 51 (0 119 55 50)
194 Temperature_Celsius    0x0022  051  056  000    Old_age  Always      -      51 (0 13 0 0)
195 Hardware_ECC_Recovered  0x001a  048  036  000    Old_age  Always      -      11031483
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  Extended offline    Completed without error      00%      2078        -
# 2  Short offline      Completed without error      00%      2074        -
# 3  Short offline      Completed without error      00%      2074        -
# 4  Short offline      Completed without error      00%      1906        -
# 5  Short offline      Completed without error      00%      1906        -
# 6  Short offline      Completed without error      00%      595        -
 
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.
 
It's strange that although humax3 and humax2 are both running 1.03.12/2.22 they have different smartmontools versions installed,
humax3 is running :- smartctl 6.0 2013-04-25 r11898M and
humax2 is running :- smartctl 5.41 2011-06-09 r3365
 
Humax provide smartctl version 6.0 as part of the 1.03.xx firmware. The CFW smartmontools package provides an earlier version.
 
Well spotted. Because I reformatted the HDD humax3 has no packages installed at all (am I correct?) it will be running the stock Humax version. Whereas humax2 has loads of packages installed.
I assume there's no way the package manager can avoid overwriting newer stock versions? Or do the CFW versions merely appear earlier in the path?
 
ABMorley said:
On running fix-disk I was surprised to see loads and loads of errors from e2fsck. In fact e2fsck died as it ran out of memory.

Thinking this might have had something to do with my messing around I reformatted the drive (via the standard Humax UI). But, even after that it still shows up with loads of errors. Logfile is attached - Disk check after reformat (via Humax UI).log. Actually I used e2fsck -n -f /dev/sda2 so as not to write any changes.

So: After a reformat, the disk is in a state that e2fsck is unhappy with.
Click to expand...
If you run e2fsck from the command line it will run out of memory unless some swap space has been allocated. fix-disk will create and use the necessary swap file.
I didn't run fix-disk on it - instead I ran: e2fsck -n -f /dev/sda2 so nothing would get changed.
Click to expand...
You could run fix-disk with the options '-B -P -2 -x -n' to just run e2fsck on partition 2 with the '-n' option and with a swap file.

It might be useful to look at the output of 'tune2fs -l /dev/sda2' in case the filesystem is unusual in any way.
 
xyz321 said:
You could run fix-disk with the options '-B -P -2 -x -n' to just run e2fsck on partition 2 with the '-n' option and with a swap file.
Click to expand...
I think fix-disk has a -y hard-coded into the call to e2fsck.
Code: 
humax3# fix-disk -B -P -2 -x -n
Running /bin/fix-disk
Custom firmware version 2.22
 
 
Checking disk sda
 
Partition /dev/sda1 is already unmounted
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted
Skipped pending sector error tests
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
 
 
Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=272c1660-9b79-4096-99e9-e81ec80fe794
 
Checking partition /dev/sda2...
e2fsck: Only one of the options -p/-a, -n or -y may be specified.
Removing extra swap space.
 
Finished


It might be useful to look at the output of 'tune2fs -l /dev/sda2' in case the filesystem is unusual in any way.
Click to expand...
Here goes:
Code: 
humax3# tune2fs -l /dev/sda2
tune2fs 1.41.14 (22-Dec-2010)
Filesystem volume name:  hmx_int_stor
Last mounted on:          <not available>
Filesystem UUID:          4d555967-7376-4ad6-a080-b78ed7a26fae
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
Filesystem flags:        signed_directory_hash
Default mount options:    (none)
Filesystem state:        clean
Errors behavior:          Continue
Filesystem OS type:      Linux
Inode count:              29860704
Block count:              119209984
Reserved block count:    5960516
Free blocks:              115907836
Free inodes:              29856164
First block:              0
Block size:              4096
Fragment size:            4096
Reserved GDT blocks:      995
Blocks per group:        32768
Fragments per group:      32768
Inodes per group:        8208
Inode blocks per group:  513
Filesystem created:      Sun Mar 16 13:20:49 2014
Last mount time:          Mon Mar 17 20:54:51 2014
Last write time:          Mon Mar 17 20:55:20 2014
Mount count:              8
Maximum mount count:      26
Last checked:            Sun Mar 16 13:20:49 2014
Check interval:          15552000 (6 months)
Next check after:        Fri Sep 12 14:20:49 2014
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Journal inode:            8
Default directory hash:  tea
Directory Hash Seed:      e82fe5e2-c128-42aa-8225-3c5ed5bd7d84
Journal backup:          inode blocks
humax3#
 
xyz321 said:
You could run fix-disk with the options '-B -P -2 -x -n' to just run e2fsck on partition 2 with the '-n' option and with a swap file.
Click to expand...
And for the enthusiast, here's the log from running a hacked fix-disk so e2fsck doesn't write to the drive. Log attached.

The closing lines are:
Code: 
Illegal block #537922567 (4294967295) in inode 15695.  IGNORED.
Illegal block #537922568 (4294967295) in inode 15695.  IGNORED.
Illegal block #537922569 (4294967295) in inode 15695.  IGNORED.
Illegal block #537922570 (4294967295) in inode 15695.  IGNORED.
Illegal block #537922571 (4294967295) in inode 15695.  IGNORED.
Illegal indirect block (537951741) in inode 15695.  IGNORED.
Error while iterating over blocks in inode 15695: Illegal indirect block found
e2fsck: aborted
Aborting...
humax3#

Thanks everyone - any ideas?
 

Attachments

  • fix-disk-log.log.zip
    60.6 KB · Views: 1
This is very strange, e2fsck may have failed because it was unable to fix the faults. If you are not too worried about the contents of the disk you could try running it without the '-n' option but you may have done this before.

Did you format it using the Humax UI or from the command line? If the former, you could try the following from maintenance mode:
Code: 
umount /dev/sda2
mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sda2
 
xyz321 said:
Did you format it using the Humax UI or from the command line?
Click to expand...
It was via the Humax UI.
Last night I deleted all the partitions then rebooted, so there couldn't be any funnies left over. Naturally the UI asked me to reformat so I did. Thus the box is now reformatted completely.

running my hacked fix-disk:
Code: 
...
Inode 15689, i_size is 8030115674518766, should be 49152.  Fix? no
 
Inode 15689, i_blocks is 4781294, should be 80.  Fix? no
 
Inode 15692, i_size is 8030390552425710, should be 49152.  Fix? no
 
Inode 15692, i_blocks is 4781294, should be 80.  Fix? no
 
Inode 15695 has illegal block(s).  Clear? no
 
Illegal block #537920524 (4294967295) in inode 15695.  IGNORED.
Illegal block #537920525 (4294967295) in inode 15695.  IGNORED.
Illegal block #537920526 (4294967295) in inode 15695.  IGNORED.
...
Illegal block #537922571 (4294967295) in inode 15695.  IGNORED.
Illegal indirect block (537951741) in inode 15695.  IGNORED.
Error while iterating over blocks in inode 15695: Illegal indirect block found
e2fsck: aborted
Aborting...
So no change there. A UI stock reformat generates the funny stuff.

BTW sda3 doesn't have any funnies:
Code: 
humax3# ./tm-fix-disk -B -P -3 -x -n
Running ./tm-fix-disk
Custom firmware version 2.22
 
 
Checking disk sda
 
Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3
Skipped pending sector error tests
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
 
 
Checking partition /dev/sda3...
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create? no
 
Pass 4: Checking reference counts
Pass 5: Checking group summary information
 
hmx_int_stor: ********** WARNING: Filesystem still has errors **********
 
hmx_int_stor: 11/655776 files (0.0% non-contiguous), 342131/2622611 blocks
Aborting...

But sda1 does:
Code: 
humax3# ./tm-fix-disk -B -P -1 -x -n
Running ./tm-fix-disk
Custom firmware version 2.22
 
 
Checking disk sda
 
Partition /dev/sda1 is already unmounted
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted
Skipped pending sector error tests
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
 
 
Checking partition /dev/sda1...
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Inode 239 is in use, but has dtime set.  Fix? no
 
Inode 241 is in use, but has dtime set.  Fix? no
 
Inode 241 has imagic flag set.  Clear? no
 
Inode 241 has a extra size (25449) which is invalid
Fix? no
 
Inode 242 has EXTENTS_FL flag set on filesystem without extents support.
Clear? no
 
Inode 242 is in use, but has dtime set.  Fix? no
 
Inode 242 has a extra size (29816) which is invalid
Fix? no
 
Inode 242 has compression flag set on filesystem without compression support.  Clear? no
 
Inode 242 has INDEX_FL flag set but is not a directory.
Clear HTree index? no
 
HTREE directory inode 242 has an invalid root node.
Clear HTree index? no
 
Inode 242 should not have EOFBLOCKS_FL set (size 7955925801654970224, lblk -1)
Clear? no
 
Inode 242, i_size is 7955925801654970224, should be 0.  Fix? no
 
Inode 242, i_blocks is 1667855986, should be 0.  Fix? no
 
Inode 243 is in use, but has dtime set.  Fix? no
 
Inode 243 has imagic flag set.  Clear? no
 
Inode 243 has a extra size (48386) which is invalid
Fix? no
 
Inodes that were part of a corrupted orphan linked list found.  Fix? no
 
Inode 245 was part of the orphaned inode list.  IGNORED.
Inode 245 is in use, but has dtime set.  Fix? no
 
Inode 246 has EXTENTS_FL flag set on filesystem without extents support.
Clear? no
 
Inode 246 was part of the orphaned inode list.  IGNORED.
Inode 246 is in use, but has dtime set.  Fix? no
 
Inode 246 has a extra size (29397) which is invalid
Fix? no
 
Inode 246 has a bad extended attribute block 13031.  Clear? no
 
Extended attribute block 13031 has h_blocks > 1.  Clear? no
 
Extended attribute block 13031 is corrupt (invalid value).  Clear? no
 
Extended attribute block 13031 is corrupt (invalid value).  Clear? no
 
Extended attribute block 13031 is corrupt (allocation collision).  Clear? no
 
Inode 246, i_size is 3594981961843179976, should be 0.  Fix? no
 
Inode 246, i_blocks is 301989955, should be 8.  Fix? no
 
Inode 247 is in use, but has dtime set.  Fix? no
 
Inode 247 has imagic flag set.  Clear? no
[...]
Illegal block #11 (1896940577) in inode 258.  IGNORED.
Illegal indirect block (2785411072) in inode 258.  IGNORED.
Illegal double indirect block (33686279) in inode 258.  IGNORED.
Illegal triple indirect block (336659489) in inode 258.  IGNORED.
Error while iterating over blocks in inode 258: Illegal triply indirect block found
e2fsck: aborted
Aborting...


xyz321 said:
If the former, you could try the following from maintenance mode:
Code: 
umount /dev/sda2
mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sda2
Click to expand...

Done! Naturally e2fsck has no issues with it. But does the humax stock firmware rely on these oddities? Does it specially put them in for some technical reason, and running without them will result in the box catching fire? Or did they just issue the update on a Friday afternoon after a long lunch and somehow mucked up?

I've also done the same to sda1, so now all three partitions check out OK by e2fsck. I'll see what fix-disk makes of them.

Has anyone else with 1.03.12 tried running fix-disk? If it were just one box I'd think there was something funny about it... but both?
 
Update. fix-disk (with no options) now finds no error or problems, as you might expect. But I imagine that a stock reformat will reintroduce the strangeness.
 
Well, with
mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sda[12]​
done on sda 1 and 2, and sda3 being clean anyway, I though I'd let it record stuff for a bit then run fix-disk....
Fix-disk completes with no error.
Now, let's see if the stock reformat reintroduces the behaviour....
From the Humax UI on the TV, reformatting produced the following modal dialogue:
Cannot format the hard disk. The capacity is too large.​
Now I cannot format it! Also I cannot run the HDD test from the Humax UI on the TV - selecting it has no effect!
So, now a hard power cycle - switch off at the back... wait ... power on.
No run the Humax UI disk check.... OK.
On a whim, re-run fix-disk.....
Now.... Loads of errors on running fix disk:
Code: 
...
File ... (inode #29848, mod time Tue Mar 18 09:02:29 2014)
  has 8121 multiply-claimed block(s), shared with 14 file(s):
        <filesystem metadata>
        ... (inode #31288, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #31000, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #30744, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #30696, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #30648, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #30600, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #30248, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #30184, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #30008, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #29912, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #29736, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #29656, mod time Tue Mar 18 09:02:29 2014)
        ... (inode #29496, mod time Tue Mar 18 09:02:29 2014)
Clone multiply-claimed blocks? yes
...

And I haven't even reformatted it. How weird is that? BTW sda3 and 2 were fine - only sda1 was mad.
 
Further update.
I reformatted the first partition:
mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sda1​
So once again fix-disk is happy. And the box is happy.

Left it in standby overnight, which includes one program record plus the usual wake-up for OTA upgrade.
In the morning, fix-disk still happy.
So.... I've just turned off the power (with the unit in standby, hard drive spun down of course) then - after allowing the capacitors to discharge - turned it on.

Normally on a hard power-on, the unit starts, does some housekeeping then turns back off into standby (orange circle). However, right now, it is in active standby - blue circle on the front, HDD, web and telnet server running, but no Humax UI. Web UI says " System is in standby".
Not much processing going on, but the humaxtv process is doing something:
Code: 
Mem: 94340K used, 30644K free, 0K shrd, 31760K buff, 35780K cached
CPU:  1% usr  0% sys  0% nic  97% idle  0% io  0% irq  0% sirq
Load average: 0.00 0.02 0.02 2/155 1760
  PID  PPID USER    STAT  VSZ %VSZ %CPU COMMAND
  203  157 root    S    322m 264%  2% /usr/bin/humaxtv
1760  1591 root    R N  1348  1%  0% top
1343    1 root    S N  12392  10%  0% /mod/sbin/mongoose /mod/etc/mongoose.conf
1380    1 root    S N  2660  2%  0% /mod/bin/epg -f /mnt/hd1/dvbepg/epg.dat sqlitedumpd /mnt/hd1/epg.db
  654    1 root    S    1504  1%  0% udhcpc -t 5 -T 10 -p /var/lib/humaxtv/udhcpc.eth0.pid -i eth0
1336    1 root    S N  1368  1%  0% /mod/sbin/crond
1519  135 root    S N  1264  1%  0% {tmenu} /bin/sh /bin/tmenu
  157    26 root    S    1252  1%  0% {S90settop} /bin/sh /etc/init.d/S90settop start
1591  1519 root    S N  1248  1%  0% /bin/sh -l
    1    0 root    S    1244  1%  0% init
  26    1 root    S    1240  1%  0% {rcS} /bin/sh /etc/init.d/rcS
  129    1 nobody  S      936  1%  0% /usr/bin/dnsmasq
  135    1 root    S N    824  1%  0% /sbin/utelnetd -l /bin/tmenu -p 23 -d -B
  24    1 root    SW      0  0%  0% [mtdblockd]
  707    9 root    SW<      0  0%  0% [kjournald]
 
Black Hole said:
See Things Every... (click) section 18, specifically "Delinquent Half-Awake".
Click to expand...
Ah good... so that's normal - thanks for pointing that out. And sure enough, power-cycling from the front panel (or remote, presumably) turn it on normally, then off normally. So all good then.
Wonder what fix-disk makes of it. You'll remember before the hard (mains) power cycle it was all happy.... here goes....
... and it's still happy. So it appears that my earlier observation that the filesystem gets mangled was wrong. Maybe there was a power glitch or something.
So, a hard power cycle appears to make no difference. If fix-disk is happy before the hard power cycle then it's happy afterwards.
Next step - and I need to go to work so I'm not doing it now - is to once again reformat the HDD using the Humax UI to confirm that that does reintroduce the errors/inconsistencies.

Thanks everyone for your suggestions so far. I'm not even sure that it's a problem. The box that is running with the filesystem with which fix-disk is unhappy continues to work just fine.
 
Well, here's the next instalment.
Story so far: All three partitions are formatted from the command line (not Humax's UI) and check out fine with fix-disk.
This evening I ran fix-disk again. Still good.
Ran the Humax UI disk check. No problems.
So I tried formatting it from the Humax UI. The UI said:
Cannot format the hard disk. The capacity is too large.​
Re-ran fix-disk. Still OK.
Tried formatting the disk again. Same message.
Re-ran fix-disk again....
Now sda1 has the fault and fix-disk is spewing messages like mad.

So it looks as though:
  • The boxes come formatted strangely, in a way that fix-disk (or rather e2fsck) doesn't like.
  • Using the Humax UI formatter leads to it getting formatted strangely.
  • Using the command line (mkfs.ext3 -m 0 -O sparse_super -T largefile /dev/sdan) leaves it formatted normally (at least by e2fsck's standards).
  • It seems to stay that way as long as we don't reformat it using the Humax UI.
Anyone else found this on machines formatted by 1.03.12/2.22?
 
You must log in or register to reply here.
Back
Top