Disk realloc sector count is: 524 on a refurbed box

A

adgibs99

Member
I just received a newly refurbished FOX HDR T2 from Humax Direct and when I installed the custom firmware this warning was waiting for me.....should I be concerned???? Should it go back?

!! WARNING !!

There appear to be some hardware problems with the internal hard disk on this device.

Disk realloc sector count is: 524

Don't panic; for help, visit wiki.hummy.tv
 
adgibs99 said:
There appear to be some hardware problems with the internal hard disk on this device.

Disk realloc sector count is: 524
Click to expand...
What size disk is it? My crude rule of thumb is start worrying at 500 reallocated sectors for a 500GB drive and at a 1000 sectors for a 1TB drive. However I do agree that the rate at which sectors are being reallocated is more important. I would watch what happens for a few days. By the way what are the power on hours reported to be?
 
Its a 1gb drive - Seagate Pipeline 5900.2. Power on hours are 4069.

Output from Hard Disk diagnostic is:
IDNameFlagsRaw ValueValueWorstThreshTypeUpdatedWhen Failed
1 Raw_Read_Error_Rate POSR-- 12826918 107 099 006 Pre-fail Always -
3 Spin_Up_Time PO---- 0 095 093 000 Pre-fail Always -
4 Start_Stop_Count -O--CK 5872 095 095 020 Old_age Always -
5 Reallocated_Sector_Ct PO--CK 524 088 088 036 Pre-fail Always -
7 Seek_Error_Rate POSR-- 122424374 081 060 030 Pre-fail Always -
9 Power_On_Hours -O--CK 4069 096 096 000 Old_age Always -
10 Spin_Retry_Count PO--C- 0 100 100 097 Pre-fail Always -
12 Power_Cycle_Count -O--CK 2936 098 098 020 Old_age Always -
184 End-to-End_Error -O--CK 0 100 100 099 Old_age Always -
187 Reported_Uncorrect -O--CK 0 100 100 000 Old_age Always -
188 Command_Timeout -O--CK 4295032833 100 100 000 Old_age Always -
189 High_Fly_Writes -O-RCK 1 099 099 000 Old_age Always -
190 Airflow_Temperature_Cel -O---K 49 051 044 045 Old_age Always In_the_past
194 Temperature_Celsius -O---K 49 049 056 000 Old_age Always -
195 Hardware_ECC_Recovered -O-RC- 12826918 047 038 000 Old_age Always -
197 Current_Pending_Sector -O--C- 0 100 100 000 Old_age Always -
198 Offline_Uncorrectable ----C- 0 100 100 000 Old_age Offline -
199 UDMA_CRC_Error_Count -OSRCK 0 200 200 000 Old_age Always -
 
That's quite a lot older than I would expect, even from a refurb. The problem you have is that the only way you could know that there are that many reallocated sectors is by installing the custom firmware or physically removing the disk and connecting it to a PC. The high count probably indicates the reason that the box was originally returned to Humax. However, the sector reallocations are complete and there are no outstanding sectors (attributes 197 & 198) so if the box is behaving well and the number of sectors doesn't increase then you don't have a problem. You can acknowledge the current values in the web interface and it will warn you if anything changes.
 
Running fix-disk found lots of error:
Code: 
hmx_int_stor: |================================                \ 66.4% 
hmx_int_stor: |================================                | 66.5% 
hmx_int_stor: |================================                / 66.6% 
                                                                             
Inode 57409685 has illegal block(s).  Clear? yes
 
Illegal block #12 (1433041147) in inode 57409685.  CLEARED.
Illegal block #13 (2840868447) in inode 57409685.  CLEARED.
Illegal block #14 (3893332017) in inode 57409685.  CLEARED.
Illegal block #15 (774995786) in inode 57409685.  CLEARED.
Illegal block #16 (896703822) in inode 57409685.  CLEARED.
Illegal block #17 (2073722890) in inode 57409685.  CLEARED.
Illegal block #18 (2094431066) in inode 57409685.  CLEARED.
Illegal block #19 (543092088) in inode 57409685.  CLEARED.
Illegal block #20 (490383444) in inode 57409685.  CLEARED.
Illegal block #21 (3635354511) in inode 57409685.  CLEARED.
Illegal block #22 (2618952394) in inode 57409685.  CLEARED.
Too many illegal blocks in inode 57409685.
Clear inode? yes
 
