From: Roman Kagan <Roman.Kagan@itep.ru>
To: linux-kernel@vger.kernel.org
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Subject: Re: Problem: IDE data corruption with VIA chipsets on2.4.20-19.8+others
Date: Fri, 12 Sep 2003 15:19:28 +0400 [thread overview]
Message-ID: <20030912111928.GA5641@panda.itep.ru> (raw)
On Fri, Sep 12, 2003 at 04:14:54AM +0000, Rogier Wolff wrote:
> Anyway, speaking about SMART, some "smartd" was interfering with
> normal operation on one of our systems and we saw similar "nasty"
> stuff on that system until I removed "smartd".
>
> Aug 10 06:54:25 falbala kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> Aug 10 06:54:25 falbala kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> Aug 10 06:54:25 falbala kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> Aug 10 06:54:25 falbala kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
> Aug 10 07:24:25 falbala kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> Aug 10 07:24:25 falbala kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> Aug 10 07:24:25 falbala kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> Aug 10 07:24:25 falbala kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
> Aug 10 08:24:25 falbala kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> Aug 10 08:24:25 falbala kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> Aug 10 08:24:25 falbala kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> Aug 10 08:24:25 falbala kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
You probably have SMART disabled on those drives by BIOS, and smartd is
not smart enough to enable it before trying to use it so the drives
complain. I had the same problem on my GigaByte mobo where the BIOS
setup didn't even provide an option to turn SMART on (like earlier Award
BIOSes did).
Check with smartctl -i /dev/hdX. Enable with smartctl -e /dev/hdX
_before_ starting smartd.
Sorry for OT.
Roman.
next reply other threads:[~2003-09-12 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 11:19 Roman Kagan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 11:45 Problem: IDE data corruption with VIA chipsets on2.4.20-19.8+others John Bradford
2003-09-11 19:11 Eric Bickle
2003-09-11 18:20 Eric Bickle
2003-09-11 18:43 ` Alan Cox
2003-09-12 8:14 ` Rogier Wolff
2003-09-12 10:44 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030912111928.GA5641@panda.itep.ru \
--to=roman.kagan@itep.ru \
--cc=R.E.Wolff@BitWizard.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.