Fix disk

Dave H

New Member
Hi I updated my custom firmware as I was getting a few 0 hours recordings so I thought I would check the hard drive, I started the Fix disk program at 11.30 am and it was still going at midnight.
I had to leave it on over night but my lap top shut down after three hours so in the morning the telnet said lost connection.
I had to exit maintenance mode so I want to know in 15 hours has fix disk done anything and is this normal length of time for a scan ?
 

Ezra Pound

Well-Known Member
Fix-disk takes about 30 mins. to complete when run on a 500GB HDD with no errors, it can take many hours to run when it is finding / fixing problems, so 15 hours is not unusual, somtimes fix-disk may need to be run more than once. I would expect a second run fo take less time than the first as there should fewer problems to fix
 
Last edited:
OP
D

Dave H

New Member
I run this again yesterday and got the same problem software caused the connection error what are my obtains now as the box is not recording no more ?
 

MontysEvilTwin

Well-Known Member
I run this again yesterday and got the same problem software caused the connection error what are my obtains now as the box is not recording no more ?
Fix disk needs to run until it is complete. This may be quite quick, but can also take ages if there are many errors: I had a run once that reported lots of inode errors and took hours.
Your laptop will need to stay on until it finishes. Leave the charger connected and switched on so that it is running on mains power, rather than just the battery. You need to go into power management (control panel) and ensure that it is set to never sleep on mains power; it is OK for the screen to switch off. You can change the power settings back to how they were after you have finished.
 

MoisiePants

New Member
Hello Dave:

A word of caution for you: if you can, make an image of your drive before you go much further with this, incase you need to roll back.

Whilst I'm not placing blame or suggesting this is a widespread issue (it clearly isn't!), I had an experience recently with Fix Disk killing the file system on my Hummy drive. After >8,000,000 lines of output, the Hummy wouldn't boot - and all my recordings had disappeared. It probably took about 30 mins to do this.

Thankfully, it looks like I'm gradually getting them back, thanks to a Linux recovery tool - but it's taking a long while (especially as it seems I didn't have auto-decrypt running).

Good luck - I hope your issue isn't as severe as mine was!



In case anyone's interested, here's a snippet of output from my Fix Disk run:

Code:
      /---------------------------------------------\
      |  M A I N T E N A N C E   M O D E   M E N U  |
      \---------------------------------------------/

  [ Humax HDR-Fox T2 (humax) 1.03.12/3.03 ]

    1 - Check and repair hard disk (fix-disk).
    2 - Run short hard-disk self test.
    3 - Run long hard-disk self test.
    4 - Check self-test progress.
  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: 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.03


Checking disk sda

Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3

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
Inode 129 has EXTENTS_FL flag set on filesystem without extents support.
Clear? yes

Inode 130 is in use, but has dtime set.  Fix? yes

Inode 130 has a extra size (27223) which is invalid
Fix? yes

Inode 131 is in use, but has dtime set.  Fix? yes

Inode 131 has a extra size (29822) which is invalid
Fix? yes

Inode 132 has EXTENTS_FL flag set on filesystem without extents support.
Clear? yes

Inode 133 has EXTENTS_FL flag set on filesystem without extents support.
Clear? yes

Inode 134 is in use, but has dtime set.  Fix? yes

Inode 134 has a extra size (54342) which is invalid
Fix? yes

Inode 135 is in use, but has dtime set.  Fix? yes

Inode 135 has imagic flag set.  Clear? yes

Inode 135 has a extra size (50612) which is invalid
Fix? yes

...

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

Illegal block #0 (3845660654) in inode 80434.  CLEARED.
Illegal block #1 (3881317847) in inode 80434.  CLEARED.
Illegal block #2 (1749232179) in inode 80434.  CLEARED.
Illegal block #3 (3537164738) in inode 80434.  CLEARED.
Illegal block #4 (3935929256) in inode 80434.  CLEARED.
Illegal block #5 (1912130494) in inode 80434.  CLEARED.
Illegal block #6 (3398137719) in inode 80434.  CLEARED.
Illegal block #7 (2167187634) in inode 80434.  CLEARED.
Illegal block #8 (1756832363) in inode 80434.  CLEARED.
Illegal block #9 (1094451497) in inode 80434.  CLEARED.
Illegal block #10 (4225343909) in inode 80434.  CLEARED.
Too many illegal blocks in inode 80434.
Clear inode? yes

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

Illegal block #0 (812307060) in inode 80320.  CLEARED.
Illegal block #1 (178633820) in inode 80320.  CLEARED.
Illegal block #2 (1731316013) in inode 80320.  CLEARED.
Illegal block #3 (619039793) in inode 80320.  CLEARED.
Illegal block #4 (2479714657) in inode 80320.  CLEARED.
Illegal block #5 (203279793) in inode 80320.  CLEARED.
Illegal block #6 (1619807061) in inode 80320.  CLEARED.
Illegal block #7 (585538990) in inode 80320.  CLEARED.
Illegal block #8 (1388792980) in inode 80320.  CLEARED.
Illegal block #9 (728730180) in inode 80320.  CLEARED.
Illegal block #10 (432121635) in inode 80320.  CLEARED.
Too many illegal blocks in inode 80320.
Clear inode? yes

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

Inode 80369, i_size is 5281557296955778518, should be 0.  Fix? yes

Inode 80369, i_blocks is 1207153014, should be 0.  Fix? yes

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

Illegal block #0 (1983075695) in inode 80725.  CLEARED.
Illegal block #1 (1079244259) in inode 80725.  CLEARED.
Illegal block #2 (2703194256) in inode 80725.  CLEARED.
Illegal block #3 (1297833156) in inode 80725.  CLEARED.
Illegal block #4 (4100777363) in inode 80725.  CLEARED.
Illegal block #5 (1688396782) in inode 80725.  CLEARED.
Illegal block #6 (1849430665) in inode 80725.  CLEARED.
Illegal block #7 (4148115185) in inode 80725.  CLEARED.
Illegal block #8 (764890671) in inode 80725.  CLEARED.
Illegal block #9 (4223672049) in inode 80725.  CLEARED.
Illegal block #10 (975977929) in inode 80725.  CLEARED.
Too many illegal blocks in inode 80725.
Clear inode? yes

...

Inode 141610, i_size is 2522015793273646592, should be 0.  Fix? yes

Inode 141610, i_blocks is 302041306, should be 0.  Fix? yes

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

Illegal block #3 (1850839636) in inode 141367.  CLEARED.
Illegal block #8 (587207168) in inode 141367.  CLEARED.
Illegal block #10 (1744860160) in inode 141367.  CLEARED.
Illegal block #11 (1828746496) in inode 141367.  CLEARED.
Illegal indirect block (1929404928) in inode 141367.  CLEARED.
Illegal double indirect block (2147483904) in inode 141367.  CLEARED.
Illegal block #17843217 (4294967295) in inode 141367.  CLEARED.
Error storing directory block information (inode=141367, block=0, num=9232509): Memory allocation failed
e2fsck: aborted

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

hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
tee: /tmp/fix-disk.log: I/O error
Removing extra swap space.
Are you having problems with a delete loop? [Y/N]: Are you having problems with a delete loop? [Y/N]: y
cat: write error: No space left on device

Finished

Press return to continue:


Thanks,

Pants.
 
Last edited by a moderator:
Top