Using smartctl to detect scan errors (like google tells me to do ...)

[Jason Usher]

The big report that google published made it clear that even a single scan 
error in the SMART data of a disk drive is a good predictor of eventual 
failure...

However, when I run smartctl:

# smartctl -a /dev/da0 | grep -i pre-fail
  1 Raw_Read_Error_Rate 0x000b   100   100   016Pre-fail  Always   
-   0
  2 Throughput_Performance  0x0005   135   135   054Pre-fail  Offline  
-   84
  3 Spin_Up_Time0x0007   126   126   024Pre-fail  Always   
-   612 (Average 612)
  5 Reallocated_Sector_Ct   0x0033   100   100   005Pre-fail  Always   
-   0
  7 Seek_Error_Rate 0x000b   100   100   067Pre-fail  Always   
-   0
  8 Seek_Time_Performance   0x0005   123   123   020Pre-fail  Offline  
-   31
 10 Spin_Retry_Count0x0013   100   100   060Pre-fail  Always   
-   0


There is nothing called a scan error.  Further, the wikipedia page for 
S.M.A.R.T. has nothing in the error table called a scan error.


So ...


What is a scan error, and which metric should I tell smartctl to check ?


Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Using smartctl to detect scan errors (like google tells me to do ...)

[Bruce Cran]

On 09/07/2012 16:12, Jason Usher wrote:

What is a scan error, and which metric should I tell smartctl to check ?


I think they mean a SMART scan, as in a self-test - 
http://www.twopenguins.it/2011/12/test-an-hard-disk-with-smartctl/ has 
details of how to run it.


--
Bruce Cran
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org