linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Smith <andy@lug.org.uk>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: "command 0x25 timeout, stat 0x50 host_stat 0x1"
Date: Sun, 11 Jun 2006 15:09:15 +0000	[thread overview]
Message-ID: <20060611150915.GL32471@strugglers.net> (raw)
In-Reply-To: <44822BE7.4010905@ucolick.org>

[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]

On Sat, Jun 03, 2006 at 05:40:07PM -0700, Patrik Jonsson wrote:
> Andy Smith wrote:
> > Booting the system with a Knoppix 4 DVD (kernel version 2.6.12), I
> > went to set up the md arrays and got a syslog full of this:
> > 
> > ata2: command 0x25 timeout, stat 0x50 host_stat 0x2
> > ata1: command 0x25 timeout, stat 0x50 host_stat 0x1
> > ata1: command 0x25 timeout, stat 0x50 host_stat 0x1
> > ata1: command 0x25 timeout, stat 0x50 host_stat 0x2
> > 
> > as well as a painfully slow (~100K/sec) initial resync.

[...]

> I shot in the dark, but cabling might be a culprit. I've had some issues
> with cables, both with the ridiculously unreliable SATA connectors
> coming out a little as well as with cables which must have been
> insufficiently shielded.

It actually seems to have been power related.  I'm using Icydock
SATA disk chassis which have two molex power connectors and one SATA
power connector for 3 drives.  I had thought that the differing
types made it an either/or situation, i.e. that it would be happy
with the two molex.  The "documentation" is what I would charitably
call terse.  Anyway after putting in the 3rd SATA power this problem
went away.

Cheers,
Andy

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-06-11 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-04  0:05 "command 0x25 timeout, stat 0x50 host_stat 0x1" Andy Smith
2006-06-04  0:40 ` Patrik Jonsson
2006-06-11 15:09   ` Andy Smith [this message]

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=20060611150915.GL32471@strugglers.net \
    --to=andy@lug.org.uk \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).