From: Andre Noll <maan@systemlinux.org>
To: Moses Leslie <moses@flyingcroc.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: silent corruption with RAID1
Date: Sun, 26 Feb 2006 09:22:09 +0100 [thread overview]
Message-ID: <20060226082209.GH7030@skl-net.de> (raw)
In-Reply-To: <20060225182714.F4550@fincher.users.accretive-networks.net>
On 18:40, Moses Leslie wrote:
> 0000:00:0a.0 Unknown mass storage controller: Silicon Image, Inc.
> (formerly CMD Technology Inc) SiI 3112 [SATALink/SATARaid] Serial ATA
> Controller (rev 02)
Do you have Seagate drives? Some models have problems with this controller..
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
next prev parent reply other threads:[~2006-02-26 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 2:40 silent corruption with RAID1 Moses Leslie
2006-02-26 5:07 ` Bill Davidsen
2006-02-26 8:22 ` Andre Noll [this message]
2006-02-26 8:57 ` Moses Leslie
2006-02-26 9:05 ` Andre Noll
2006-02-26 17:39 ` Moses Leslie
2006-02-27 0:55 ` Moses Leslie
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=20060226082209.GH7030@skl-net.de \
--to=maan@systemlinux.org \
--cc=linux-raid@vger.kernel.org \
--cc=moses@flyingcroc.net \
/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).