[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44B8E19E.2060904@rtr.ca>
Date: Sat, 15 Jul 2006 08:37:50 -0400
From: Mark Lord <lkml@....ca>
To: Christian Trefzer <ctrefzer@....de>
Cc: lkml <linux-kernel@...r.kernel.org>
Subject: Re: FYI: strange libata EH lines in dmesg once after every bootup
>>> > >the following happens every time after bootup, tested with freshly built
>>> > >2.6.18-rc1-mm2:
>> > ..
>>> > >ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
>>> > >ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error)
>>> > >ata1: EH complete
>> > ..
>> >
>> > Those are S.M.A.R.T. commands.
>> >
>> > Either your drive does not support S.M.A.R.T.,
>> > or you have not enabled it it with smartctl
>
>
> This drive model surely supports S.M.A.R.T. but maybe support in the
> driver is still underway. I just did a
>
> # smartctl --device=ata --smart=on --offlineauto=off --saveauto=on -T permissive /dev/sdb
>
> and this is what I got:
>
> smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
> === START OF ENABLE/DISABLE COMMANDS SECTION ===
> SMART Enabled.
> Error SMART Enable Auto-save failed: Input/output error
> Smartctl: SMART Enable Attribute Autosave Failed.
>
> SMART Automatic Offline Testing Disabled.
Okay. Most likely your drive doesn't support the autosave features.
Just do "smartctl -d ata -a /dev/sdb" to see what it does support,
and then change the system startup scripts to not issue any unsupported
commands -- that'll get rid of those harmless boot time error messages.
Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists