Fixdisk caused HDR-FOX T2 to want to reformat the drive

aekostas

Member
Restarting the conversation from https://hummy.tv/forum/threads/sche...mes-already-recorded.10474/page-3#post-159771 to decontaminate that thread.

The problem
I ran fixdisk, which made a large number of repairs. I think it finished with out of memory error, and I do not know if that log is available somewhere. Anyway, on restarting, the Hummy is asking to reformat the disk; I did not do that. I cannot access the WebIF (in a loop of "The system is initialising.").

On rerunning, it got stuck on the same sector for hours, reporting the following again and again:

Code:
Running select disk self test
Error at LBA 251006816

/dev/sda:
re-writing sector 251006816: succeeded
This is an advanced-format disk.
Also checking blocks 251006816 - 251006823 (8 blocks)
    Block 251006816  - OK
    Block 251006817  - OK
    Block 251006818  - OK
    Block 251006819  - OK
    Block 251006820  - OK
    Block 251006821  - OK
    Block 251006822  - OK
    Block 251006823  - OK

Running select disk self test

Diagnostics
smartctl
I ran # smartctl -a /dev/sda and got the following:
Code:
# 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, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Green
Device Model:     WDC WD10EZRX-00L4HB0
Serial Number:    WD-WCC4J0771360
LU WWN Device Id: 5 0014ee 2b3de474f
Firmware Version: 01.01A01
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sat Jan 22 17:40:52 2022 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

