Is my disc bust?

xyz321 said:
Note to others:- these figures are for the original 1TB disk please do not use these numbers on another disk.
Click to expand...
Out of interest, I checked the partition tables for the 2 boxes I look after and they are different, despite being identical models:
Code: 
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
 
  Device Boot      Start        End      Blocks  Id System
/dev/sda1              8    2104510    1052251+ 83 Linux
Partition 1 does not end on cylinder boundary
/dev/sda2        2104512  955787166  476841327+ 83 Linux
/dev/sda3      955787168  976768062    10490447+ 83 Linux
 
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
 
  Device Boot      Start        End      Blocks  Id System
/dev/sda1              2    2104514    1052256+ 83 Linux
/dev/sda2        2104515  955787174  476841330  83 Linux
/dev/sda3      955787175  976768064    10490445  83 Linux

Anyone any thoughts as to why (or which one is 'wrong')?
 
af123 said:
You have a new error on the disk at sector 7 that was exposed by the latest short test.
You need to fix that one too. Then another short test to see if there are any more. Rinse and repeat.
Click to expand...
What do you think about trying badblocks instead of smartctl, just to see how many errors there are? e.g.
Code: 
humax# badblocks -v /dev/sda 1000 0
 
Ran Badblocks -

Code: 
humax# badblocks -v /dev/sda 1000 0


Result

Code: 
Humax HDR-Fox T2 (humax) 1.02.32/2.18
 
To return to the menu, type: exit
 
humax# badblocks -v /dev/sda 1000 0
Checking blocks 0 to 1000
Checking for bad blocks (read-only test): 0 0.00% done, 0:08 elapsed
1 0.10% done, 0:24 elapsed
2 0.20% done, 0:32 elapsed
3 0.30% done, 0:40 elapsed
4
5
6
7
8
9
10
11
12
13
14
15
done
Pass completed, 16 bad blocks found.

But I don't know enough for this to be of value to me

So ran this

Code: 
humax# hdparm --repair-sector 7 --yes-i-know-what-i-am-doing /dev/sda
 
/dev/sda:
re-writing sector 7: succeeded


Then this...
Code: 
smartctl -t short /dev/sda
(wait a few minutes)
smartctl -l selftest /dev/sda

Now the check

Code: 
smartctl 5.41 2011-06-09 r3365 [7405b0-smp-linux-2.6.18-7.1] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
 
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA                                                                                       
 
_of_first_error
# 1  Short offline      Completed without error      00%      8890        -
# 2  Short offline      Completed: read failure      90%      8890        7
# 3  Short offline      Completed: read failure      90%      8889        6
# 4  Short offline      Completed: read failure      90%      8889        6
# 5  Short offline      Completed: read failure      90%      8889        6
# 6  Short offline      Completed: read failure      90%      8889        6
# 7  Short offline      Completed: read failure      90%      8889        6
# 8  Short offline      Completed: read failure      90%      8889        6
# 9  Short offline      Completed: read failure      90%      8889        6

Now reboot...

WOW - THANKS YOU DID IT

It's all back!!!!!!


Next...

What I'm thinking of is...
What do you think?
- Get an external disc to backup to
Back up
Then when it goes wrong again return it to the shop for repair under the warranty
It's got 3 years to go under the extended warranty

By the way I've got one happy wife

THANKS
 
Can you post the output of smartctl -A /dev/sda now? That will give us an idea of how sick your disk is now. It might well be fine now that you've repaired those bad sectors but the key indication will be the number of reallocated sectors shown against attribute 5.

Backing up the recordings you care about is always a good idea. If you're running the auto-unprotect package then even HD recordings will be decrypted during copy.
 
PH111 said:
Code: 
Checking for bad blocks (read-only test): 0 0.00% done, 0:08 elapsed
1 0.10% done, 0:24 elapsed
2 0.20% done, 0:32 elapsed
3 0.30% done, 0:40 elapsed
4
5
6
7
8
9
10
11
12
13
14
15
done
Pass completed, 16 bad blocks found.
Click to expand...
You need to repair all the other sectors listed, as you have done for 6 and 7.
You could then do a "long" instead of a "short" smartctl test, or run "badblocks -v /dev/sda" to test the whole disk.
It's all back!!!!!!
Click to expand...
Have you still got your recordings or is it just working again with an empty disk?
By the way I've got one happy wife
Click to expand...
#include "crudecomment.h"

(That's a C programmer's type joke!)
 
It would be interesting to see the results from running the badblocks command again. I suspect the output may be quite different.
 
Code: 
smartctl -A /dev/sda now?

Result

