From: Jeff Garzik <jeff@garzik.org>
To: Tomas Lund <tlund@nxs.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: Need help understanding SATA error message.
Date: Fri, 28 Mar 2008 09:40:37 -0400 [thread overview]
Message-ID: <47ECF555.6050000@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0803271554050.5510@envy.nxs.se>
Tomas Lund wrote:
> Hello,
>
> I have a SuperMicro X7SBi with ICH9R SATA running 64bit linux 2.6.24.4.
> I have 4 1TB disks connected to the motherboard, and one of the disks is
> logging an error message. Everything is brand new, and hooked up just a
> few weeks ago.
>
> S.M.A.R.T. shows no errors (see output from "smartctl -a" at the bottom
> of this email) after running both a short and long offline selftest, and
> my question is if its possible to tell from this error message what the
> problem is. The result "51/04:00:0a:24:f9" is a bit crypting to me, and
> it would be nice to know what the problem actually is before returning
> the disk.
What a coincidence :) The ata wiki, just created yesterday, had a new
page added yesterday:
http://ata.wiki.kernel.org/index.php/Libata_error_messages
Regards,
Jeff
next prev parent reply other threads:[~2008-03-28 13:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 7:04 Need help understanding SATA error message Tomas Lund
2008-03-28 13:40 ` Jeff Garzik [this message]
2008-03-28 14:28 ` Tomas Lund
2008-03-28 15:49 ` Mark Lord
2008-03-28 15:59 ` Mark Lord
2008-03-28 22:21 ` Tomas Lund
2008-03-29 3:50 ` Mark Lord
2008-03-30 15:01 ` Tomas Lund
2008-03-31 0:59 ` Tejun Heo
2008-03-31 14:53 ` Mark Lord
2008-04-01 0:26 ` Tejun Heo
2008-04-01 2:01 ` Mark Lord
2008-04-01 7:11 ` Tomas Lund
2008-04-01 12:05 ` Mark Lord
2008-04-01 16:15 ` Tejun Heo
2008-04-02 5:17 ` Tomas Lund
2008-04-03 10:39 ` Tomas Lund
2008-04-11 6:16 ` Tejun Heo
2008-03-29 3:54 ` Mark Lord
2008-03-29 10:39 ` Tomas Lund
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=47ECF555.6050000@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=tlund@nxs.se \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).