|
From: Bruce A. <ba...@gr...> - 2004-11-23 21:08:51
|
Hi Philip,
This is a feature, not a bug. It turns out that there are a number of
disks on the market whose identify device data indicates that they do not
support SMART LOG functions, although in fact they do. Hence we try these
commands even if the disk claims not to support them.
One can avoid all system log messages by simply not using the '-a'
argument of smartctl but instead using arguments corresponding only to the
actual supported features, eg:
smartctl -H /dev/hda
or
smartctl -H -l error /dev/hda
or whatever is suppported by your disk.
Cheers,
Bruce
On Tue, 23 Nov 2004, Philip Lafleur wrote:
> I noticed a few of these messages in my system logs:
>
> kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
>
> Then I stumbled upon a message in the smartmontools-support archives:
> http://sourceforge.net/mailarchive/forum.php?thread_id=2020594&forum_id=12495
>
> And I confirmed that smartctl/smartd were the culprits:
>
> Warning: device does not support Error Logging
> Error SMART Error Log Read failed: Input/output error
> Smartctl: SMART Error Log Read Failed
> Warning: device does not support Self Test Logging
> Error SMART Error Self-Test Log Read failed: Input/output error
> Smartctl: SMART Self Test Log Read Failed
> Device does not support Selective Self Tests/Logging
>
> From the thread, it appears that this bug was fixed a year ago, but I'm
> experiencing it with smartmontools 5.33.
>
> Philip
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Smartmontools-support mailing list
> Sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartmontools-support
>
>
|