From: likewhoa <likewhoa@weboperative.com>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: raid10 issues after reorder of boot drives.
Date: Fri, 27 Apr 2012 16:04:22 -0400 [thread overview]
Message-ID: <4F9AFBC6.7070803@weboperative.com> (raw)
I have a strange issue on my raid10 8x400GB array. I cannot assemble my
array anymore and it's gotten to a point that I don't know what to do to
recover my data. I was hoping I could get some advice on it. Below is
some info which I hope will help troubleshoot this issue.
> mdadm -Esv
ARRAY /dev/md/1 metadata=1.0 num-devices=0
UUID=828ed03d:0c28afda:4a636e88:7b29ec9f name=Darkside:1
spares=7
devices=/dev/sdg3,/dev/sdf3,/dev/sde3,/dev/sdd3,/dev/sdc3,/dev/sda3,/dev/sdb3
ARRAY /dev/md/1 level=raid10 metadata=1.0 num-devices=8
UUID=828ed03d:0c28afda:4a636e88:7b29ec9f name=Darkside:1
devices=8:131
> mdadm --version
mdadm - v3.2.3 - 23rd December 2011
> for i in /dev/sd{a,b,c,d,e,f,g,i}; do fdisk -l
${i};done
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4644f013
Device Boot Start End Blocks Id System
/dev/sda1 2048 2099199 1048576 82 Linux swap / Solaris
/dev/sda2 2099200 73779199 35840000 fd Linux raid
autodetect
/dev/sda3 73779200 976773119 451496960 fd Linux raid
autodetect
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e460f
Device Boot Start End Blocks Id System
/dev/sdb1 2048 2099199 1048576 82 Linux swap / Solaris
/dev/sdb2 2099200 73779199 35840000 fd Linux raid
autodetect
/dev/sdb3 73779200 976773119 451496960 fd Linux raid
autodetect
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x7d10530f
Device Boot Start End Blocks Id System
/dev/sdc1 2048 2099199 1048576 82 Linux swap / Solaris
/dev/sdc2 2099200 73779199 35840000 fd Linux raid
autodetect
/dev/sdc3 73779200 976773119 451496960 fd Linux raid
autodetect
Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x81a213ab
Device Boot Start End Blocks Id System
/dev/sdd1 2048 2099199 1048576 82 Linux swap / Solaris
/dev/sdd2 2099200 73779199 35840000 fd Linux raid
autodetect
/dev/sdd3 73779200 976773119 451496960 fd Linux raid
autodetect
Disk /dev/sde: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4644f00e
Device Boot Start End Blocks Id System
/dev/sde1 2048 2099199 1048576 82 Linux swap / Solaris
/dev/sde2 2099200 73779199 35840000 fd Linux raid
autodetect
/dev/sde3 73779200 976773119 451496960 fd Linux raid
autodetect
Disk /dev/sdf: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4644f00c
Device Boot Start End Blocks Id System
/dev/sdf1 2048 2099199 1048576 82 Linux swap / Solaris
/dev/sdf2 2099200 73779199 35840000 fd Linux raid
autodetect
/dev/sdf3 73779200 976773119 451496960 fd Linux raid
autodetect
Disk /dev/sdg: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x327d8d82
Device Boot Start End Blocks Id System
/dev/sdg1 2048 2099199 1048576 82 Linux swap / Solaris
/dev/sdg2 2099200 73779199 35840000 fd Linux raid
autodetect
/dev/sdg3 73779200 976773119 451496960 fd Linux raid
autodetect
Disk /dev/sdi: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e460f
Device Boot Start End Blocks Id System
/dev/sdi1 2048 2099199 1048576 82 Linux swap / Solaris
/dev/sdi2 2099200 73779199 35840000 fd Linux raid
autodetect
/dev/sdi3 73779200 976773119 451496960 fd Linux raid
autodetect
> uname -r
3.3.3-gentoo
Thanks in advanced.
next reply other threads:[~2012-04-27 20:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 20:04 likewhoa [this message]
2012-04-27 21:51 ` raid10 issues after reorder of boot drives likewhoa
2012-04-27 22:05 ` NeilBrown
2012-04-27 23:29 ` likewhoa
2012-04-28 0:24 ` NeilBrown
2012-04-28 0:35 ` likewhoa
2012-04-28 2:37 ` likewhoa
2012-04-28 2:55 ` NeilBrown
2012-04-28 2:59 ` likewhoa
2012-04-28 3:23 ` NeilBrown
2012-04-28 3:51 ` likewhoa
2012-04-28 15:23 ` likewhoa
2012-04-28 21:28 ` NeilBrown
2012-04-29 14:23 ` likewhoa
2012-04-27 22:03 ` NeilBrown
2012-04-27 23:26 ` likewhoa
2012-05-01 9:45 ` Brian Candler
2012-05-01 10:18 ` NeilBrown
2012-05-01 11:15 ` Brian Candler
2012-05-02 2:37 ` linbloke
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=4F9AFBC6.7070803@weboperative.com \
--to=likewhoa@weboperative.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).