Fix-disk unable to resolve errors

Ubtree

Member
I recently upgraded my HDR-FOX T2 by installing a 2TB HDD. (To do this, I updated to the latest custom firmware, physically installed the drive, let the firmare setup the drive, and copied across the media files.) All seemed to be well, but after a few days, the Humax started to freeze for no apparent reason. (This has happened before, on a number of occasions, with both my current box and a previous HDR-FOX T2.)

I ran fix-disk, and it seemed to work. But last night the Humax froze again. Now, when I run fix-disk, errors are reported but fix-disk aborts.

The following is the report generated by fix-disk.
Code:
Please select option: 1
Any additional options (or press return for none):
Are you sure you wish to run the hard disk checker? [Y/N] y
Running /bin/fix-disk
Custom firmware version 3.00
Checking disk sda
Partition /dev/sda1 is already unmounted
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted
Running short disk self test
No pending sectors found - skipping sector repair
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Checking partition /dev/sda3...
e2fsck 1.42.10 (18-May-2014)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
hmx_int_stor: 13/655776 files (7.7% non-contiguous), 143793/2622611 blocks
Checking partition /dev/sda1...
e2fsck 1.42.10 (18-May-2014)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
hmx_int_stor: 18/65808 files (22.2% non-contiguous), 15864/263062 blocks
Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=9077393d-0d05-4596-b6e1-d1ec39e90456
Checking partition /dev/sda2...
e2fsck 1.42.10 (18-May-2014)
Pass 1: Checking inodes, blocks, and sizes
^[[A^[[A^[[Ahmx_int_stor: |  |
Inode 1514350 has EXTENTS_FL flag set on filesystem without extents support.
Clear? yes
Inode 1514351 has EXTENTS_FL flag set on filesystem without extents support.
Clear? yes
Inode 1514352 is in use, but has dtime set.  Fix? yes
Inode 1514352 has imagic flag set.  Clear? yes
Inode 1514352 has a extra size (11553) which is invalid
Fix? yes
Inode 1514353 has EXTENTS_FL flag set on filesystem without extents support.
Clear? yes
Inode 1514354 has EXTENTS_FL flag set on filesystem without extents support.
Clear? yes
Inode 1514355 has EXTENTS_FL flag set on filesystem without extents support.
Clear? yes
Inode 1514356 is in use, but has dtime set.  Fix? yes
Inode 1514356 has a extra size (13683) which is invalid
Fix? yes
Inode 1514357 is in use, but has dtime set.  Fix? yes
Inode 1514357 has imagic flag set.  Clear? yes
Inode 1514357 has a extra size (24012) which is invalid
Fix? yes
Special (device/socket/fifo) inode 1514357 has non-zero size.  Fix? yes
Inode 1514358 is in use, but has dtime set.  Fix? yes
Inode 1514358 has imagic flag set.  Clear? yes
Inode 1514358 has a extra size (12065) which is invalid
Fix? yes
Inode 1514359 is in use, but has dtime set.  Fix? yes
Inode 1514359 has a extra size (39938) which is invalid
Fix? yes
Inode 1513866 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1513866 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1513866, i_size is 3850730813019815559, should be 0.  Fix? yes
Inode 1513866, i_blocks is 299707929, should be 0.  Fix? yes
Inode 1513792 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1513792, i_size is 16086523889345204925, should be 0.  Fix? yes
Inode 1513792, i_blocks is 3041991963, should be 0.  Fix? yes
Inode 1514255 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1514255 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1514255, i_size is 16163172223130943815, should be 0.  Fix? yes
Inode 1514255, i_blocks is 344985856, should be 0.  Fix? yes
Inode 1514291 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1514291 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1514291, i_size is 7541954179849060679, should be 0.  Fix? yes
Inode 1514291, i_blocks is 1648827785, should be 0.  Fix? yes
Inode 1514356 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1514356, i_size is 2004885391420381240, should be 0.  Fix? yes
Inode 1514356, i_blocks is 1442330586, should be 0.  Fix? yes
Inode 1514358 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1514358 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1514358, i_size is 9790596519384098118, should be 0.  Fix? yes
Inode 1514358, i_blocks is 3490472585, should be 0.  Fix? yes
Inode 1514185 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1514185 has a bad extended attribute block 68484434.  Clear? yes
Inode 1514185 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1514185, i_size is 18077126860963998049, should be 0.  Fix? yes
Inode 1514185, i_blocks is 789038089, should be 0.  Fix? yes
Inode 1513989 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1513989, i_size is 13877364081868252583, should be 0.  Fix? yes
Inode 1513989, i_blocks is 2421683569, should be 0.  Fix? yes
Inode 1514314 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1514314 has illegal block(s).  Clear? yes
Illegal block #0 (544773524) in inode 1514314.  CLEARED.
Illegal block #1 (2637303229) in inode 1514314.  CLEARED.
Illegal block #2 (3163202645) in inode 1514314.  CLEARED.
Illegal block #3 (3338846915) in inode 1514314.  CLEARED.
Illegal block #4 (2503997107) in inode 1514314.  CLEARED.
Illegal block #5 (4012516837) in inode 1514314.  CLEARED.
Illegal block #6 (2385649953) in inode 1514314.  CLEARED.
Inode 1514314 is too big.  Truncate? yes
Block #7 (355270983) causes symlink to be too big.  CLEARED.
Illegal block #8 (3861394174) in inode 1514314.  CLEARED.
Illegal block #9 (3286561375) in inode 1514314.  CLEARED.
Illegal block #10 (954228383) in inode 1514314.  CLEARED.
Too many illegal blocks in inode 1514314.
Clear inode? yes
Inode 1514330 has a bad extended attribute block 2097748.  Clear? yes
Inode 1514330 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1514330, i_size is 139900004378738759, should be 0.  Fix? yes
Inode 1514330, i_blocks is 3601793311, should be 0.  Fix? yes
Inode 1513782 has a bad extended attribute block 209321915.  Clear? yes
Inode 1513782 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1513782, i_size is 9952532597291980283, should be 0.  Fix? yes
Inode 1513782, i_blocks is 3048655634, should be 0.  Fix? yes
Inode 1514259, i_size is 4400953075209123081, should be 0.  Fix? yes
Inode 1514259, i_blocks is 552820716, should be 0.  Fix? yes
Inode 1514010 has a bad extended attribute block 408036677.  Clear? yes
Inode 1514010, i_size is 1415874865620261436, should be 0.  Fix? yes
Inode 1514010, i_blocks is 3149783798, should be 0.  Fix? yes
Inode 1514195 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1514195, i_size is 4488758617308987719, should be 0.  Fix? yes
Inode 1514195, i_blocks is 1880499959, should be 0.  Fix? yes
Inode 1514288 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1514288, i_size is 795999165733797959, should be 0.  Fix? yes
Inode 1514288, i_blocks is 2792187645, should be 0.  Fix? yes
Inode 1514312, i_blocks is 368608546, should be 0.  Fix? yes
Inode 1514359, i_size is 17511772608354402159, should be 0.  Fix? yes
Inode 1514359, i_blocks is 1833547023, should be 0.  Fix? yes
Inode 1513950 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1513950, i_size is 14403932446407126901, should be 0.  Fix? yes
Inode 1513950, i_blocks is 3801551301, should be 0.  Fix? yes
Inode 1514183, i_size is 11171278798493728839, should be 0.  Fix? yes
Inode 1514183, i_blocks is 1342177280, should be 0.  Fix? yes
Inode 1514329 has compression flag set on filesystem without compression support
.  Clear? yes
Inode 1514329 has a bad extended attribute block 3145728.  Clear? yes
Inode 1514329 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1514329, i_size is 167899823640479312, should be 0.  Fix? yes
Inode 1514329, i_blocks is 1890834095, should be 0.  Fix? yes
Inode 1514352 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 1514352, i_size is 821956157319124779, should be 0.  Fix? yes
Inode 1514352, i_blocks is 1693206401, should be 0.  Fix? yes
Inode 1514140 has illegal block(s).  Clear? yes
Illegal block #0 (1712092012) in inode 1514140.  CLEARED.
Illegal block #1 (1650601584) in inode 1514140.  CLEARED.
Illegal block #2 (1868770915) in inode 1514140.  CLEARED.
Illegal block #8 (1698841352) in inode 1514140.  CLEARED.
Illegal block #9 (1701405285) in inode 1514140.  CLEARED.
Illegal block #10 (1712092019) in inode 1514140.  CLEARED.
Illegal block #11 (1650601584) in inode 1514140.  CLEARED.
Illegal indirect block (1868770915) in inode 1514140.  CLEARED.
Inode 1514140 is too big.  Truncate? yes
Block #36702220 (415396854) causes directory to be too big.  CLEARED.
Error storing directory block information (inode=1514140, block=0, num=33487981)
: Memory allocation failed
e2fsck: aborted
hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
Removing extra swap space.
Finished
Can anyone help me with this?
 
Last edited:
I recently upgraded my HDR-FOX T2 by installing a 2TB HDD.
It might help if you specify the exact make and model of hard drive you have fitted. Beyond saying that the file system is in a bad way I can't throw any light on what is wrong; hopefully someone with more knowledge will be able to comment.
 
Was it new or second hand?
I purchased the drive a year or so ago, to install in my previous HDR-FOX T2, which I abandoned shortly afterwards. I kept the drive, and have now installed it in the replacement HDR-FOX T2.
Could you post the SMART data (WebIf>Diagnostics>Hard drive)?
I've now run the diagnostics, but I'm not sure how to report them. Should I simply copy and paste into a reply?
 
Any suggesions, from anyone? Should I replace the drive? If so, what drive would be suitable? (All the recommendations that I have found by looking through earlier threads have been discontinued!)
 
We need to be able to see the SMART data which you appear to have deleted; please post it again.
Is this what you need?
Code:
SMART Status  PASSED
Device Model  WDC WD20EURS-63S48Y0
Serial Number  WD-WCAZAJ209569
LU WWN Device Id  5 0014ee 2b21f7fbc
Firmware Version  51.0AB51
User Capacity  2,000,398,934,016 bytes [2.00 TB]
Sector Sizes  512 bytes logical, 4096 bytes physical
ATA Version is  8
ATA Standard is  Exact ATA specification draft version not indicated
Local Time is  Tue Oct 28 14:36:38 2014 GMT
SMART support is  Available - device has SMART capability.
SMART support is  Enabled
Attributes
ID Name Flags Raw Value Value Worst Thresh Type Updated When Failed
1 Raw_Read_Error_Rate POSR-K 0 200 200 051 Pre-fail Always -
3 Spin_Up_Time POS--K 6308 173 168 021 Pre-fail Always -
4 Start_Stop_Count -O--CK 111 100 100 000 Old_age Always -
5 Reallocated_Sector_Ct PO--CK 0 200 200 140 Pre-fail Always -
7 Seek_Error_Rate -OSR-K 0 100 253 000 Old_age Always -
9 Power_On_Hours -O--CK 223 100 100 000 Old_age Always -
10 Spin_Retry_Count -O--CK 0 100 100 000 Old_age Always -
11 Calibration_Retry_Count -O--CK 0 100 100 000 Old_age Always -
12 Power_Cycle_Count -O--CK 111 100 100 000 Old_age Always -
192 Power-Off_Retract_Count -O--CK 105 200 200 000 Old_age Always -
193 Load_Cycle_Count -O--CK 5 200 200 000 Old_age Always -
194 Temperature_Celsius -O---K 37 113 095 000 Old_age Always -
196 Reallocated_Event_Count -O--CK 0 200 200 000 Old_age Always -
197 Current_Pending_Sector -O--CK 0 200 200 000 Old_age Always -
198 Offline_Uncorrectable ----CK 0 100 253 000 Old_age Offline -
199 UDMA_CRC_Error_Count -O--CK 0 200 200 000 Old_age Always -
200 Multi_Zone_Error_Rate ---R-- 0 100 253 000 Old_age Offline -
Self-test logs
No. Description Status Remaining When First Error LBA
# 1 Short offline Completed without error 00% 220 -
# 2 Short offline Completed without error 00% 219 -
# 3 Short offline Completed without error 00% 219 -
# 4 Short offline Completed without error 00% 218 -
# 5 Short offline Completed without error 00% 201 -
# 6 Short offline Completed without error 00% 192 -
# 7 Short offline Completed without error 00% 185 -
 
Nothing of any concern there. In post #3 you said the drive was a WD20EARS but it actually appears to be a WD20EURS which is a drive designed for PVR usage. I certainly wouldn't be considering changing the drive on the evidence so far. If it was me, I would take the drive out, connect it to a PC and run the Western Digital diagnostics on it.
 
I'm not sure that this drive is reporting temperature correctly, but if it is, it seems to be indicating that the 'Worst' temperature recorded is 95 Deg C, I would say that is too high, do you know if the Humax's fan is working correctly?
Does the picture freezing occur soon after 'turn-on' or only after the Humax has warmed up? (possibly an hour or two)
Code:
194 Temperature_Celsius -O---K 37 113 095 000 Old_age Always -
 
Last edited:
Back
Top