linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Landman <landman@scalableinformatics.com>
To: Andrew Dunn <andrew.g.dunn@gmail.com>
Cc: linux-raid list <linux-raid@vger.kernel.org>
Subject: Re: RAID down, dont know why!
Date: Sun, 08 Nov 2009 09:15:01 -0500	[thread overview]
Message-ID: <4AF6D265.7090104@scalableinformatics.com> (raw)
In-Reply-To: <4AF6D0F8.80704@gmail.com>

Andrew Dunn wrote:
> storrgie@ALEXANDRIA:~$ lsscsi  | grep sd[ijkl]
> [11:0:0:0]   disk    ATA      WDC WD1001FALS-0 0K05  /dev/sdi
> [11:0:1:0]   disk    ATA      WDC WD1001FALS-0 0K05  /dev/sdj
> [11:0:2:0]   disk    ATA      WDC WD1001FALS-0 0K05  /dev/sdk
> [11:0:3:0]   disk    ATA      WDC WD1001FALS-0 0K05  /dev/sdl
> 

Does smartctl report drive failure?

	smartctl -a /dev/sdi | grep "SMART overall-health"
	smartctl -a /dev/sdj | grep "SMART overall-health"
	smartctl -a /dev/sdk | grep "SMART overall-health"
	smartctl -a /dev/sdl | grep "SMART overall-health"

> 
> Joe Landman wrote:
>> Andrew Dunn wrote:
>>> I just copied 4+ TiB of information to this array, restarted 5 times
>>> and tried to access it.... What is going on?
>> It looks like you have 4 failed drives. sdl,sdi,sdj,sdk
>>
>> Is it possible you lost power or connectivity to those drives?
>>
>> If you have lsscsi installed, what does lsscsi tell you about this?
>>
>> lsscsi  | grep sd[ijkl]
>>
>> Given the proximity of the drives in ordering, I'd suspect a power
>> loss, or cable seating, or similar to those drives.
>>
>> Reseat power/signal cables on the drive bays, and see if this helps.
>>
>>
>> Joe
>>
> 


-- 
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics, Inc.
email: landman@scalableinformatics.com
web  : http://scalableinformatics.com
        http://scalableinformatics.com/jackrabbit
phone: +1 734 786 8423 x121
fax  : +1 866 888 3112
cell : +1 734 612 4615

  reply	other threads:[~2009-11-08 14:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08 14:00 RAID down, dont know why! Andrew Dunn
2009-11-08 14:07 ` Joe Landman
2009-11-08 14:08   ` Andrew Dunn
2009-11-08 14:15     ` Joe Landman [this message]
2009-11-08 14:21       ` Andrew Dunn
     [not found]     ` <4AF82DAC.4020307@harddata.com>
2009-11-09 22:03       ` Andrew Dunn
     [not found]   ` <4AF82D29.507@harddata.com>
     [not found]     ` <4AF82DE4.2040805@scalableinformatics.com>
2009-11-09 21:23       ` Andrew Dunn
2009-11-08 14:22 ` Robin Hill
2009-11-08 14:24   ` Andrew Dunn
2009-11-08 15:01     ` Robin Hill
2009-11-08 22:08       ` Ryan Wagoner
2009-11-08 22:15         ` Andrew Dunn

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=4AF6D265.7090104@scalableinformatics.com \
    --to=landman@scalableinformatics.com \
    --cc=andrew.g.dunn@gmail.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).