All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-raid@vger.kernel.org
Subject: emergency call for help: raid5 fallen apart
Date: Wed, 24 Feb 2010 15:54:47 +0100	[thread overview]
Message-ID: <4B853DB7.1060406@xunil.at> (raw)


Sorry for maybe FAQing, I am in emergency mode:

customer server, RAID5 + hotspare, 4 drives ...

gentoo Linux version 2.6.25-gentoo-r7

mdadm 2.6.4-r1 here

-

one of the 4 drives showed massive errors in dmesg, /dev/sdc
SMART-errors etc.
bought new drive and wanted to swap today.

# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb1[1] sda1[0]
      104320 blocks [2/2] [UU]

md3 : active raid5 sdb3[1] sda3[0]
      19550976 blocks level 5, 64k chunk, algorithm 2 [3/2] [UU_]

md4 : inactive sdb4[1](S) sdd4[3](S) sdc4[2](S) sda4[0](S)
      583641088 blocks



-


I did:

mdadm /dev/md3 --fail /dev/sdc3

went OK

mdadm /dev/md4 --remove /dev/sdc3

OK as well, raid md3 rebuilt

-

With md4 I was too aggressive maybe:

mdadm /dev/md4 --fail /dev/sdc4 --remove /dev/sdc4

this rendered md4 unusable, even after a reboot it can't be reassambled.

This is bad, to say the least.

md4 : inactive sdb4[1](S) sdd4[3](S) sdc4[2](S) sda4[0](S)
      583641088 blocks


What to try?

This is a crucial server and I feel a lot of pressure.
Rebuilding that raid would mean a lot of restore-work etc.
So I would really appreciate a goo advice here.

THANKS!

Stefan



             reply	other threads:[~2010-02-24 14:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 14:54 Stefan G. Weichinger [this message]
2010-02-24 15:05 ` emergency call for help: raid5 fallen apart Stefan G. Weichinger
2010-02-24 15:22   ` Robin Hill
2010-02-24 15:32     ` Stefan G. Weichinger
2010-02-24 16:38       ` Stefan G. Weichinger
2010-02-24 16:53         ` Stefan G. Weichinger
2010-02-24 17:02           ` Stefan G. Weichinger
2010-02-25  8:05             ` Giovanni Tessore
2010-02-25 16:27               ` Stefan /*St0fF*/ Hübner
2010-02-25 16:45               ` John Robinson
2010-02-25 17:41                 ` Dawning Sky
2010-02-25 18:31                   ` John Robinson
2010-02-26  2:42                     ` Michael Evans
2010-02-26 20:15                 ` Bill Davidsen
2010-02-28 11:50                 ` Stefan /*St0fF*/ Hübner
2010-02-28 12:52                   ` Stefan /*St0fF*/ Hübner
2010-02-24 17:09           ` Robin Hill
2010-02-24 17:28             ` Stefan G. Weichinger
2010-02-24 17:35             ` Stefan G. Weichinger
2010-02-24 18:12               ` Robin Hill
2010-02-24 19:54                 ` Stefan G. Weichinger

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=4B853DB7.1060406@xunil.at \
    --to=lists@xunil.at \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.