1 |
On 6/2/10, Dale <rdalek1967@×××××.com> wrote: |
2 |
> smoker-new ~ # smartctl -l selftest /dev/hdb |
3 |
> smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen |
4 |
> Home page is http://smartmontools.sourceforge.net/ |
5 |
> |
6 |
> === START OF READ SMART DATA SECTION === |
7 |
> SMART Self-test log structure revision number 1 |
8 |
> Num Test_Description Status Remaining |
9 |
> LifeTime(hours) LBA_of_first_error |
10 |
> # 1 Extended offline Completed without error 00% |
11 |
> 1038 - |
12 |
> # 2 Short offline Completed without error 00% |
13 |
> 1037 - |
14 |
> # 3 Extended offline Completed without error 00% |
15 |
> 1075 - |
16 |
> # 4 Extended offline Completed without error 00% |
17 |
> 305 - |
18 |
> # 5 Extended offline Completed without error 00% |
19 |
> 660 - |
20 |
> # 6 Extended offline Completed without error 00% |
21 |
> 213 - |
22 |
> # 7 Extended offline Completed without error 00% |
23 |
> 687 - |
24 |
> # 8 Extended offline Completed without error 00% |
25 |
> 686 - |
26 |
> # 9 Extended offline Completed without error 00% |
27 |
> 629 - |
28 |
|
29 |
I was thinking about smartctl -A attributes table (or just plain -a |
30 |
for all), which might've showed a great number of sector relocations |
31 |
or other internal I/O-related issues. |
32 |
|
33 |
But this report raises another question: why aren't the reported |
34 |
lifetimes in an ascending list? They jump back and forth. |
35 |
|
36 |
-- |
37 |
Arttu V. |