From: Konstantin Olchanski <olchansk@sam.triumf.ca>
To: linux-raid@vger.kernel.org
Subject: Please help- raid1 recovery after disk failure
Date: Mon, 18 Oct 2004 15:56:52 -0700 [thread overview]
Message-ID: <20041018225652.GC29864@sam.triumf.ca> (raw)
Dear Linux raiders- I ran into a problem with raid1 recovery after
a disk failure (running Fedora2, kernel 2.6.8-1.521smp).
1) I had a raid1 filesystem mirrored across /dev/hda2 and /dev/hdc2.
2) Disk hda died (unreadable sectors, fails SMART tests)
3) A new blank hda was installed and partitionned exactly like hdc.
4) I cannot restart and rebuild the raid1 volume because hdc2 is
in a funny "spare" state (see below)
How do I mark hdc2 as "active"?
Once "active", I assume then I will be able to restart md0,
hot-add /dev/hda2 as usual. (And the mirror will resync and rebuild itself?
Hopefully?)
[root@tw04 root]# mdadm -E /dev/hdc2
/dev/hdc2:
Magic : a92b4efc
Version : 00.90.00
UUID : aade8782:20122089:4f496788:228d85b9
Creation Time : Fri Oct 8 17:12:56 2004
Raid Level : raid1
Device Size : 124158208 (118.41 GiB 127.14 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Mon Oct 18 06:04:35 2004
State : clean, no-errors
Active Devices : 1
Working Devices : 2
Failed Devices : 1
Spare Devices : 1
Checksum : 7041db42 - correct
Events : 0.312429
Number Major Minor RaidDevice State
this 2 22 2 2 spare /dev/hdc2
0 0 3 2 0 active sync /dev/hda2
1 1 0 0 1 faulty removed
2 2 22 2 2 spare /dev/hdc2
[root@tw04 root]#
--
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
next reply other threads:[~2004-10-18 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 22:56 Konstantin Olchanski [this message]
2004-10-18 23:22 ` Please help- raid1 recovery after disk failure Mike Tran
2004-10-27 4:20 ` Konstantin Olchanski
2004-10-18 23:28 ` Guy
2004-10-18 23:31 ` 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=20041018225652.GC29864@sam.triumf.ca \
--to=olchansk@sam.triumf.ca \
--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).