From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: M Benz <mbenz74@hotmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: is my RAID safe?
Date: Sun, 26 Dec 2004 17:02:04 +0000 [thread overview]
Message-ID: <1104080521.16049.6.camel@localhost.localdomain> (raw)
In-Reply-To: <BAY15-F265CCA05303049813A8802B2980@phx.gbl>
On Sul, 2004-12-26 at 14:30, M Benz wrote:
> Today I found this that at my /var/log/message (kernel 2.6.10):
>
> Dec 26 21:35:14 s1 kernel: ata5: status=0x51 { DriveReady SeekComplete
> Error }
> Dec 26 21:35:14 s1 kernel: ata5: error=0x84 { DriveStatusError BadCRC }
>
> ata5 is md raid1 with ata6, both are sata drives connected to a promise
> SATA controller.
BadCRC is usually cable noise. The kernel will retry such an event
several times, then fall back to PIO and try that before it gives up.
next prev parent reply other threads:[~2004-12-26 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 14:30 is my RAID safe? M Benz
2004-12-26 17:02 ` Alan Cox [this message]
2004-12-26 18:18 ` Bartlomiej Zolnierkiewicz
2004-12-26 20:46 ` Norbert van Nobelen
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=1104080521.16049.6.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenz74@hotmail.com \
/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