linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian McKee <brian@soulspark.org>
To: linux-raid@vger.kernel.org
Subject: Raid5 Array stopped suddenly, no apparent error messages.
Date: Wed, 09 May 2012 11:08:56 -0700	[thread overview]
Message-ID: <4FAAB2B8.6090403@soulspark.org> (raw)

If this is not a good place to ask for help, please point me to where I
can ask. Sorry if I offend.

TL;DR: My question is this: is it safe to run mdadm --create
--assume-clean on an existing array? And by safe I mean: is it
guaranteed that the existing ext4 partition's data will not be lost when
I run the command?

Background: I have a 4.5TB Raid 5 Array (96% full) that has been up and
running for almost two years. A couple of months ago I upgraded my
kernel to 3.2.12 and yesterday around 2:00 PM this raid array stopped
working, became read only and started throwing a lot of I/O errors.

I assumed it was a failed drive but was saddened to see that according
to mdadm three drives had been removed from the array. The array
contains four drives, three 1.5 TB drives and one 2.0 TB drive
(partitioned so that it has a 1.5TB first partition to match the other
three). All three of the 1.5TB drives reported as bad according to mdadm.

I ran smartctl and it reported that all four drives were healthy which
gave me hope that something else had gone wrong and the data was okay.

For more details you can read this gentoo thread:
http://forums.gentoo.org/viewtopic-p-7033578.html

Summary: The three drives won't assemble because they are not fresh.

Any help or advice would be greatly appreciated. Mostly I want to know
if its safe to force mdadm to accept the drives into an array with
--create --assume-clean.

Thanks,

Brian McKee

             reply	other threads:[~2012-05-09 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 18:08 Brian McKee [this message]
2012-05-10 10:09 ` Raid5 Array stopped suddenly, no apparent error messages John Robinson
2012-05-10 15:50   ` Brian McKee

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=4FAAB2B8.6090403@soulspark.org \
    --to=brian@soulspark.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).