hard drive error won't fix

rjm2k1 · Mar 30, 2016

Hi, my humax has started freezing when trying to play any recordings, the auto fix doesn't work and the diagnostics shows the results below, any suggestions appreciated - thanks in advance

Code:

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 942475336
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 942475336: succeeded

Running short disk self test
Error at LBA 942475336
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 942475336: succeeded

Running short disk self test
Error at LBA 942475336
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 942475336: succeeded

Running short disk self test
Error at LBA 942475336
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 942475336: succeeded

Running short disk self test
Error at LBA 942475336
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 942475336: succeeded

Running short disk self test
Error at LBA 942475336
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 942475336: succeeded

Running short disk self test
Error at LBA 942475336
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 942475336: succeeded

Running short disk self test
Error at LBA 942475336
Do you wish to attempt repair of the bad block? [Y/N]: n
Skipped repair of LBA 942475336
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Dev: /dev/sda LBA: 942475336
LBA: 942475336 is on partition /dev/sda2, start: 23101470, bad sector offset: 91
9373866
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 942475336 maps to file system block 114921733 on /dev/sda2

Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
^[[5~Block 114921733 is marked as in use

Searching for inode...
debugfs 1.42.10 (18-May-2014)
Inode: 112235

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
112235  /mnt/hd2/mod/tmp/redring.log
Dev: /dev/sda LBA: 942475336
LBA: 942475336 is on partition /dev/sda2, start: 23101470, bad sector offset: 91
9373866
dumpe2fs 1.42.10 (18-May-2014)
Using superblock 0
Block size: 4096
LBA 942475336 maps to file system block 114921733 on /dev/sda2

Checking to see if this block is in use...
debugfs 1.42.10 (18-May-2014)
Block 114921733 is marked as in use

Searching for inode...
debugfs 1.42.10 (18-May-2014)

af123 · Mar 30, 2016

Upgrade to CFW 3.10 and try again. If that's an AF disk there may be surrounding sectors that also need repairing.

rjm2k1 · Mar 31, 2016

thanks, am I better off with the stock kernel or custom kernel version?

MartinLiddle · Mar 31, 2016

rjm2k1 said:
thanks, am I better off with the stock kernel or custom kernel version?

Custom kernel unless that gives problems.

rjm2k1 · Mar 31, 2016

did the trick thanks, couldn't work out how to re-mount the partition to delete the file that was mentioned but I guess that's not critical. Is this an indication that the drive will fail soon?

MartinLiddle · Mar 31, 2016

rjm2k1 said:
Is this an indication that the drive will fail soon?

Not necessarily. Post the hard drive diagnostic (Diagnostics>disk diagnostics) and you will get a more informed opinion.

Trev · Mar 31, 2016

But in a code box this time please.

rjm2k1 · Apr 1, 2016

Here's the diagnostics thanks

Code:

SMART data read from device /dev/sda
Disk Information
SMART Status    PASSED   
Model Family     Seagate Video 3.5 HDD
Device Model     ST1000VM002-1CT162
Serial Number     S1G2FVDB
LU WWN Device Id     5 000c50 061f0c38a
Firmware Version     SC23
User Capacity     1,000,204,886,016 bytes [1.00 TB]
Sector Sizes     512 bytes logical, 4096 bytes physical
Rotation Rate     5900 rpm
Form Factor     3.5 inches
Device is     In smartctl database [for details use: -P show]
ATA Version is     ATA8-ACS T13/1699-D revision 4
SATA Version is     SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is     Fri Apr 1 16:58:04 2016 BST
SMART support is     Available - device has SMART capability.
SMART support is     Enabled
Attributes
ID     Name     Flags     Raw Value     Value     Worst     Threshold     Life Left     Notes
1     Raw_Read_Error_Rate     POSR--     135634096     117     085     006         -
3     Spin_Up_Time     PO----     0     097     097     000         -
4     Start_Stop_Count     -O--CK     2825     098     098     020     98%     -
5     Reallocated_Sector_Ct     PO--CK     8     100     100     036     100%     -
7     Seek_Error_Rate     POSR--     353892387     085     060     030         -
9     Power_On_Hours     -O--CK     10836     088     088     000     88%     -
10     Spin_Retry_Count     PO--C-     0     100     100     097     100%     -
12     Power_Cycle_Count     -O--CK     2825     098     098     020     98%     -
184     End-to-End_Error     -O--CK     0     100     100     099         -
187     Reported_Uncorrect     -O--CK     2053     001     001     000         -
188     Command_Timeout     -O--CK     0     100     100     000         -
189     High_Fly_Writes     -O-RCK     111     001     001     000         -
190     Airflow_Temperature_Cel     -O---K     39     061 (39°C)     044 (56°C)     045 (55°C)         In_the_past
191     G-Sense_Error_Rate     -O--CK     0     100     100     000         -
192     Power-Off_Retract_Count     -O--CK     2823     099     099     000     99%     -
193     Load_Cycle_Count     -O--CK     2825     099     099     000     99%     -
194     Temperature_Celsius     -O---K     39     039     056     000         -
197     Current_Pending_Sector     -O--C-     0     100     100     000         -
198     Offline_Uncorrectable     ----C-     0     100     100     000         -
199     UDMA_CRC_Error_Count     -OSRCK     0     200     200     000         -
Self-test logs
No.     Description     Status     Remaining     When     First Error LBA
# 1     Short offline     Completed without error     00%     10825     -
# 2     Short offline     Completed: read failure     90%     10825     942475336
# 3     Short offline     Completed: read failure     90%     10820     942475336
# 4     Short offline     Completed: read failure     90%     10820     942475336
# 5     Short offline     Completed: read failure     90%     10820     942475336
# 6     Short offline     Completed: read failure     90%     10820     942475336
# 7     Short offline     Completed: read failure     90%     10820     942475336
# 8     Short offline     Completed: read failure     90%     10820     942475336
# 9     Short offline     Completed: read failure     90%     10820     942475336
#10     Short offline     Completed: read failure     90%     10820     942475336
#11     Short offline     Completed without error     00%     0     -
Rendered in: 0.612 seconds

MartinLiddle · Apr 3, 2016

rjm2k1 said:
Here's the diagnostics thanks

Looks fine to me; only a single 4k sector reallocated.

af123 · Apr 4, 2016

Could you post the fix-disk.log file? I'd be interested to check what 3.10 did different with the sector.
It should be viewable from the webif diagnostics/logs screen.
Thanks.

rjm2k1 · Apr 4, 2016

af123 said:
Could you post the fix-disk.log file? I'd be interested to check what 3.10 did different with the sector.
It should be viewable from the webif diagnostics/logs screen.
Thanks.

sure, here is what I think is relevant...

Code:

Pass 2: Checking directory structure
53    Pass 1: Checking inodes, blocks, and sizes
52    Checking partition /dev/sda2...
51   
50    /dev/sda1: |========================================================| 100.0%   
                                                                               
/dev/sda1: 15/288 files (6.7% non-contiguous), 12043/265064 blocks
49    Pass 5: Checking group summary information
48    Pass 4: Checking reference counts
47    Pass 3: Checking directory connectivity
46    /dev/sda1: |====                                                    |  7.8%   
/dev/sda1: |===================================                     / 62.2%   
                                                                               
Pass 2: Checking directory structure
45    Pass 1: Checking inodes, blocks, and sizes
44    Checking partition /dev/sda1...
43   
42    /dev/sda3: |=====================================================   \ 95.1%   
/dev/sda3: |=====================================================   | 95.2%   
/dev/sda3: |========================================================| 100.0%   
                                                                               
/dev/sda3: 14/2592 files (0.0% non-contiguous), 73894/2622611 blocks
41    Pass 5: Checking group summary information
40    Pass 4: Checking reference counts
39    Pass 3: Checking directory connectivity
38    /dev/sda3: |                                                        |  0.9%   
/dev/sda3: |=                                                       /  1.7%   
/dev/sda3: |=========                                               - 15.6%   
/dev/sda3: |===============                                         \ 27.7%   
/dev/sda3: |===================                                     | 34.6%   
/dev/sda3: |=======================                                 / 41.5%   
/dev/sda3: |================================                        - 57.0%   
                                                                               
Pass 2: Checking directory structure
37    Pass 1: Checking inodes, blocks, and sizes
36    Checking partition /dev/sda3...
35   
34    112235    /mnt/hd2/mod/tmp/redring.log
33    Inode    Pathname
32    The following file contains a corrupt block and can not be fully recovered.
31   
30    Inode: 112235
29    Block 114921733 is marked as in use
28    LBA 942475336 maps to file system block 114921733 on /dev/sda2
27    LBA: 942475336 is on partition /dev/sda2, start: 23101470, bad sector offset: 919373866
26    Using superblock 0 on sda3
25    Using superblock 0 on sda2
24    Using superblock 0 on sda1
23    No pending sectors found - skipping sector repair
22   
21    Running short disk self test
20        Block 942475343  -                      - Repaired
19        Block 942475342  -                      - Repaired
18        Block 942475341  -                      - Repaired
17        Block 942475340  -                      - Repaired
16        Block 942475339  -                      - Repaired
15        Block 942475338  -                      - Repaired
14        Block 942475337  -                      - Repaired
13        Block 942475336  - OK
12    Also checking blocks 942475336 - 942475343 (8 blocks)
11    This is an advanced-format disk.
10    Error at LBA 942475336
9    Running short disk self test
8   
7    Checking disk sda (4096 byte sectors)
6   
5   
4    ----------------------------------------------------------------------
3    Fix-disk run starting...
2    ----------------------------------------------------------------------
1

af123 · Apr 4, 2016

Excellent thanks. That confirms that the new AF physical sector code did indeed kick in and do the job.

rjm2k1 · Apr 5, 2016

af123 said:
Excellent thanks. That confirms that the new AF physical sector code did indeed kick in and do the job.

Worked for me thanks!

One thing I've noticed now is that the System Monitor isn't recording any information, no CPU temp, no Fan speed etc. Is this a known side effect of the custom kernel?

prpr · Apr 5, 2016

No, it's not. It's probably your sysmon database that's corrupt. Try this and see if it starts working:

Code:

humax# cd /mod/monitor && mv monitor.db oldmonitor.db && sqlite3 oldmonitor.db ".clone monitor.db"

If it does, zip up the oldmonitor.db and post it somewhere where we can find it to have a look.

AV_Mike · Apr 5, 2016

I have experienced a couple of Sysmon failures - but each time I just deleted the monitor.db
Could the above fix be added as a diagnostic option?

Regards, Mike.

rjm2k1 · Apr 5, 2016

prpr said:
If it does, zip up the oldmonitor.db and post it somewhere where we can find it to have a look.

seems to have done the trick, here's the old db thanks
https://www.dropbox.com/s/hxlzcfkmv3haz93/oldmonitor.zip?dl=0

prpr · Apr 5, 2016

rjm2k1 said:
seems to have done the trick, here's the old db thanks

It's the same error as someone else had.

Code:

sqlite> pragma integrity_check;
*** in database main ***
Page 231: btreeInitPage() returns error code 11
Page 230: btreeInitPage() returns error code 11
sqlite> .dump
 ...
INSERT INTO "net" VALUES(1431102241,'raw',0,0,3,30);
INSERT INTO "net" VALUES(1431102300,'5min',0,0,73,85);
/**** ERROR: (11) database disk image is malformed *****/
/**** ERROR: (11) database disk image is malformed *****/
CREATE TABLE state(
       module text not null primary key,
       state text
     );
INSERT INTO "state" VALUES('net','lastpoll 1435688341 inerrs 0 outerrs 0 uptime 26.59 inoctets 5980 outoctets 2464');
COMMIT;

It's a bit of a mystery how this database is getting corrupted.

rjm2k1 · Apr 6, 2016

prpr said:
It's the same error as someone else had.
It's a bit of a mystery how this database is getting corrupted.

I've had to do some forced power downs due to the box freezing so could be down to those!

prpr · Apr 6, 2016

Possibly, but I'd expect Mr. Sqlite's code to be a bit more resilient. Perhaps it isn't, or perhaps it's something else. Difficult to tell...

MymsMan · Nov 28, 2017

prpr said:
No, it's not. It's probably your sysmon database that's corrupt. Try this and see if it starts working:

Code:

humax# cd /mod/monitor && mv monitor.db oldmonitor.db && sqlite3 oldmonitor.db ".clone monitor.db"

If it does, zip up the oldmonitor.db and post it somewhere where we can find it to have a look.

I noticed Sysmon had stopped collecting data back in September and I ran prpr's fix successfully

Running the pragma check shows different errors to previous.

Code:

sqlite> pragma integrity_check;
*** in database main ***
On tree page 2 cell 0: invalid page number 259
On tree page 252 cell 43: Rowid 1503959341 out of order
On tree page 64 cell 44: Rowid 1503957061 out of order
On tree page 63 cell 44: Rowid 1503954841 out of order
sqlite>

.dump show huge number of INSERT INTO followed by COMMIT with no Errors

Code:

INSERT INTO "vmstat" VALUES(1503993188,'raw',3328,42624,22,42160,51,0,27);
INSERT INTO "vmstat" VALUES(1504085167,'raw',3032,43864,35,36252,35,17,13);
INSERT INTO "vmstat" VALUES(1507161600,'weekly',3780,46708,14,31924,45,42,0);
INSERT INTO "vmstat" VALUES(1507420800,'daily',3780,46708,14,31924,45,42,0);
INSERT INTO "vmstat" VALUES(1507460400,'hourly',3780,46708,14,31924,45,42,0);
INSERT INTO "vmstat" VALUES(1507461300,'15min',3780,46708,14,31924,45,42,0);
INSERT INTO "vmstat" VALUES(1507461600,'5min',3780,46708,14,31924,45,42,0);
INSERT INTO "vmstat" VALUES(1507461609,'raw',3780,46708,14,31924,45,42,0);
INSERT INTO "vmstat" VALUES(1508601549,'raw',8808,30388,7,46984,7,84,1);
COMMIT;

Data base available if closer look needed

hard drive error won't fix

New Member

Administrator

New Member

Super Moderator

New Member

Super Moderator

The Dumb One

New Member

Super Moderator

Administrator

New Member

Administrator

New Member

Well-Known Member

New Member

New Member

Well-Known Member

New Member

Well-Known Member

Ad detector