OP
Black Hole
May contain traces of nut
I take it this is out of warranty then?
-
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.
Steps for Repairing a Disk of Unknown Faults
- Thread starter Black Hole
- Start date
Yes. Purchased 27/12/2010 (I think you collate these - serial 63 7104496 00032) and replaced under warranty (same fault as now) 06/07/2011 with serial 63 7104496 00594 which in turn was replaced 11/01/2012 due to extremely slow reaction to all commands, with my current machine. Not a good history.
OP
Black Hole
May contain traces of nut
That's sad. My original machine is coming up to three years old and not had a problem.
UPDATE
Before going on holiday I removed the hard drive, connected it to my Windows XP desktop and reformatted the three EXT3 partitions. Whilst I had to format them with 2KB sectors, when I returned the drive to the Humax and did a format there (I now no longer get the error "Cannot format the hard disk. The capacity is too large") this then showed them as 512 byte sectors. On my return from holiday all the programmes I set up to be recorded, and have watched so far, have been without problem.
I note, however, that not much has changed in the 'ID# ATTRIBUTE_NAME' lines that Ezra mentioned as being noteworthy! There certainly still seem to be problems with this drive - the "Check and repair hard disk (fix-disk)" results are below; but the tests 2 & 3 do not run, they just immediately return to the menu.
[Okay, the results are in an attached file since I'm getting the "You cannot post links or email addresses until you have 10 posts. This is to prevent SPAM" otherwise. Is it really effective having this protection if it can be then be simply circumvented? Is it actually trying to prevent LONG messages? There are no email addresses in it]
The bottom line is that as long as it carries on as it is I'm happy to get a bit more life out of it; when it starts acting up again I'll know what to do!
Graham
Before going on holiday I removed the hard drive, connected it to my Windows XP desktop and reformatted the three EXT3 partitions. Whilst I had to format them with 2KB sectors, when I returned the drive to the Humax and did a format there (I now no longer get the error "Cannot format the hard disk. The capacity is too large") this then showed them as 512 byte sectors. On my return from holiday all the programmes I set up to be recorded, and have watched so far, have been without problem.
I note, however, that not much has changed in the 'ID# ATTRIBUTE_NAME' lines that Ezra mentioned as being noteworthy! There certainly still seem to be problems with this drive - the "Check and repair hard disk (fix-disk)" results are below; but the tests 2 & 3 do not run, they just immediately return to the menu.
[Okay, the results are in an attached file since I'm getting the "You cannot post links or email addresses until you have 10 posts. This is to prevent SPAM" otherwise. Is it really effective having this protection if it can be then be simply circumvented? Is it actually trying to prevent LONG messages? There are no email addresses in it]
The bottom line is that as long as it carries on as it is I'm happy to get a bit more life out of it; when it starts acting up again I'll know what to do!
Graham
OP
Black Hole
May contain traces of nut
The file contains strings that look a bit like URLs. Spam posts frequently contain links to dodgy web sites.
Ezra Pound
Well-Known Member
There is a new version of fix-disk (0.3) now available in the repository. This may help but the disk does have a high reallocated sector count and the "unknown errors" may cause difficulties. This new version will attempt to fix the problem with the partition table (LBA 0) but I can not guarantee success. In any case it will not improve the reallocated sector count.
Ezra Pound
Well-Known Member
will this new version of fix-disk eventually be embedded into the Custom Firmware?
OP
Black Hole
May contain traces of nut
Can somebody using WiFi please report where in the Humax menus the unit's network IP address is reported? Is it in the WiFi section of the menus or is it under Menu >> Settings >> System >> Internet Setting >> Configure LAN?
dandnsmith
Forum Supporter
Menu|Settings|System|Internet|Configure LAN(WiFi)
OP
Black Hole
May contain traces of nut
Thanks, but that leaves me none the wiser. The menu location should be either
Menu >> Settings >> System >> Internet Setting >> Configure LAN
or
Menu >> Settings >> System >> Internet Setting >> Configure Wi-Fi
Not having a WiFi link myself, the Configure Wi-Fi option is greyed out so I can't see what lies within. It would be useful for future reference to have a list of the sub-menu options that appear under that section.
Menu >> Settings >> System >> Internet Setting >> Configure LAN
or
Menu >> Settings >> System >> Internet Setting >> Configure Wi-Fi
Not having a WiFi link myself, the Configure Wi-Fi option is greyed out so I can't see what lies within. It would be useful for future reference to have a list of the sub-menu options that appear under that section.
OP
Black Hole
May contain traces of nut
Ah! So with a WiFi dongle plugged in, the menu options become
Menu >> Settings >> System >> Internet Setting >> Configure LAN(WiFi)
and
Menu >> Settings >> System >> Internet Setting >> Configure Wi-Fi
?
It would still be useful to have the sub-menus on record.
Menu >> Settings >> System >> Internet Setting >> Configure LAN(WiFi)
and
Menu >> Settings >> System >> Internet Setting >> Configure Wi-Fi
?
It would still be useful to have the sub-menus on record.
ChrisDaniels
Well-Known Member
Does this help? skip to 2:20
OP
Black Hole
May contain traces of nut
So basically the Configure WiFi sub-menu only deals with the authentication to the access point, and the IP stuff is on the Configure LAN(Wi-Fi) sub-menu. Thanks.
Hello, been a while for me but I have finally gotten round to updating my CF today to 1.03.12.
For a long while now I have been having freeze up problems when attempting to change certain preferences, usually video preferences. Also, the webif has warned me about hard disk problems. So today i have followed the instructions on here about stopping potentially conflicting network servers (I stopped Plex and the humax sharing), and to attempt HDD fix have run the fix disk in maintenance mode.
Problem now is maintenance mode seems to be hanging after about 6 hours....The front of hummy says MAINTENANCE with a little bar at 1 block. Here is what telnet is showing. The text in bold is what I thought I had originally copy/pasted to this thread, but the additional text seems to be in telnet also,but looks like it might be duplication of the earlier short disk test, so I may have inadvertently pasted into telnet? Anyway do you think this is still running? Can I/Should I turn the machine off and try again? Help please, as no TV to watch tonight and wifey is asking if I;ve been messing with it agan as she can't watch strictly... :-(
Menu version 1.13
Enter system PIN: ****
/---------------------------------------------\
| 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
Error at LBA 1618226387
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226387: succeeded
Running short disk self test
Error at LBA 1618226388
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226388: succeeded
Running short disk self test
Error at LBA 1618226393
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226393: succeeded
Running short disk self test
Error at LBA 1618226398
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226398: succeeded
Running short disk self test
Error at LBA 1616125130
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1616125130: succeeded
Running short disk self test
Error at LBA 1618226394
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226394: succeeded
Running short disk self test
Pending sector error(s) found
LBA has not yet been found
A long test is required - this could take 3 hour(s) 35 minutes
Do you wish to continue? [Y/N]: y
Running long disk self test
Error at LBA 1612709126
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612709126: succeeded
Running select disk self test
Error at LBA 1612715390
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612715390: succeeded
Running select disk self test
Error at LBA 1612715391
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612715391: succeeded
Running select disk self test
Error at LBA 1612717734
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612717734: succeeded
Running select disk self test
Error at LBA 1612718521
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612718521: succeeded
Running select disk self test
Error at LBA 1612718522
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612718522: succeeded
Running select disk self test
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Dev: /dev/sda LBA: 1618226387
LBA: 1618226387 is on partition /dev/sda2, start: 2104515, bad sector offset: 1616121872
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1618226387 maps to file system block 202015234 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 202015234 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 50372880
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372880 /mnt/hd2/mod/webif/html/settings/settings.js
Dev: /dev/sda LBA: 1618226388
LBA: 1618226388 is on partition /dev/sda2, start: 2104515, bad sector offset: 1616121873
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1618226388 maps to file system block 202015234 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 202015234 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 50372880
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372880 /mnt/hd2/mod/webif/html/settings/settings.js
Dev: /dev/sda LBA: 1618226393
LBA: 1618226393 is on partition /dev/sda2, start: 2104515, bad sector offset: 1616121878
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1618226393 maps to file system block 202015234 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 202015234 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 50372880
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372880 /mnt/hd2/mod/webif/html/settings/settings.js
Dev: /dev/sda LBA: 1618226398
LBA: 1618226398 is on partition /dev/sda2, start: 2104515, bad sector offset: 1616121883
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1618226398 maps to file system block 202015235 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 202015235 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 50372881
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372881 /mnt/hd2/mod/webif/html/settings/settings.jim
Dev: /dev/sda LBA: 1616125130
LBA: 1616125130 is on partition /dev/sda2, start: 2104515, bad sector offset: 1614020615
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1616125130 maps to file system block 201752576 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 201752576 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Block Inode number 201752576 <block not found>
Dev: /dev/sda LBA: 1618226394
LBA: 1618226394 is on partition /dev/sda2, start: 2104515, bad sector offset: 1616121879
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1618226394 maps to file system block 202015234 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 202015234 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 50372880
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372880 /mnt/hd2/mod/webif/html/settings/settings.js
Dev: /dev/sda LBA: 1612709126
LBA: 1612709126 is on partition /dev/sda2, start: 2104515, bad sector offset: 1610604611
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1612709126 maps to file system block 201325576 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 201325576 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Menu version 1.13
Enter system PIN: ****
/---------------------------------------------\
| 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
Error at LBA 1618226387
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226387: succeeded
Running short disk self test
Error at LBA 1618226388
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226388: succeeded
Running short disk self test
Error at LBA 1618226393
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226393: succeeded
Running short disk self test
Error at LBA 16182
For a long while now I have been having freeze up problems when attempting to change certain preferences, usually video preferences. Also, the webif has warned me about hard disk problems. So today i have followed the instructions on here about stopping potentially conflicting network servers (I stopped Plex and the humax sharing), and to attempt HDD fix have run the fix disk in maintenance mode.
Problem now is maintenance mode seems to be hanging after about 6 hours....The front of hummy says MAINTENANCE with a little bar at 1 block. Here is what telnet is showing. The text in bold is what I thought I had originally copy/pasted to this thread, but the additional text seems to be in telnet also,but looks like it might be duplication of the earlier short disk test, so I may have inadvertently pasted into telnet? Anyway do you think this is still running? Can I/Should I turn the machine off and try again? Help please, as no TV to watch tonight and wifey is asking if I;ve been messing with it agan as she can't watch strictly... :-(
Menu version 1.13
Enter system PIN: ****
/---------------------------------------------\
| 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
Error at LBA 1618226387
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226387: succeeded
Running short disk self test
Error at LBA 1618226388
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226388: succeeded
Running short disk self test
Error at LBA 1618226393
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226393: succeeded
Running short disk self test
Error at LBA 1618226398
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226398: succeeded
Running short disk self test
Error at LBA 1616125130
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1616125130: succeeded
Running short disk self test
Error at LBA 1618226394
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226394: succeeded
Running short disk self test
Pending sector error(s) found
LBA has not yet been found
A long test is required - this could take 3 hour(s) 35 minutes
Do you wish to continue? [Y/N]: y
Running long disk self test
Error at LBA 1612709126
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612709126: succeeded
Running select disk self test
Error at LBA 1612715390
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612715390: succeeded
Running select disk self test
Error at LBA 1612715391
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612715391: succeeded
Running select disk self test
Error at LBA 1612717734
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612717734: succeeded
Running select disk self test
Error at LBA 1612718521
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612718521: succeeded
Running select disk self test
Error at LBA 1612718522
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1612718522: succeeded
Running select disk self test
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Dev: /dev/sda LBA: 1618226387
LBA: 1618226387 is on partition /dev/sda2, start: 2104515, bad sector offset: 1616121872
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1618226387 maps to file system block 202015234 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 202015234 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 50372880
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372880 /mnt/hd2/mod/webif/html/settings/settings.js
Dev: /dev/sda LBA: 1618226388
LBA: 1618226388 is on partition /dev/sda2, start: 2104515, bad sector offset: 1616121873
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1618226388 maps to file system block 202015234 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 202015234 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 50372880
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372880 /mnt/hd2/mod/webif/html/settings/settings.js
Dev: /dev/sda LBA: 1618226393
LBA: 1618226393 is on partition /dev/sda2, start: 2104515, bad sector offset: 1616121878
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1618226393 maps to file system block 202015234 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 202015234 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 50372880
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372880 /mnt/hd2/mod/webif/html/settings/settings.js
Dev: /dev/sda LBA: 1618226398
LBA: 1618226398 is on partition /dev/sda2, start: 2104515, bad sector offset: 1616121883
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1618226398 maps to file system block 202015235 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 202015235 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 50372881
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372881 /mnt/hd2/mod/webif/html/settings/settings.jim
Dev: /dev/sda LBA: 1616125130
LBA: 1616125130 is on partition /dev/sda2, start: 2104515, bad sector offset: 1614020615
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1616125130 maps to file system block 201752576 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 201752576 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Block Inode number 201752576 <block not found>
Dev: /dev/sda LBA: 1618226394
LBA: 1618226394 is on partition /dev/sda2, start: 2104515, bad sector offset: 1616121879
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1618226394 maps to file system block 202015234 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 202015234 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 50372880
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372880 /mnt/hd2/mod/webif/html/settings/settings.js
Dev: /dev/sda LBA: 1612709126
LBA: 1612709126 is on partition /dev/sda2, start: 2104515, bad sector offset: 1610604611
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 1612709126 maps to file system block 201325576 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 201325576 is marked as in use
Searching for inode...
debugfs 1.42.10 (18-May-2014)
Menu version 1.13
Enter system PIN: ****
/---------------------------------------------\
| 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
Error at LBA 1618226387
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226387: succeeded
Running short disk self test
Error at LBA 1618226388
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226388: succeeded
Running short disk self test
Error at LBA 1618226393
Do you wish to attempt repair of the bad block? [Y/N]: y
/dev/sda:
re-writing sector 1618226393: succeeded
Running short disk self test
Error at LBA 16182
update: I have switched the humax off and on again. It has rebooted into normal mode. When I go into Webif I no longer get the disk warnings. I suspect the disk may still be prblemattic but will monitor that.
The problem remains of freezing when changin gsimple settings such as video mode (auto, letterbox etc) and other settings. When I take out the wifi dongle and reboot the probem resolves. I note the probkem reported in the scan above of "The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372880 /mnt/hd2/mod/webif/html/settings/settings.js"
How can I fix this issue please?
The problem remains of freezing when changin gsimple settings such as video mode (auto, letterbox etc) and other settings. When I take out the wifi dongle and reboot the probem resolves. I note the probkem reported in the scan above of "The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.10 (18-May-2014)
Inode Pathname
50372880 /mnt/hd2/mod/webif/html/settings/settings.js"
How can I fix this issue please?