From: Andrew Dunn <andrew.g.dunn@gmail.com>
To: linux-raid list <linux-raid@vger.kernel.org>
Subject: Re: RAID down, dont know why!
Date: Sun, 08 Nov 2009 09:24:20 -0500 [thread overview]
Message-ID: <4AF6D494.2050207@gmail.com> (raw)
In-Reply-To: <20091108142238.GA11786@cthulhu.home.robinhill.me.uk>
What would I be looking for on this? Its a lot to sift through.
Currently just line-by-lining it.
Robin Hill wrote:
> On Sun Nov 08, 2009 at 09:00:29AM -0500, 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?
>>
>> What kind of logs do you need, I really need help!
>>
>>
> From the message you've posted, it looks like something has triggered
> the (simultaneous) removal of four drives from the array. I'd check the
> dmesg output - it should provide some information. I'd guess these four
> drives are all attached to the same controller (are they external or
> internal?), so possibly the controller reset (or for external drives, it
> could be a cable issue).
>
> You should be able to force an assembly anyway (using the --force flag)
> but I'd make sure you know exactly what the issue is first, otherwise
> this is likely to happen again.
>
> Cheers,
> Robin
>
--
Andrew Dunn
http://agdunn.net
next prev parent reply other threads:[~2009-11-08 14:24 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
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 [this message]
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=4AF6D494.2050207@gmail.com \
--to=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).