General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        Auto Offline Data Collection: Enabled.
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:                (12660) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        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:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 145) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x3035) SCT Status supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       39
  3 Spin_Up_Time            0x0027   136   121   021    Pre-fail  Always       -       4175
  4 Start_Stop_Count        0x0032   094   094   000    Old_age   Always       -       6458
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   092   092   000    Old_age   Always       -       6448
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   094   094   000    Old_age   Always       -       6455
192 Power-Off_Retract_Count 0x0032   192   192   000    Old_age   Always       -       6392
193 Load_Cycle_Count        0x0032   176   176   000    Old_age   Always       -       72515
194 Temperature_Celsius     0x0022   103   082   000    Old_age   Always       -       40
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       2
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   192   000    Old_age   Always       -       759
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 7 (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 7 occurred at disk power-on lifetime: 6440 hours (268 days + 8 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 67 0f f6 ee  Error: UNC at LBA = 0x0ef60f67 = 251006823

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  20 00 01 67 0f f6 ee 0a      00:02:04.171  READ SECTOR(S)
  30 00 01 66 0f f6 ee 0a      00:02:04.110  WRITE SECTOR(S)
  ec 00 01 66 0f f6 a0 0a      00:02:04.095  IDENTIFY DEVICE
  20 00 01 66 0f f6 ee 0a      00:02:04.046  READ SECTOR(S)
  30 00 01 65 0f f6 ee 0a      00:02:03.891  WRITE SECTOR(S)

Error 6 occurred at disk power-on lifetime: 6440 hours (268 days + 8 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 66 0f f6 ee  Error: UNC at LBA = 0x0ef60f66 = 251006822

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  20 00 01 66 0f f6 ee 0a      00:02:04.046  READ SECTOR(S)
  30 00 01 65 0f f6 ee 0a      00:02:03.891  WRITE SECTOR(S)
  ec 00 01 65 0f f6 a0 0a      00:02:03.873  IDENTIFY DEVICE
  20 00 01 65 0f f6 ee 0a      00:02:03.816  READ SECTOR(S)
  30 00 01 64 0f f6 ee 0a      00:02:03.755  WRITE SECTOR(S)

Error 5 occurred at disk power-on lifetime: 6440 hours (268 days + 8 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 65 0f f6 ee  Error: UNC at LBA = 0x0ef60f65 = 251006821

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  20 00 01 65 0f f6 ee 0a      00:02:03.816  READ SECTOR(S)
  30 00 01 64 0f f6 ee 0a      00:02:03.755  WRITE SECTOR(S)
  ec 00 01 64 0f f6 a0 0a      00:02:03.740  IDENTIFY DEVICE
  20 00 01 64 0f f6 ee 0a      00:02:03.682  READ SECTOR(S)
  30 00 01 63 0f f6 ee 0a      00:02:03.622  WRITE SECTOR(S)

Error 4 occurred at disk power-on lifetime: 6440 hours (268 days + 8 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 64 0f f6 ee  Error: UNC at LBA = 0x0ef60f64 = 251006820

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  20 00 01 64 0f f6 ee 0a      00:02:03.682  READ SECTOR(S)
  30 00 01 63 0f f6 ee 0a      00:02:03.622  WRITE SECTOR(S)
  ec 00 01 63 0f f6 a0 0a      00:02:03.607  IDENTIFY DEVICE
  20 00 01 63 0f f6 ee 0a      00:02:03.558  READ SECTOR(S)
  30 00 01 62 0f f6 ee 0a      00:02:03.514  WRITE SECTOR(S)

Error 3 occurred at disk power-on lifetime: 6440 hours (268 days + 8 hours)
  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 63 0f f6 ee  Error: UNC at LBA = 0x0ef60f63 = 251006819

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  20 00 01 63 0f f6 ee 0a      00:02:03.558  READ SECTOR(S)
  30 00 01 62 0f f6 ee 0a      00:02:03.514  WRITE SECTOR(S)
  ec 00 01 62 0f f6 a0 0a      00:02:03.496  IDENTIFY DEVICE
  20 00 01 62 0f f6 ee 0a      00:02:03.438  READ SECTOR(S)
  30 00 01 61 0f f6 ee 0a      00:02:03.377  WRITE SECTOR(S)

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Aborted by host               10%      6447         -
# 2  Short offline       Completed: read failure       90%      6440         251006816
# 3  Short offline       Completed without error       00%      6438         -
# 4  Extended offline    Aborted by host               90%      3518         -
# 5  Extended offline    Completed without error       00%      3516         -
# 6  Short offline       Completed without error       00%      3508         -
# 7  Short offline       Completed without error       00%      3496         -
# 8  Short offline       Completed: read failure       90%      3496         1142627824
# 9  Short offline       Completed: read failure       90%      3496         1142627824
#10  Selective offline   Completed: read failure       90%      3495         963535768
#11  Extended offline    Completed: read failure       90%      3495         963535760
#12  Short offline       Completed: read failure       90%      3495         963535760
#13  Conveyance offline  Completed without error       00%        58         -
5 of 6 failed self-tests are outdated by newer successful extended offline self-test # 5

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.
I am not sure if these flag a critical issue, but note a fail is again in sector 251006816.
fdisk
I also looked into a thread deemed similar (thanks @prpr) and ran fdisk -lu /dev/sda, getting the following:
Code:
# fdisk -lu /dev/sda

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               8     2104510     1052251+ 83 Linux
Partition 1 does not end on cylinder boundary
/dev/sda2         2104512  1932539166   965217327+ 83 Linux
/dev/sda3      1932539168  1953520062    10490447+ 83 Linux
Again I don't know what these may mean.
diag igorw
I ran diag igorw and got the following:
Code:
d# diag igorw
Running: igorw
END CHS 1953520064
Searching for partition 3...
sh: out of memory
Unable to find partition 3
As my drive is not 2TB, I did not know if I should be following the rest of the advice on that thread and thought to post and see if people have any thoughts.

Many thanks in advance for any inputs!
 
I think it finished with out of memory error, and I do not know if that log is available somewhere.
It probably didn't, but the log is to be found in /mnt/hd3 (but the filesystem needs to be mounted and at least readable, which it may not be).
Anyway, on restarting, the Hummy is asking to reformat the disk;
I would run fixdisk again, but use the option to skip the SMART checks and hopefully it'll try and fix the filesystem(s), which is probably what's prompting the format message.
I am not sure if these flag a critical issue, but note a fail is again in sector 251006816.
I don't know why that group of sectors won't repair. There's nothing obviously wrong with the disk.
Again I don't know what these may mean.
It means your partition table is intact and has the correct values for a 1TB disk.
I ran diag igorw and got the following:
Don't use that. We proved in the aforementioned thread that it is hopelessly broken.
As my drive is not 2TB, I did not know if I should be following the rest of the advice on that thread
No, don't.
 
It probably didn't, but the log is to be found in /mnt/hd3 (but the filesystem needs to be mounted and at least readable, which it may not be).
Empty directory. :)
I would run fixdisk again, but use the option to skip the SMART checks and hopefully it'll try and fix the filesystem(s), which is probably what's prompting the format message.
OK, I ran fixdisk with -P -y, let's see how it goes.
I don't know why that group of sectors won't repair. There's nothing obviously wrong with the disk.
Happy days (modulo the subject of this and the other thread. :) :))

Thank you for your prompt, informative posts!
 
Last edited:
3.5 hrs in it looks like it hung. I lost contact; is there a way to reconnect with the terminal? I restarted telnet on a new window and I just see the usual options; I thought there used to be a "connect" or something?

Code:
 fixdisk - Check and repair hard disk.
   short - Run short hard-disk self test.
    long - Run long hard-disk self test.
   check - Check self-test progress.
    gptf - Re-format disk using GPT scheme.
     epg - Clear persistent EPG data.
    dlna - Reset DLNA server database.
       x - Leave maintenance mode (Humax will restart).
    diag - Run a diagnostic.
     cli - System command line (advanced users).

Please select option:
 
I guess it's going to sleep after 3 hrs. inactivity, but I'd have thought that was done by the Humax software which isn't running at that time.
Have you got the relevant power save option turned off anyway?
The fixdisk stuff should run in a protected session that you can reconnect to if your PC loses connection.
 
I think you are asking if I had set it to sleep after some time; I had. It had shut down earlier, before I put it in maintenance mode and started fixdisk and perhaps the maintenance mode prevents this from kicking in; the box appears on, the roundel being blue.

Wondering if fixdisk crashed though, or why is it offering it again?
 
Good morning. I now realise that the front reports "fixdisk done". I exited maintenance mode and rebooted; the Hummy still asks to be reformatted.

Is there another diagnostic one could run?

Edit: I ran another fixdisk -P -y; this time the terminal showed progress and completed (failed, as per Error storing directory block information (inode=1240688, block=0, num=40903952): Memory allocation failed e2fsck: aborted?) quickly, thus:

Code:
Please select option: fixdisk
Any additional options (-h for list or press return for none): -P -y
Are you sure you wish to run the hard disk checker (-P -y)? [Y/N] y
Running /bin/fix-disk

Checking disk sda (4096 byte sectors)

Unmounted /dev/sda1
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted

Skipped pending sector error tests

Checking partition tables...

MBR Status: MBR only
GPT Status: not present

Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3


Sun Jan 23 08:23:17 GMT 2022: Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 240k/0k (157k/84k), time: 11.78/ 4.29/ 4.77
Pass 1: I/O read: 165MB, write: 0MB, rate: 14.00MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 340k/0k (260k/81k), time:  0.01/ 0.00/ 0.01
Pass 2: I/O read: 1MB, write: 0MB, rate: 120.95MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 340k/0k (260k/81k), time: 12.40/ 4.56/ 4.83
Pass 3A: Memory used: 340k/0k (260k/81k), time:  0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 340k/0k (259k/82k), time:  0.00/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 340k/0k (53k/288k), time:  1.00/ 0.99/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 340k/0k (53k/288k), time:  2.58/ 1.97/ 0.05
Pass 5: I/O read: 1MB, write: 0MB, rate: 0.39MB/s

          16 inodes used (0.00%, out of 655776)
           0 non-contiguous files (0.0%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 3/3/0
      438716 blocks used (16.73%, out of 2622611)
           0 bad blocks
           1 large file

           5 regular files
           2 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
           7 files
Memory used: 340k/0k (53k/288k), time: 15.99/ 7.52/ 4.88
I/O read: 166MB, write: 1MB, rate: 10.38MB/s
Sun Jan 23 08:23:34 GMT 2022

Sun Jan 23 08:23:34 GMT 2022: Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 296k/0k (218k/79k), time:  0.96/ 0.39/ 0.45
Pass 1: I/O read: 17MB, write: 0MB, rate: 17.62MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 316k/0k (306k/11k), time:  0.17/ 0.12/ 0.03
Pass 2: I/O read: 7MB, write: 0MB, rate: 41.97MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 316k/0k (306k/11k), time:  1.21/ 0.54/ 0.49
Pass 3A: Memory used: 328k/0k (306k/23k), time:  0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 328k/0k (306k/23k), time:  0.00/ 0.00/ 0.00
Pass 3: I/O read: 1MB, write: 0MB, rate: 268.38MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 328k/0k (128k/201k), time:  0.15/ 0.15/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 328k/0k (128k/201k), time:  0.37/ 0.29/ 0.00
Pass 5: I/O read: 1MB, write: 0MB, rate: 2.70MB/s

        2096 inodes used (3.19%, out of 65808)
           1 non-contiguous file (0.0%)
           2 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 2031/2024/2023
       17713 blocks used (6.73%, out of 263062)
           0 bad blocks
           1 large file

           7 regular files
          10 directories
         503 character device files
         547 block device files
         548 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
         472 sockets
------------
        2087 files
Memory used: 328k/0k (128k/201k), time:  1.76/ 0.98/ 0.50
I/O read: 23MB, write: 1MB, rate: 13.05MB/s
Sun Jan 23 08:23:36 GMT 2022

Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=34779bdb-9f79-4e49-acae-cc7a1a068527

Sun Jan 23 08:23:58 GMT 2022: Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
/usr/lib/ext2/bin/e2fsck: Group descriptors look bad... trying backup blocks...
Resize inode not valid.  Recreate? yes

Pass 1: Checking inodes, blocks, and sizes
Inode 1240782, i_size is 10784383283302179918, should be 0.  Fix? yes

Inode 1240782, i_blocks is 1192943893, should be 0.  Fix? yes

Inode 1240797 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240797, i_size is 11989688997933657634, should be 0.  Fix? yes

Inode 1240797, i_blocks is 1307857097, should be 0.  Fix? yes

Inode 1240731 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240731 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240731, i_size is 14535852145289902283, should be 0.  Fix? yes

Inode 1240731, i_blocks is 3975877460, should be 0.  Fix? yes

Inode 1240849 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240849, i_size is 15835549338089325632, should be 0.  Fix? yes

Inode 1240849, i_blocks is 2862895449, should be 0.  Fix? yes

Inode 1240742 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240742 has illegal block(s).  Clear? yes

Illegal block #1 (946471102) in inode 1240742.  CLEARED.
Illegal block #3 (990213995) in inode 1240742.  CLEARED.
Illegal block #4 (3864859694) in inode 1240742.  CLEARED.
Illegal block #5 (4007915129) in inode 1240742.  CLEARED.
Illegal block #6 (3703688033) in inode 1240742.  CLEARED.
Illegal block #7 (2524191304) in inode 1240742.  CLEARED.
Illegal block #9 (2710581301) in inode 1240742.  CLEARED.
Illegal block #10 (2457840569) in inode 1240742.  CLEARED.
Illegal block #11 (1720969377) in inode 1240742.  CLEARED.
Illegal indirect block (1941674402) in inode 1240742.  CLEARED.
Illegal double indirect block (2626561686) in inode 1240742.  CLEARED.
Too many illegal blocks in inode 1240742.
Clear inode? yes

Inode 1240701 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240701 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240701, i_size is 17907884382650898844, should be 0.  Fix? yes

Inode 1240701, i_blocks is 219260380, should be 0.  Fix? yes

Inode 1240710 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240710, i_size is 7665767477169342068, should be 0.  Fix? yes

Inode 1240710, i_blocks is 698262536, should be 0.  Fix? yes

Inode 1240713 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240713, i_size is 15302517501645997040, should be 0.  Fix? yes

Inode 1240713, i_blocks is 2998457816, should be 0.  Fix? yes

Inode 1240826 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240826, i_size is 14116622147784832977, should be 0.  Fix? yes

Inode 1240826, i_blocks is 1170921825, should be 0.  Fix? yes

Inode 1240784 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240784, i_size is 16845161953404298544, should be 0.  Fix? yes

Inode 1240784, i_blocks is 474007282, should be 0.  Fix? yes

Inode 1240855, i_size is 11234729284380401728, should be 0.  Fix? yes

Inode 1240855, i_blocks is 4205186516, should be 0.  Fix? yes

Inode 1240724, i_size is 8254547955366463513, should be 0.  Fix? yes

Inode 1240724, i_blocks is 1611393104, should be 0.  Fix? yes

Inode 1240749 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240749, i_size is 10085660804928395228, should be 0.  Fix? yes

Inode 1240749, i_blocks is 3786272084, should be 0.  Fix? yes

Inode 1240847 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240847 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240847, i_size is 591415644934012789, should be 0.  Fix? yes

Inode 1240847, i_blocks is 912434408, should be 0.  Fix? yes

Inode 1240853 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240853 has a bad extended attribute block 103686918.  Clear? yes

Inode 1240853 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240853, i_size is 8052561686510085983, should be 0.  Fix? yes

Inode 1240853, i_blocks is 2578237370, should be 0.  Fix? yes

Inode 1240754 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240754, i_size is 1851657576226588895, should be 0.  Fix? yes

Inode 1240754, i_blocks is 1979904057, should be 0.  Fix? yes

Inode 1240808, i_size is 14933002158246260789, should be 0.  Fix? yes

Inode 1240808, i_blocks is 389399560, should be 0.  Fix? yes

Inode 1240730 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240730, i_size is 2479977728568537163, should be 0.  Fix? yes

Inode 1240730, i_blocks is 861013742, should be 0.  Fix? yes

Inode 1240856 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240856, i_size is 4981738194088999271, should be 0.  Fix? yes

Inode 1240856, i_blocks is 2207567872, should be 0.  Fix? yes

Inode 1240680 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240680 has a bad extended attribute block 86744574.  Clear? yes

Inode 1240680 has illegal block(s).  Clear? yes

Illegal block #0 (676816900) in inode 1240680.  CLEARED.
Illegal block #1 (1010394143) in inode 1240680.  CLEARED.
Illegal block #2 (426972454) in inode 1240680.  CLEARED.
Illegal block #3 (2599402973) in inode 1240680.  CLEARED.
Illegal block #4 (682909890) in inode 1240680.  CLEARED.
Illegal block #5 (2196399694) in inode 1240680.  CLEARED.
Illegal block #6 (3338237436) in inode 1240680.  CLEARED.
Illegal block #7 (840732022) in inode 1240680.  CLEARED.
Illegal block #8 (4263160403) in inode 1240680.  CLEARED.
Illegal block #9 (1627641270) in inode 1240680.  CLEARED.
Illegal block #10 (2714579508) in inode 1240680.  CLEARED.
Too many illegal blocks in inode 1240680.
Clear inode? yes

Inode 1240708, i_size is 5491330956899617296, should be 0.  Fix? yes

Inode 1240708, i_blocks is 1725253650, should be 0.  Fix? yes

Inode 1240750 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240750 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240750, i_size is 10782148426678573940, should be 0.  Fix? yes

Inode 1240750, i_blocks is 3940822683, should be 0.  Fix? yes

Inode 1240824, i_size is 13048131550660145986, should be 0.  Fix? yes

Inode 1240824, i_blocks is 3713144682, should be 0.  Fix? yes

Inode 1240683 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240683, i_size is 1735955752657246382, should be 0.  Fix? yes

Inode 1240683, i_blocks is 1690623176, should be 0.  Fix? yes

Inode 1240694 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240694, i_size is 7072373680279243579, should be 0.  Fix? yes

Inode 1240694, i_blocks is 2854060157, should be 0.  Fix? yes

Inode 1240861 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240861, i_size is 5123655010010064265, should be 0.  Fix? yes

Inode 1240861, i_blocks is 69965982, should be 0.  Fix? yes

Inode 1240830 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240830 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240830, i_size is 16660275626515860001, should be 0.  Fix? yes

Inode 1240830, i_blocks is 2104737450, should be 0.  Fix? yes

Inode 1240733 has compression flag set on filesystem without compression support.  Clear? yes

Inode 1240733 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes

Inode 1240733, i_size is 2827606372918981960, should be 0.  Fix? yes

Inode 1240733, i_blocks is 52930325, should be 0.  Fix? yes

Inode 1240688 has illegal block(s).  Clear? yes

Illegal block #2 (4026749441) in inode 1240688.  CLEARED.
Illegal block #4 (4027142657) in inode 1240688.  CLEARED.
Illegal block #5 (2383021157) in inode 1240688.  CLEARED.
Illegal block #6 (1852243972) in inode 1240688.  CLEARED.
Illegal block #7 (4209242121) in inode 1240688.  CLEARED.
Illegal block #9 (1728270849) in inode 1240688.  CLEARED.
Illegal block #10 (2550594278) in inode 1240688.  CLEARED.
Illegal block #11 (4027209992) in inode 1240688.  CLEARED.
Illegal indirect block (1701734160) in inode 1240688.  CLEARED.
Illegal double indirect block (1241712079) in inode 1240688.  CLEARED.
Illegal block #62915596 (3719620111) in inode 1240688.  CLEARED.
Error storing directory block information (inode=1240688, block=0, num=40903952): Memory allocation failed
e2fsck: aborted

hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****

hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
Sun Jan 23 08:27:03 GMT 2022
Removing extra swap space.

Finished
fix-disk: session terminated with exit status 0
 
Last edited:
I thought there used to be a "connect" or something?
I'm pretty sure "fixdisk" reconnects to the active session (if there is one).

the Hummy still asks to be reformatted.
Bearing in mind this is a "best guess" (more intended to stimulate thought rather than action), maybe the Humax start-up code is failing to find a resource it expects on a prepared drive, and its knee-jerk is to rebuild the resource by formatting. Maybe the fixdisk process has been unable to restore the resource to Humax's expectations.

If you can remove the HDD and connect it to a PC, you will be able to assess the actual state of the drive and contents. You will need to use a Linux boot for that, which is quite straight-forward providing you can boot your PC from DVD or USB.
 
If you can remove the HDD and connect it to a PC, you will be able to assess the actual state of the drive and contents. You will need to use a Linux boot for that, which is quite straight-forward providing you can boot your PC from DVD or USB.
Thanks for the suggestion. Can I confirm that the Windows Subsystem for Linux (which I am running on my computer) is insufficient and I will need to do the Linux boot?
 
Can I confirm that the Windows Subsystem for Linux (which I am running on my computer) is insufficient
I have no idea what that is. The reason for booting Linux is to enable OS recognition of the Ext3 file system. There are Ext3 readers for Windows, but I regard them as more complicated than simply booting Linux. If you think you can access Ext3 without, then by all means carry on.

For the benefit of other readers: modern Linux distributions will boot "live" from DVD or bootable USB (without disturbing the Windows boot, or whatever your installed OS might be). Linux recognises Ext3 "out of the box", and there are many varieties of Linux which are not dissimilar from using Windows (and are a handy way to bypass Windows when it's getting in the way). However, if your PC is under the care of an IT department, it might well have been locked down to stop it booting from anything other than the HDD.
 
Thanks for the suggestion. Can I confirm that the Windows Subsystem for Linux (which I am running on my computer) is insufficient and I will need to do the Linux boot?
I would give WSL a try. One thought that I had; your drive is a Western Digital drive but most drives in the Humax are Seagate drives; I wonder if something in fix-disk isn't working as expected on a WD drive? I also have seen you report out of memory errors several times; is the swap space working and if it is have you considered increasing it?
 
I would give WSL a try. One thought that I had; your drive is a Western Digital drive but most drives in the Humax are Seagate drives; I wonder if something in fix-disk isn't working as expected on a WD drive? I also have seen you report out of memory errors several times; is the swap space working and if it is have you considered increasing it?
Thanks Martin. Is there a pointer about the swap space? I thought it was fixdisk that created it.
 
I exited maintenance mode and rebooted; the Hummy still asks to be reformatted.
Because partition 2 seems very corrupted.
maybe the Humax start-up code is failing to find a resource it expects on a prepared drive, and its knee-jerk is to rebuild the resource by formatting.
Of course. Humax's answer to everything is to format the disk.
Maybe the fixdisk process has been unable to restore the resource to Humax's expectations.
Indeed, as shown by the fixdisk output.
Can I confirm that the Windows Subsystem for Linux (which I am running on my computer) is insufficient
Don't know. I played with it once and found it rather horrid compared to real Linux, but all my Windows PCs are virtual machines on real Linux, so I have no need for WSL.
This page may be of interest, where it seems to imply you can do what's required.
And more general stuff here.
Make sure you mount the drive, not the partition, as you want the partitions unmounted to be able to check/repair.
 
Last edited:
I've looked up WSL and it appears (to me) to be the Windows equivalent/opposite of Wine. Wine (in Linux) translates operating system calls so that an executable compiled for Windows can communicate with Linux, and presumably WSL provides the opposite translation so that a Linux executable can communicate with Windows. I don't see how that will magically make Windows "see" Ext3 file systems (but see update below).

So far as I understand it, the options are:
  • Boot to an OS with built-in Ext3 support, eg
    Something like System Rescue CD ought to do the job.

  • Run an Ext3 OS in a virtual machine;

  • Add an Ext3 driver/extension to Windows;

  • Run a version of Windows which has native Ext3 support (does Win11 do this?).
Update: according to the link in the previous post (posted while I was compiling this one), Windows Subsystem for Linux 2 (as of September 2020) offers the ability to mount Linux file systems from the command line (credit prpr for this insight). Therefore, add another option to the list:
However, this seems to be limited to file access to a specified partition, so would not be suitable for HDD diagnostics:
Having read up on this again, I don't think it will work, as it will only mount the disk (unpartitioned) or mount the partitions you specify.



Thanks Martin. Is there a pointer about the swap space? I thought it was fixdisk that created it.
I think we need @prpr to pontificate on this, but while the HDD is (fully) off-line there can't be any swap space. Recently I discovered the fixdisk logs are stored on partition 3, along with the .swap0 file, so presumably hd3 gets mounted at some point.

Increasing the swap space is (I guess) as simple as increasing the size of .swap0: see https://hummy.tv/forum/threads/swapper-virtual-memory.8844/post-159601
 
Last edited:
I think we need @prpr to pontificate on this,
Why me? I didn't write it. It's all down to xyz321.
presumably hd3 gets mounted at some point.
Yes. You just need to read the logs, or the code, or both.
If you want a custom swap file size for this, you need to create it yourself, and run e2fsck /dev/sda2 manually having done so.
 
Back
Top