From: Jeff Garzik <jeff@garzik.org>
To: LCID Fire <lcid-fire@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Link to sata drives fail randomly
Date: Fri, 24 Apr 2009 17:21:13 -0400 [thread overview]
Message-ID: <49F22D49.6000806@garzik.org> (raw)
In-Reply-To: <49F210C2.8050703@gmx.net>
LCID Fire wrote:
> First of - I have a Asus P5K WS where I'm running (or actually trying) a
> raid10 based on 4 sata drives. All drives are connected to esata slot
> panels which connect to the mainboard ports.
> The problem I'm encountering is the links to random drives fail every
> week or so.
> The strange thing is - the link is often failing for 2 drives at a time
> - which is the best when running a raid10 *sarcasm*
> The drives are WD, Samsung and Hitachi - so I think some specific driver
> failure can be ruled out.
> I attached the dmesg - perhaps someone could tell me which component is
> responsible for my drives losing their link.
Looks like a flaky cable, or bad connector.
Jeff
next prev parent reply other threads:[~2009-04-24 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 19:19 Link to sata drives fail randomly LCID Fire
2009-04-24 21:21 ` Jeff Garzik [this message]
2009-04-24 22:08 ` Ray Lee
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=49F22D49.6000806@garzik.org \
--to=jeff@garzik.org \
--cc=lcid-fire@gmx.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox