| 1 |
On 03/20/2013 10:50:51 PM, Carlos Hendson wrote: |
| 2 |
> I started a long test on the hard drive: |
| 3 |
> |
| 4 |
> smartctl -t long /dev/sda |
| 5 |
> |
| 6 |
> smartctl -a /dev/sda also appears to indicate various errors (the |
| 7 |
> output |
| 8 |
> is attached). I'll trying to track down some documentation as to what |
| 9 |
> they're actually reporting. |
| 10 |
> |
| 11 |
> Looking at the difference between the output of smartctl for before |
| 12 |
> and |
| 13 |
> during the test, there has been an increase in errors detected for ID |
| 14 |
> #195 |
| 15 |
> |
| 16 |
> Before test: |
| 17 |
> 195 Hardware_ECC_Recovered 0x001a 001 001 000 Old_age |
| 18 |
> Always |
| 19 |
> - 241822 |
| 20 |
> |
| 21 |
> During test: |
| 22 |
> 195 Hardware_ECC_Recovered 0x001a 001 001 000 Old_age |
| 23 |
> Always |
| 24 |
> - 243582 |
| 25 |
> |
| 26 |
> Could this be the cause of the stalls during compiles? If it is the |
| 27 |
> cause, is it possible for the kernel to detect such failures and |
| 28 |
> report |
| 29 |
> them? |
| 30 |
> |
| 31 |
|
| 32 |
These numbers are misleading. You might have a look at |
| 33 |
http://www.users.on.net/~fzabkar/HDD/Seagate_SER_RRER_HEC.html |
| 34 |
|
| 35 |
Helmut. |
Archives