HDD advice please

Stummery

Member
Yesterday my Humax started to behave erratically to remote presses and also pauses/judder in video playback etc.
Checking the webif I had a notification: Disk pending sector count is: 1 Disk offline sector count is: 1
Disk Diagnostics gave SMART errors in lines 197 and 198
I carried out a HDD test through the Humax on screen system menu which failed with error 8
I entered maintainence mode via Telnet and ran Fix-disk, after many hours (log file 60Mb) it finished. Here is the start

Code:
Checking disk sda (512 byte sectors)

Running short disk self test
Error at LBA 364129531
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
LBA: 364129531 is on partition /dev/sda2, start: 2104512, bad sector offset: 362025019
LBA 364129531 maps to file system block 45253127 on /dev/sda2
Block 45253127 is marked as in use
Inode: 11337326

The following file contains a corrupt block and can not be fully recovered.
Inode    Pathname
11337326    /mnt/hd2/mod/monitor/monitor.db-journal

Checking partition /dev/sda3...
Pass 1: Checking inodes, blocks, and sizes

followed by lots of lines like these

Code:
Inode 579903 has compression flag set on filesystem without compression support.  Clear? yes

Inode 579903, i_size is 15772203858589713698, should be 0.  Fix? yes

Inode 579903, i_blocks is 2362158259, should be 0.  Fix? yes

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

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

Inode 580142, i_size is 360827043592843715, should be 0.  Fix? yes

Inode 580142, i_blocks is 805558959, should be 0.  Fix? yes

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

Illegal block #0 (1775909266) in inode 580040.  CLEARED.
Illegal block #1 (3145246614) in inode 580040.  CLEARED.
Illegal block #2 (2118264958) in inode 580040.  CLEARED.
Illegal block #3 (3283424794) in inode 580040.  CLEARED.
Illegal block #4 (813408917) in inode 580040.  CLEARED.
Illegal block #5 (3932727216) in inode 580040.  CLEARED.
Illegal block #6 (3507380514) in inode 580040.  CLEARED.
Illegal block #7 (2056004512) in inode 580040.  CLEARED.
Illegal block #8 (2536978451) in inode 580040.  CLEARED.
Illegal block #9 (2966683453) in inode 580040.  CLEARED.
Illegal block #10 (4257122358) in inode 580040.  CLEARED.
Too many illegal blocks in inode 580040.
Clear inode? yes

Inode 579895, i_size is 7198412346662645270, should be 0.  Fix? yes

Inode 579895, i_blocks is 4199145734, should be 0.  Fix? yes

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

Inode 580082, i_size is 18086537168557890090, should be 0.  Fix? yes

Inode 580082, i_blocks is 3093567065, should be 0.  Fix? yes

Inode 579998, i_size is 15197689925992458958, should be 0.  Fix? yes

After it had completed Humax now works OK again. HDD passes as OK, using on screen system menu.

Webif Disk diagnostics give SMART data as
Code:
Total space: 447.6 GiB
Used: 301.22 GiB (67%)
Free: 126.29 GiB (29%)
Dustbin: 20.09 GiB (4%) Humax HDR Fox T2 (humax) - Diagnostics
Idle: 35m
SMART data read from device /dev/sda
Disk Information
SMART Status    PASSED 
Model Family     Seagate Pipeline HD 5900.2
Device Model     ST3500312CS
Serial Number     5VVFJNJ4
LU WWN Device Id     5 000c50 05cebd68b
Firmware Version     SC13
User Capacity     500,107,862,016 bytes [500 GB]
Sector Size     512 bytes logical/physical
Rotation Rate     5900 rpm
Device is     In smartctl database [for details use: -P show]
ATA Version is     ATA8-ACS T13/1699-D revision 4
SATA Version is     SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is     Tue Jan 10 11:03:26 2017 GMT
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--     127019464     117     085     006         -
3     Spin_Up_Time     PO----     0     097     097     000         -
4     Start_Stop_Count     -O--CK     2424     098     098     020     98%     -
5     Reallocated_Sector_Ct     PO--CK     0     100     100     036     100%     -
7     Seek_Error_Rate     POSR--     177618305     082     060     030         -
9     Power_On_Hours     -O--CK     5920     094     094     000     94%     -
10     Spin_Retry_Count     PO--C-     0     100     100     097     100%     -
12     Power_Cycle_Count     -O--CK     1212     099     099     020     99%     -
184     End-to-End_Error     -O--CK     0     100     100     099         -
187     Reported_Uncorrect     -O--CK     1002     001     001     000         -
188     Command_Timeout     -O--CK     0     100     100     000         -
189     High_Fly_Writes     -O-RCK     0     100     100     000         -
190     Airflow_Temperature_Cel     -O---K     36     064 (36°C)     047 (53°C)     045 (55°C)         -
194     Temperature_Celsius     -O---K     36     036     053     000         -
195     Hardware_ECC_Recovered     -O-RC-     127019464     054     046     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%     5919     -
# 2     Short offline     Completed without error     00%     5902     -
# 3     Short offline     Completed: read failure     90%     5902     364129531
# 4     Short offline     Completed: read failure     90%     5901     364129531
# 5     Short offline     Completed without error     00%     5789     -
# 6     Short offline     Completed without error     00%     5788     -
# 7     Short offline     Completed without error     00%     4957     -
Rendered in: 0.723 seconds

As in the start of Fix-disk I seem to have a failure at 364129531
so my question is do I need to be concerned? Is my HDD on the way out? Do I need to carry out any further tests etc.?
 

MartinLiddle

Super Moderator
Staff member
so my question is do I need to be concerned? Is my HDD on the way out? Do I need to carry out any further tests etc.?
Looking at the data after the fix-disk run it looks OK to me. I would just keep an eye on the hard drive diagnostics and run fix-disk again in a month. If that reports no problems then you should be OK.
 

af123

Administrator
Staff member
As in the start of Fix-disk I seem to have a failure at 364129531
That's just showing up in the historical log. There are no problem sectors on the disk now and the one that was suspected as faulty by the drive firmware turned out to be ok too.
 
OP
Stummery

Stummery

Member
Thank you both for your replies. Good to know your thoughts. :doublethumbsup:
I will keep an eye on the drive and carry out a Fix-disk check again in a month.
I have also installed the beta version of Fix-disk (tmenu) so that the next time I run the check I won't need to have the laptop on and connected for the whole time. :)
 

prpr

Well-Known Member
Fix-disk and Tmenu are not the same thing. I believe you need both packages installed for the new functionality.
 

af123

Administrator
Staff member
Fix-disk and Tmenu are not the same thing. I believe you need both packages installed for the new functionality.
Just tmenu is enough. Updating fix-disk will give you the progress updates on the front panel.
 
Top