Code: 
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate    0x000f  088  088  006    Pre-fail  Always      -                   159895707
  3 Spin_Up_Time            0x0003  095  095  000    Pre-fail  Always      -                                           0
  4 Start_Stop_Count        0x0032  095  095  020    Old_age  Always      -                                  5418
  5 Reallocated_Sector_Ct  0x0033  070  070  036    Pre-fail  Always      -                                  1236
  7 Seek_Error_Rate        0x000f  083  060  030    Pre-fail  Always      -                           202621327
  9 Power_On_Hours          0x0032  090  090  000    Old_age  Always      -                               8890
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -                                           0
12 Power_Cycle_Count      0x0032  098  098  020    Old_age  Always      -                                2712
184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -                                      0
187 Reported_Uncorrect      0x0032  001  001  000    Old_age  Always      -                                859
188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -                                   0
189 High_Fly_Writes        0x003a  099  099  000    Old_age  Always      -                                         1
190 Airflow_Temperature_Cel 0x0022  062  033  045    Old_age  Always  In_the_past 38 (0 185 38 37)
194 Temperature_Celsius    0x0022  038  067  000    Old_age  Always      -                        38 (0 19 0 0)
195 Hardware_ECC_Recovered  0x001a  043  035  000    Old_age  Always      -           159895707
197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -                                  0
198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -                                       0
199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -                           0

prpr asked
Have you still got your recordings or is it just working again with an empty disk?

Yes got the recordings - they are there and play.



Badblocks command...

Code: 
humax# badblocks -v /dev/sda 1000 0
Checking blocks 0 to 1000
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found.

That looks nice.
 
But it only tests a minute amount of the disk. I still suggest you test it thoroughly as described in #45
 
Hi prpr

Thanks for the suggestion

Just took a look at doing a long test, and that told me it would be 234 minutes

So will have a go at that when I have longer available
 
PH111 said:
Just took a look at doing a long test, and that told me it would be 234 minutes

So will have a go at that when I have longer available
Click to expand...
It runs in the background, so you can just kick it off and it doesn't affect anything else (you don't need to be in Maintenance mode). You just have to poll the results once in a while to see if/where it has stopped and fix the relevant sector before setting it going again. "badblocks" is probably a better option as it will tell you everything bad in one run, whereas "smartctl" will only find the first error.
 
The problem is that badblocks produces false positives. It was showing 16 bad sectors above but only two needed fixing. A long test will be interrupted by file system operations unless in maintenance mode.
 
xyz321 said:
A long test will be interrupted by file system operations unless in maintenance mode.
Click to expand...
I beg to differ. I have just run one on my Humax in normal mode without any problems. Likewise on a PC. It is a background operation as far as the disk is concerned.
 
That's how I read xyz's post (the disk check operations will be interrupted by normal file system operations and then resume afterwards - ie the system will function normally during the check).
 
Sorry to labour this point, but a smartctl long test in maintenance mode takes the same amount of time as one in normal operation mode. I don't understand use of the term "interrupt" in this context, nor do I understand why anyone would want to do the test in maintenance mode, which stops you using the box as normal and doesn't gain you anything.
 
I don't understand what point you are labouring. In various clumsy ways we are all saying the same thing: the disk checking does not slug the normal Humax operations, but if it did one would use Maintenance Mode to give it full-time access.
 
In the past I have had disks which would abort a self test if the OS was accessing them. I could have sworn this disk did the same. However, it does seem to successfully run in background.

I am not sure how useful it is to run it in background. If faults are found they would have to be fixed in maintenance mode anyway. Most of the time people will only go into maintenance mode if there is a problem i.e possible dropouts etc. In this case there is little advantage in using normal mode to do the scan.
 
Have been out all day - so will run code now - and see how long it is before it finds an error

Edit
ran
smartctl -t long /dev/sda (in maitenance mode)
it said 234 min - will it tell me when it has finished and I can run
smartctl -a /dev/sda
 
xyz321 said:
In this case there is little advantage in using normal mode to do the scan.
Click to expand...
One advantage is that fan will run in normal mode. Things can get a bit hot if maintenance mode is used for too long (something I'm trying to fix).
 
It did get hot - and so I looked for a result after 2 hours (120 min)

I got the following

Code: 
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
 
=== START OF INFORMATION SECTION ===
Model Family:    Seagate Pipeline HD 5900.2
Device Model:    ST31000424CS
Serial Number:    5VX1FX8C
LU WWN Device Id: 5 000c50 037dc149d
Firmware Version: SC13
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:  8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sat Aug  3 21:33:24 2013 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
 
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.
 
General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 244) Self-test routine in progress...
                                        40% of test remaining.
Total time to complete Offline
data collection:                (  653) seconds.
Offline data collection
capabilities:                    (0x73) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (  1) minutes.
Extended self-test routine
recommended polling time:        ( 234) minutes.
Conveyance self-test routine
recommended polling time:        (  2) minutes.
SCT capabilities:              (0x103b) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.
 
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED                                                                                  RAW_VALUE
  1 Raw_Read_Error_Rate    0x000f  088  088  006    Pre-fail  Always      -                                                                                        166806241
  3 Spin_Up_Time            0x0003  095  095  000    Pre-fail  Always      -                                                                                        0
  4 Start_Stop_Count        0x0032  095  095  020    Old_age  Always      -                                                                                        5428
  5 Reallocated_Sector_Ct  0x0033  070  070  036    Pre-fail  Always      -                                                                                        1236
  7 Seek_Error_Rate        0x000f  083  060  030    Pre-fail  Always      -                                                                                        202656867
  9 Power_On_Hours          0x0032  090  090  000    Old_age  Always      -                                                                                        8897
