From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: "Bryn M. Reeves" <bmr@redhat.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: help decoding aacraid errors (3.10.40 kernel)
Date: Fri, 27 Jun 2014 12:59:18 +0200 [thread overview]
Message-ID: <201406271259.18659.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <20140627104131.GD10042@localhost.localdomain>
On Friday 27 of June 2014, Bryn M. Reeves wrote:
> On Fri, Jun 27, 2014 at 10:55:08AM +0200, Arkadiusz Miskiewicz wrote:
> > [3757350.671860] Result: hostbyte=0x00 driverbyte=0x08
> > [3757350.671862] sd 0:0:2:0: [sdc]
> > [3757350.671863] Sense Key : 0x4 [current]
>
> http://www.t10.org/lists/2sensekey.htm
>
> 0x4 is "hardware error".
>
> > [3757350.671866] sd 0:0:2:0: [sdc]
> > [3757350.671868] ASC=0x44 ASCQ=0x0
>
> http://www.t10.org/lists/asc-num.htm
>
> 0x44/0x00 is "internal target failure".
Thanks for links. I wonder why kernel doesn't decode these to be actually
readable without a need for asking on ml - was decoding considered?
Anyway Adaptec support helped with details:
http://ask.adaptec.com/app/answers/detail/a_id/14947/track/AvOF~QqxDv8S~TbvGmIW~yLb_fsq5C75Mv~s~zj~PP8l
Basically this controller finds "bad stripes" and blocks any access to these
areas resulting in errors :-/ What's more interesting there is no recovery
procedure beside recreation. Fun :-)
> Regards,
> Bryn.
--
Arkadiusz Miśkiewicz, arekm / maven.pl
Q: vger.kernel.org postmasters - always rude and impolite, hmm?
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-27 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 8:55 help decoding aacraid errors (3.10.40 kernel) Arkadiusz Miskiewicz
2014-06-27 10:41 ` Bryn M. Reeves
2014-06-27 10:59 ` Arkadiusz Miskiewicz [this message]
2014-06-27 11:37 ` Bryn M. Reeves
2014-06-27 11:48 ` Arkadiusz Miskiewicz
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=201406271259.18659.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=bmr@redhat.com \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox