linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: John McMonagle <johnm@advocap.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid corruption problems.
Date: Mon, 25 Dec 2006 14:06:12 -0500	[thread overview]
Message-ID: <45902124.8080205@tmr.com> (raw)
In-Reply-To: <458E880A.7030400@advocap.org>

John McMonagle wrote:
> Bill Davidsen wrote:
>
>   
>> John McMonagle wrote:
>>
>>     
>>> Have a raid1  backup server that seems to get corrupted.
>>> This is the 3rd time in about a year.
>>> Have 2 other backup servers that were cloned from this one that have
>>> no problems.
>>>
>>> Done a couple kernel upgrades recently.
>>> Now has 2.6.18-2 kernel.
>>> It's based on Debian sarge.
>>>
>>> It's a low end Intel server motherboard using ata_piix sata driver.
>>> Have another mother board just like doing raid1 with sata drives that
>>> has had no problems but it has a much lighter disk load.
>>> smartctl has never shown any problems.
>>> In /sys/block/md2 did
>>> echo check > syncaction
>>> No error messages but mismatch_cnt  is 1152.
>>> rc0/errors and rc1/errors are both 0.
>>>
>>> I'm guessing a hardware problem.
>>> Any suggestions? 
>>>       
>> Since memory is the easiest to test, I'd try memtest86+ for at least
>> 12 hr. If this were PATA I'd suggest replugging the cables, but it's
>> lower probability with SATA. Still, probably worth trying.
>>
>>     
> Ran  Memtest86+ for over 18 hours with no errors.
> Also have ecc ram.
> I can look at the cables next time I'm  there.
> Doesn't  sata do some sort of error checking over the cables?
> Anything else to try?

I wish I had another reasonable idea, but memory problems are the big 
target. Is the firmware current level (if you can compare against the 
servers which are working well that would really be good). Other than 
that power supply is the only thing even reasonably likely, particularly 
if it happens under heavy load. Have you looked at the BIOS voltage and 
temp reports just to see if they suggest anything?

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


      reply	other threads:[~2006-12-25 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-15 19:52 Raid corruption problems John McMonagle
2006-12-19 21:39 ` Bill Davidsen
2006-12-24 14:00   ` John McMonagle
2006-12-25 19:06     ` Bill Davidsen [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=45902124.8080205@tmr.com \
    --to=davidsen@tmr.com \
    --cc=johnm@advocap.org \
    --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).