10 Spin_Retry_Count        0x0013  100  100  097    Pre-fail  Always      -                                                                                        0
12 Power_Cycle_Count      0x0032  098  098  020    Old_age  Always      -                                                                                        2717
184 End-to-End_Error        0x0032  100  100  099    Old_age  Always      -                                                                                        0
187 Reported_Uncorrect      0x0032  001  001  000    Old_age  Always      -                                                                                        859
188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -                                                                                        0
189 High_Fly_Writes        0x003a  099  099  000    Old_age  Always      -                                                                                        1
190 Airflow_Temperature_Cel 0x0022  028  028  045    Old_age  Always  FAILING_NOW                                                                                  72 (0 187 72 44)
194 Temperature_Celsius    0x0022  072  072  000    Old_age  Always      -                                                                                        72 (0 19 0 0)
195 Hardware_ECC_Recovered  0x001a  036  035  000    Old_age  Always      -                                                                                        166806241
197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -                                                                                        0
198 Offline_Uncorrectable  0x0010  100  100  000    Old_age  Offline      -                                                                                        0
199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -                                                                                        0
 
SMART Error Log Version: 1
ATA Error Count: 863 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
 
Error 863 occurred at disk power-on lifetime: 8890 hours (370 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 07 00 00 00  Error: UNC at LBA = 0x00000007 = 7
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:04:05.950  READ DMA
  ec 00 00 07 00 00 a0 00      00:04:05.925  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:04:04.607  READ DMA
  ec 00 00 07 00 00 a0 00      00:04:04.582  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:04:03.295  READ DMA
 
Error 862 occurred at disk power-on lifetime: 8890 hours (370 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 07 00 00 00  Error: UNC at LBA = 0x00000007 = 7
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:04:04.607  READ DMA
  ec 00 00 07 00 00 a0 00      00:04:04.582  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:04:03.295  READ DMA
  ec 00 00 07 00 00 a0 00      00:04:03.270  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:04:01.972  READ DMA
 
Error 861 occurred at disk power-on lifetime: 8890 hours (370 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 07 00 00 00  Error: UNC at LBA = 0x00000007 = 7
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:04:03.295  READ DMA
  ec 00 00 07 00 00 a0 00      00:04:03.270  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:04:01.972  READ DMA
  ec 00 00 07 00 00 a0 00      00:04:01.947  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:04:00.620  READ DMA
 
Error 860 occurred at disk power-on lifetime: 8890 hours (370 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 07 00 00 00  Error: UNC at LBA = 0x00000007 = 7
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:04:01.972  READ DMA
  ec 00 00 07 00 00 a0 00      00:04:01.947  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:04:00.620  READ DMA
  ec 00 00 07 00 00 a0 00      00:04:00.595  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:03:59.278  READ DMA
 
Error 859 occurred at disk power-on lifetime: 8890 hours (370 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 07 00 00 00  Error: UNC at LBA = 0x00000007 = 7
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 00      00:04:00.620  READ DMA
  ec 00 00 07 00 00 a0 00      00:04:00.595  IDENTIFY DEVICE
  c8 00 08 00 00 00 e0 00      00:03:59.278  READ DMA
  b0 d5 01 e0 4f c2 00 00      00:03:59.277  SMART READ LOG
  ec 00 00 07 00 00 a0 00      00:03:59.252  IDENTIFY DEVICE
 
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_fi                                                                                  rst_error
# 1  Extended offline    Self-test routine in progress 40%      8897        -
# 2  Extended offline    Interrupted (host reset)      00%      8895        -
# 3  Extended offline    Interrupted (host reset)      00%      8895        -
# 4  Short offline      Completed without error      00%      8890        -
# 5  Short offline      Completed: read failure      90%      8890        7
# 6  Short offline      Completed: read failure      90%      8889        6
# 7  Short offline      Completed: read failure      90%      8889        6
# 8  Short offline      Completed: read failure      90%      8889        6
# 9  Short offline      Completed: read failure      90%      8889        6
#10  Short offline      Completed: read failure      90%      8889        6
#11  Short offline      Completed: read failure      90%      8889        6
#12  Short offline      Completed: read failure      90%      8889        6
 
SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 
humax#

Then I stopped it - and opend the door to the cabinet - then turned the Humax off.
We are watching via a different box tonight.

Thanks for your help

Please advise me on what these results show and when to run another test
 
You must log in or register to reply here.
Back
Top