From: Jean Jordaan <jean@upfrontsystems.co.za>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Recovering RAID5 array
Date: Tue, 20 Jan 2004 10:08:53 +0200 [thread overview]
Message-ID: <400CE215.2050502@upfrontsystems.co.za> (raw)
In-Reply-To: <16396.53737.911347.812076@notabene.cse.unsw.edu.au>
> mdadm --assemble /dev/md0 --force /dev/hd[abc]3
>
> should put it back together for you.
No luck ..
cdimage root # mdadm --verbose --assemble /dev/md0 --force /dev/hda3 /dev/hdb3
/dev/hdc3
mdadm: looking for devices for /dev/md0
mdadm: /dev/hda3 is identified as a member of /dev/md0, slot 3.
mdadm: /dev/hdb3 is identified as a member of /dev/md0, slot 4.
mdadm: /dev/hdc3 is identified as a member of /dev/md0, slot 2.
mdadm: no uptodate device for slot 0 of /dev/md0
mdadm: no uptodate device for slot 1 of /dev/md0
mdadm: added /dev/hda3 to /dev/md0 as 3
mdadm: added /dev/hdb3 to /dev/md0 as 4
mdadm: added /dev/hdc3 to /dev/md0 as 2
mdadm: /dev/md0 assembled from 1 drive - not enough to start it (use --run to
insist).
cdimage root # cat /proc/mdstat
Personalities : [raid5]
read_ahead not set
md0 : inactive ide/host0/bus1/target0/lun0/part3[2]
ide/host0/bus0/target1/lun0/part3[4] ide/host0/bus0/target0/lun0/part3[3]
0 blocks
unused devices: <none>
cdimage root # mdadm --verbose --examine /dev/hda3
/dev/hda3:
Magic : a92b4efc
Version : 00.90.00
UUID : dd5156aa:9157bc3c:9500db42:445b91fe
Creation Time : Wed Dec 17 11:44:50 2003
Raid Level : raid5
Device Size : 38001664 (36.24 GiB 38.91 GB)
Raid Devices : 3
Total Devices : 4
Preferred Minor : 0
Update Time : Mon Jan 19 07:41:21 2004
State : dirty, no-errors
Active Devices : 1
Working Devices : 3
Failed Devices : 1
Spare Devices : 2
Checksum : 736178ae - correct
Events : 0.82
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 3 3 3 3 /dev/ide/host0/bus0/target0/lun0/part3
0 0 0 0 0 faulty removed
1 1 0 0 1 faulty removed
2 2 22 3 2 active sync
/dev/ide/host0/bus1/target0/lun0/part3
3 3 3 3 3 /dev/ide/host0/bus0/target0/lun0/part3
4 4 3 67 4 /dev/ide/host0/bus0/target1/lun0/part3
I think /dev/hdb3 was the one originally marked faulty,
and I wrongly --set-faulty /dev/hda3 ..
--
Jean Jordaan
http://www.upfrontsystems.co.za
next prev parent reply other threads:[~2004-01-20 8:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 6:54 Recovering RAID5 array Jean Jordaan
2004-01-20 6:59 ` Neil Brown
2004-01-20 7:17 ` Jean Jordaan
2004-01-20 8:08 ` Jean Jordaan [this message]
2004-01-20 9:59 ` Neil Brown
2004-01-20 10:40 ` Jean Jordaan
2004-01-20 12:10 ` Maarten v d Berg
2004-01-20 12:23 ` Jean Jordaan
2004-01-20 12:57 ` Maarten v d Berg
2004-01-20 13:28 ` Jean Jordaan
2004-01-20 10:44 ` Jean Jordaan
2004-01-20 7:22 ` Guy
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=400CE215.2050502@upfrontsystems.co.za \
--to=jean@upfrontsystems.co.za \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).