Inode 57409686 has illegal block(s).  Clear? yes
 
Illegal block #12 (3949067663) in inode 57409686.  CLEARED.
Illegal block #13 (2673693975) in inode 57409686.  CLEARED.
Illegal block #14 (4168824423) in inode 57409686.  CLEARED.
Illegal block #15 (764663815) in inode 57409686.  CLEARED.
Illegal block #17 (1668836373) in inode 57409686.  CLEARED.
Illegal block #18 (4144017801) in inode 57409686.  CLEARED.
Illegal block #19 (998797415) in inode 57409686.  CLEARED.
Illegal block #20 (3895119560) in inode 57409686.  CLEARED.
Illegal block #21 (1706366962) in inode 57409686.  CLEARED.
Illegal block #22 (2400425212) in inode 57409686.  CLEARED.
Illegal block #23 (958709308) in inode 57409686.  CLEARED.
Too many illegal blocks in inode 57409686.
Clear inode? yes
 
hmx_int_stor: |================================                - 66.7% 
hmx_int_stor: |================================                \ 66.8% 
hmx_int_stor: |================================                | 66.9%

and

Code: 
hmx_int_stor: |=============================================  \ 94.8% 
hmx_int_stor: |==============================================  | 94.9% 
                                                                             
Unattached inode 57409679
Connect to /lost+found? yes
 
Inode 57409679 ref count is 2, should be 1.  Fix? yes
 
Unattached inode 57409691
Connect to /lost+found? yes
 
Inode 57409691 ref count is 2, should be 1.  Fix? yes
 
hmx_int_stor: |==============================================  / 95.0% 
                                                                             
Pass 5: Checking group summary information
hmx_int_stor: |==============================================  - 95.1% 
                                                                             
Block bitmap differences:  +(14352898--14352903) +(14516738--14516742)
Fix? yes
 
hmx_int_stor: |==============================================  \ 95.0% 
hmx_int_stor: |==============================================  | 95.1% 
hmx_int_stor: |==============================================  / 95.2%

and


Code: 
hmx_int_stor: |=============================================== - 97.3% 
hmx_int_stor: |=============================================== \ 97.4% 
hmx_int_stor: |=============================================== | 97.5% 
                                                                             
Free blocks count wrong for group #1 (29653, counted=29650).
Fix? yes
 
Free blocks count wrong for group #438 (6, counted=0).
Fix? yes
 
Free blocks count wrong for group #443 (6, counted=1).
Fix? yes
 
Free blocks count wrong (160183893, counted=160183879).
Fix? yes
 
hmx_int_stor: |=============================================== / 97.6% 
hmx_int_stor: |=============================================== - 97.7% 
hmx_int_stor: |=============================================== \ 97.8%


but all ok since then so I guess I'll just keep an eye on the reallocated sector count....
 
adgibs99 said:
but all ok since then so I guess I'll just keep an eye on the reallocated sector count....
Click to expand...
Yes that sounds a good idea. Our previous hard drive slowly accumulated reallocated sectors for a long time but then the rate per day started to increase quite rapidly and the box started to become unpleasant to use. However users have reported all sorts of failure modes so it is hard to know at the moment what is the commonest mode. With practice you can notice the sector reallocation on the TV as a brief (or not so brief if multiple sectors are involved) stutter in playback. If you are seeing the reallocated sector count increase, then probably best to ring up the supplier and complain about the stutters rather than tell them about custom firmware findings.
 
I had a rant in the HD section a while back. I bought a graded HD-Fox from Humax Direct which turned out to be older than the one it was replacing and was faulty. They do seem to let the odd lemon slip out. Even if it is working now, a disk in that condition is reaching the end of its life. If it were one of my boxes I would be ordering a replacement drive. If you possibly can find grounds to send it back I would do so sooner rather than later.
 
I guess without the custom firmware I wouldn't have known - although there was some picture break up on one of last nights recording (stuttering etc).
It passes the HDD test (the one in the normal Humax menu)....af123 - what would make it fail?
 
hdparm looks a bit drastic! all running ok at the moment and no new reallocated sectors - 12 months warranty left so I'll just keep an eye on it until it starts to cause problems - thanks for the speedy responses!
 
You must log in or register to reply here.
Back
Top