1 |
On Fri, Feb 26, 2010 at 8:01 AM, Alex Schuster <wonko@×××××××××.org> wrote: |
2 |
> Mark Knecht writes: |
3 |
> |
4 |
>> Yes, I do use smartctl on some other machines although I'm not very |
5 |
>> good about it and your write-up is helpful so thanks for that. |
6 |
>> |
7 |
>> My wife's machines is older and and I don't think SMART is |
8 |
>> supported on her drive. Note the lack of a * on the SMART line in |
9 |
>> hdparm -I: |
10 |
> |
11 |
> Okay, but it still states: |
12 |
> |
13 |
>> * SMART error logging |
14 |
>> * SMART self-test |
15 |
> |
16 |
> So maybe smartctl -t long /dev/hda still works? Just give it a try. |
17 |
|
18 |
No, -t long fails the same way. Basically every time I try to use |
19 |
smartctl on the drive it seems to issue one of these 3-line reports |
20 |
about SectorIDNotFound in dmesg. My other machines don't do this. Not |
21 |
a good sign I think... |
22 |
|
23 |
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } |
24 |
hda: task_no_data_intr: error=0x10 { SectorIdNotFound }, |
25 |
LBAsect=16777008, sector=18446744073709551615 |
26 |
hda: possibly failed opcode: 0xb0 |
27 |
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } |
28 |
hda: task_no_data_intr: error=0x10 { SectorIdNotFound }, |
29 |
LBAsect=262192, sector=18446744073709551615 |
30 |
hda: possibly failed opcode: 0xb0 |
31 |
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } |
32 |
hda: task_no_data_intr: error=0x10 { SectorIdNotFound }, LBAsect=48, |
33 |
sector=18446744073709551615 |
34 |
hda: possibly failed opcode: 0xb0 |
35 |
|
36 |
These command create the same sort of lines in dmesg: |
37 |
|
38 |
dragonfly ~ # smartctl -i /dev/hda |
39 |
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen |
40 |
Home page is http://smartmontools.sourceforge.net/ |
41 |
|
42 |
=== START OF INFORMATION SECTION === |
43 |
Model Family: Western Digital Caviar family |
44 |
Device Model: WDC WD1600BB-00FTA0 |
45 |
Serial Number: WD-WMAES2091586 |
46 |
Firmware Version: 15.05R15 |
47 |
User Capacity: 160,041,885,696 bytes |
48 |
Device is: In smartctl database [for details use: -P show] |
49 |
ATA Version is: 6 |
50 |
ATA Standard is: Exact ATA specification draft version not indicated |
51 |
Local Time is: Fri Feb 26 08:49:00 2010 PST |
52 |
SMART support is: Available - device has SMART capability. |
53 |
SMART support is: Disabled |
54 |
|
55 |
SMART Disabled. Use option -s with argument 'on' to enable it. |
56 |
dragonfly ~ # smartctl -P show /dev/hda |
57 |
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen |
58 |
Home page is http://smartmontools.sourceforge.net/ |
59 |
|
60 |
Drive found in smartmontools Database. Drive identity strings: |
61 |
MODEL: WDC WD1600BB-00FTA0 |
62 |
FIRMWARE: 15.05R15 |
63 |
match smartmontools Drive Database entry: |
64 |
MODEL REGEXP: ^WDC WD(2|3|4|6|8|10|12|16|18|20|25)00BB-.*$ |
65 |
FIRMWARE REGEXP: .* |
66 |
MODEL FAMILY: Western Digital Caviar family |
67 |
ATTRIBUTE OPTIONS: None preset; no -v options are required. |
68 |
dragonfly ~ # |
69 |
|
70 |
|
71 |
<SNIP> |
72 |
>> |
73 |
>> I've not tried the -T permissive options. |
74 |
> |
75 |
> I would :) There is also a BIOS setting for SMART, but I think this does |
76 |
> not matter here, and it's only for being able to report a failing drive |
77 |
> before booting. |
78 |
|
79 |
Tried -T permissive and -T verypermissive. Same result. More lines and |
80 |
told it's not turning on. |
81 |
|
82 |
Could this have ANYTHING to do with kernel configuation? Is there |
83 |
anything required at the kernel level that I might not have turned on? |
84 |
|
85 |
> |
86 |
>> I've never used badblocks as it seems I should only do that off-line. |
87 |
>> This might be a good time to boot with a CD and try it out. |
88 |
> |
89 |
> In read-only mode, you can use it when the system is running. Only the |
90 |
> write test (option -n) refuses to run if partitions are mounted from the |
91 |
> drive. So I'd do the 'badblocks -sv /dev/hda' right now, if you do not |
92 |
> need the drive at full speed for a while. You can interrupt it at any |
93 |
> point with Ctrl-Z and continue with the fg command. |
94 |
> |
95 |
OK, I've started that test and will report back later what it says. |
96 |
|
97 |
Thanks! |
98 |
|
99 |
- Mark |