From: Arthur Britto <ahbritto@iat.com>
To: linux-raid@vger.kernel.org
Subject: Help: Re-assemble raid-5 with inconsistent events.
Date: Fri, 21 Mar 2008 19:40:39 -0700 [thread overview]
Message-ID: <1206153639.16304.30.camel@loss.redstem.com> (raw)
Hi,
I have a RAID 5 with 6 components. The 4-port SATA controller died and
left the RAID in an inconsistent state. 2 of the 6 components have a
more recent event stamp than the others.
What command should I issue to re-assemble the RAID?
In particular, I don't want to force the RAID to be assembled with the
components in the wrong order. Especially as the order given
by /dev/sd?? does not match the component order.
Thanks in advance,
-Arthur
# mdadm -A /dev/md5
mdadm: /dev/md5 assembled from 2 drives - not enough to start the array.
# cat /proc/mdstat
...
md5 : inactive sdg2[0](S) sdj2[5](S) sdk2[4](S) sdl2[3](S) sdh2[2](S) sdi2[1](S)
2343866880 blocks
...
# mdadm -E /dev/sd[gjklhi]2 | egrep Events
Events : 0.9088480
Events : 0.9088480
Events : 0.9088476
Events : 0.9088476
Events : 0.9088476
Events : 0.9088476
# mdadm -E /dev/sd[gjklhi]2 | egrep this
this 0 8 98 0 active sync /dev/sdg2
this 2 8 114 2 active sync /dev/sdh2
this 1 8 130 1 active sync /dev/sdi2
this 5 8 146 5 active sync /dev/sdj2
this 4 8 162 4 active sync /dev/sdk2
this 3 8 178 3 active sync /dev/sdl2
# egrep '^DEVICE|md5' /etc/mdadm.conf
DEVICE /dev/sd??
ARRAY /dev/md5 level=raid5 num-devices=6 UUID=e49080f3:c60755cc:bef07a34:d5ceac64
# mdadm -E /dev/sd[gjklhi]2
/dev/sdg2:
Magic : a92b4efc
Version : 00.90.03
UUID : e49080f3:c60755cc:bef07a34:d5ceac64
Creation Time : Wed Feb 15 02:18:54 2006
Raid Level : raid5
Used Dev Size : 390644480 (372.55 GiB 400.02 GB)
Array Size : 1953222400 (1862.74 GiB 2000.10 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 5
Update Time : Wed Mar 19 07:43:46 2008
State : clean
Internal Bitmap : present
Active Devices : 2
Working Devices : 2
Failed Devices : 4
Spare Devices : 0
Checksum : 8cb597af - correct
Events : 0.9088480
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 98 0 active sync /dev/sdg2
0 0 8 98 0 active sync /dev/sdg2
1 1 0 0 1 faulty removed
2 2 8 114 2 active sync /dev/sdh2
3 3 0 0 3 faulty removed
4 4 0 0 4 faulty removed
5 5 0 0 5 faulty removed
/dev/sdh2:
Magic : a92b4efc
Version : 00.90.03
UUID : e49080f3:c60755cc:bef07a34:d5ceac64
Creation Time : Wed Feb 15 02:18:54 2006
Raid Level : raid5
Used Dev Size : 390644480 (372.55 GiB 400.02 GB)
Array Size : 1953222400 (1862.74 GiB 2000.10 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 5
Update Time : Wed Mar 19 07:43:46 2008
State : clean
Internal Bitmap : present
Active Devices : 2
Working Devices : 2
Failed Devices : 4
Spare Devices : 0
Checksum : 8cb597c3 - correct
Events : 0.9088480
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 2 8 114 2 active sync /dev/sdh2
0 0 8 98 0 active sync /dev/sdg2
1 1 0 0 1 faulty removed
2 2 8 114 2 active sync /dev/sdh2
3 3 0 0 3 faulty removed
4 4 0 0 4 faulty removed
5 5 0 0 5 faulty removed
/dev/sdi2:
Magic : a92b4efc
Version : 00.90.03
UUID : e49080f3:c60755cc:bef07a34:d5ceac64
Creation Time : Wed Feb 15 02:18:54 2006
Raid Level : raid5
Used Dev Size : 390644480 (372.55 GiB 400.02 GB)
Array Size : 1953222400 (1862.74 GiB 2000.10 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 5
Update Time : Wed Mar 19 00:56:18 2008
State : clean
Internal Bitmap : present
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Checksum : 8cb53801 - correct
Events : 0.9088476
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 8 130 1 active sync /dev/sdi2
0 0 8 98 0 active sync /dev/sdg2
1 1 8 130 1 active sync /dev/sdi2
2 2 8 114 2 active sync /dev/sdh2
3 3 8 178 3 active sync /dev/sdl2
4 4 8 162 4 active sync /dev/sdk2
5 5 8 146 5 active sync /dev/sdj2
/dev/sdj2:
Magic : a92b4efc
Version : 00.90.03
UUID : e49080f3:c60755cc:bef07a34:d5ceac64
Creation Time : Wed Feb 15 02:18:54 2006
Raid Level : raid5
Used Dev Size : 390644480 (372.55 GiB 400.02 GB)
Array Size : 1953222400 (1862.74 GiB 2000.10 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 5
Update Time : Wed Mar 19 00:56:18 2008
State : clean
Internal Bitmap : present
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Checksum : 8cb53819 - correct
Events : 0.9088476
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 5 8 146 5 active sync /dev/sdj2
0 0 8 98 0 active sync /dev/sdg2
1 1 8 130 1 active sync /dev/sdi2
2 2 8 114 2 active sync /dev/sdh2
3 3 8 178 3 active sync /dev/sdl2
4 4 8 162 4 active sync /dev/sdk2
5 5 8 146 5 active sync /dev/sdj2
/dev/sdk2:
Magic : a92b4efc
Version : 00.90.03
UUID : e49080f3:c60755cc:bef07a34:d5ceac64
Creation Time : Wed Feb 15 02:18:54 2006
Raid Level : raid5
Used Dev Size : 390644480 (372.55 GiB 400.02 GB)
Array Size : 1953222400 (1862.74 GiB 2000.10 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 5
Update Time : Wed Mar 19 00:56:18 2008
State : clean
Internal Bitmap : present
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Checksum : 8cb53827 - correct
Events : 0.9088476
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 4 8 162 4 active sync /dev/sdk2
0 0 8 98 0 active sync /dev/sdg2
1 1 8 130 1 active sync /dev/sdi2
2 2 8 114 2 active sync /dev/sdh2
3 3 8 178 3 active sync /dev/sdl2
4 4 8 162 4 active sync /dev/sdk2
5 5 8 146 5 active sync /dev/sdj2
/dev/sdl2:
Magic : a92b4efc
Version : 00.90.03
UUID : e49080f3:c60755cc:bef07a34:d5ceac64
Creation Time : Wed Feb 15 02:18:54 2006
Raid Level : raid5
Used Dev Size : 390644480 (372.55 GiB 400.02 GB)
Array Size : 1953222400 (1862.74 GiB 2000.10 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 5
Update Time : Wed Mar 19 00:56:18 2008
State : clean
Internal Bitmap : present
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Checksum : 8cb53835 - correct
Events : 0.9088476
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 3 8 178 3 active sync /dev/sdl2
0 0 8 98 0 active sync /dev/sdg2
1 1 8 130 1 active sync /dev/sdi2
2 2 8 114 2 active sync /dev/sdh2
3 3 8 178 3 active sync /dev/sdl2
4 4 8 162 4 active sync /dev/sdk2
5 5 8 146 5 active sync /dev/sdj2
next reply other threads:[~2008-03-22 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 2:40 Arthur Britto [this message]
2008-03-22 17:30 ` Help: Re-assemble raid-5 with inconsistent events Bill Davidsen
2008-03-22 20:14 ` Arthur Britto
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=1206153639.16304.30.camel@loss.redstem.com \
--to=ahbritto@iat.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).