linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Maurice Hilarius <maurice@harddata.com>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Question: how to identify failing disk in a RAID1
Date: Thu, 17 Apr 2008 09:12:02 -0400	[thread overview]
Message-ID: <48074CA2.2020004@tmr.com> (raw)
In-Reply-To: <480607F2.3060504@harddata.com>

Maurice Hilarius wrote:
> Morning Bill.
>
> BTW< I want to say "Thanks for your help with this" first.
> Just in case I forgot.
>
> So, I ran "check" once. It complained, and failed.
>
Does the failure provide any useful information?

> A few hours later, I ran it again, and it immediately returned "0"
>
I totally don't understand that, assuming that the first check was sone.

> I am still puzzled:
> Why it failed the first time
> Why it returned a result in a couple of seconds the second time.
> What it tells me?
>    I gather this means the md0 device is healthy.
>
I don't think so, I've never had a check *fail*, I just expect it to 
tell me how bad things are.

> So, meanwhile back at the ranch, I still think sda is failing..

I think it's time to be keeping a good backup, and hopefully someone 
else has a good thought on running this down more.

> Any thoughts on that?

The only thought I have at the moment is marginal power supply, and 
that's just because it can generate all manner of odd behaviors, rather 
than any other hints. Sorry.

If you aren't getting errors from SMART or logs, and I don't remember 
you sending me that info, I'm not sure how you determine which drive is 
the problem.

-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



  parent reply	other threads:[~2008-04-17 13:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 19:14 Question: how to identify failing disk in a RAID1 Maurice Hilarius
2008-04-13 19:29 ` Justin Piszcz
2008-04-14  1:14   ` Bill Davidsen
     [not found]     ` <4802CDA2.605@harddata.com>
2008-04-14 16:38       ` Bill Davidsen
     [not found]         ` <4804CD4F.7080303@harddata.com>
2008-04-15 18:14           ` Bill Davidsen
     [not found]             ` <48050DD6.7020404@harddata.com>
     [not found]               ` <48055EFA.8060505@tmr.com>
     [not found]                 ` <480607F2.3060504@harddata.com>
2008-04-17 13:12                   ` Bill Davidsen [this message]
     [not found]                     ` <48076096.2020804@harddata.com>
2008-04-18 13:17                       ` Bill Davidsen
     [not found]     ` <480F7105.9030405@harddata.com>
2008-04-23 18:54       ` Justin Piszcz
     [not found]         ` <480F8830.6020207@harddata.com>
2008-04-23 19:26           ` Justin Piszcz
2008-04-27 17:03             ` Keith Roberts
2008-04-27 19:28               ` Richard Scobie
2008-04-28  5:29                 ` Keith Roberts
2008-04-28  6:06                   ` Michael Tokarev
2008-04-28  7:01                   ` Richard Scobie
2008-04-27 21:53               ` Mark Hahn
  -- strict thread matches above, loose matches on Subject: below --
2008-04-18 17:36 David Lethe

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=48074CA2.2020004@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=maurice@harddata.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;
as well as URLs for NNTP newsgroup(s).