From: Nicolas Jungers <nicolas@jungers.net>
To: linux-raid@vger.kernel.org
Subject: trouble repairing raid10
Date: Wed, 02 Jun 2010 18:25:58 +0200 [thread overview]
Message-ID: <4C068616.3070703@jungers.net> (raw)
I've a 4 HD raid10 with to failed drive. Any attempt I made to add 2
replacement disks fail consistently.
mdadm -Af /dev/md1 /dev/sdm2 /dev/sdp2 /dev/sdb2 /dev/sdd2
mdadm: failed to add /dev/sdd2 to /dev/md1: Device or resource busy
mdadm: /dev/md1 assembled from 2 drives and 1 spare - not enough to
start the array.
or
root@disk:~# mdadm -AR /dev/md1 /dev/sdm2 /dev/sdp2
mdadm: failed to RUN_ARRAY /dev/md1: Input/output error
mdadm: Not enough devices to start the array.
root@disk:~# mdadm --add /dev/md1 /dev/sdb2
mdadm: add new device failed for /dev/sdb2 as 4: Invalid argument
The array is in near mode and I lost disk 0 and 1. Does it mean that my
data are toasted?
mdadm --examine /dev/sdm2
/dev/sdm2:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : d90ad6fe:1355134f:f83ffadc:a4fe7859
Name : m1:1
Creation Time : Thu Apr 1 21:28:58 2010
Raid Level : raid10
Raid Devices : 4
Avail Dev Size : 3907026909 (1863.02 GiB 2000.40 GB)
Array Size : 7814049792 (3726.03 GiB 4000.79 GB)
Used Dev Size : 3907024896 (1863.01 GiB 2000.40 GB)
Data Offset : 272 sectors
Super Offset : 8 sectors
State : clean
Device UUID : e217355e:632ac2f0:8120e55e:3878bd88
Update Time : Wed Jun 2 12:31:39 2010
Checksum : feef2809 - correct
Events : 1377156
Layout : near=2, far=1
Chunk Size : 1024K
Array Slot : 3 (failed, failed, 2, 3)
Array State : __uU 2 failed
next reply other threads:[~2010-06-02 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 16:25 Nicolas Jungers [this message]
2010-06-03 0:19 ` trouble repairing raid10 Neil Brown
2010-06-03 4:38 ` Nicolas Jungers
2010-06-06 16:28 ` Nicolas Jungers
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=4C068616.3070703@jungers.net \
--to=nicolas@jungers.net \
--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).