mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Lundell <linux@lundell-bros.com>
To: Daniel Egger <degger@fhm.edu>,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Two equal harddrives on one cable behaving different
Date: Tue, 27 Aug 2002 09:07:45 -0700	[thread overview]
Message-ID: <p05111a0db99151da8f21@[207.213.214.37]> (raw)
In-Reply-To: <1030446205.2539.13.camel@sonja.de.interearth.com>

At 1:03pm +0200 8/27/02, Daniel Egger wrote:
>I'm currently in the process of mirroring a drive with bad sector
>to an equal second one (same modell, same version, same firmware).
>Both of them are on the same cable, the old one as master, the new
>one is slave (now on the outer end of the cable). According to
>smartctl the old one is continously ressolving a couple CRC errors
>per hour while the second one hasn't suffered a single one yet.
>
>(195)Hardware ECC Recovered  0x001a   100   100   000       29678
>few minutes later:
>(195)Hardware ECC Recovered  0x001a   100   100   000       29694
>
>other drive:
>(195)Hardware ECC Recovered  0x001a   100   100   000       0
>
>The cable (80 conductor) seems fine (optically) and I'd wonder if it
>is the culprit because the drive on the outer end (now) works fine.

ECC errors get corrected in the drive, so it would be surprising if 
the cable had an effect. Do you have reason to think that's 
happening? That is, if you swap the drives on the cable, do the 
errors stick with the cable position, or the physical drive? I'd 
expect the latter, and if so would retire the drive.
-- 
/Jonathan Lundell.

      reply	other threads:[~2002-08-27 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27 11:03 Daniel Egger
2002-08-27 16:07 ` Jonathan Lundell [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='p05111a0db99151da8f21@[207.213.214.37]' \
    --to=linux@lundell-bros.com \
    --cc=degger@fhm.edu \
    --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

all inboxes | Powered by JetHome®