linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Kyler Laird <kyler-keyword-linuxraid.6e1399@lairds.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: "cannot start dirty degraded array"
Date: Mon, 15 Jun 2009 11:54:22 -0400	[thread overview]
Message-ID: <4A366EAE.9010706@tmr.com> (raw)
In-Reply-To: <20090610200310.GF18313@lairds.com>

Kyler Laird wrote:
> I'm in a bind.  I have three RAID6s on a Sun X4540.  A bunch of disks
> threw error all of a sudden.  Two arrays came back (degraded) on reboot
> but the third is having problems.  
>   

Just a thought, when multiple units have errors at the same time, I 
suspect a power issue. And if these are real SCSI drives, it's possible 
for a drive to fail in such a way that it glitches the SCSI bus and 
causes the controller to think that multiple drives doing concurrent 
seeks have failed. I saw this often enough to have a script to force the 
controller to mark drives good and then test them one at a time when I 
was running ISP servers.

-- 
Bill Davidsen <davidsen@tmr.com>
  Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one error occurs during
wildcard (glob) expansion.


  parent reply	other threads:[~2009-06-15 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 20:03 "cannot start dirty degraded array" Kyler Laird
2009-06-14 23:32 ` Carlos Carvalho
2009-06-14 23:56   ` Kyler Laird
2009-06-15 15:54 ` Bill Davidsen [this message]
2009-06-15 15:57   ` Kyler Laird

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=4A366EAE.9010706@tmr.com \
    --to=davidsen@tmr.com \
    --cc=kyler-keyword-linuxraid.6e1399@lairds.com \
    --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).