From: Miles Fidelman <mfidelman@traversetechnologies.com>
To: linux-raid@vger.kernel.org
Subject: rebuilding raided root partition
Date: Sat, 04 Apr 2009 22:31:32 -0400 [thread overview]
Message-ID: <49D81804.6070102@traversetechnologies.com> (raw)
Hi Folks,
I've been busily recovering from a bad crash (strangely enough, a single
disk drive failure that brought down an entire raided environment, with
spares).
I've pretty much recovered and rebuilt everything, EXCEPT....
my root partition is raided, and is now running only on its single spare
drive:
-----
server1:~# more /proc/mdstat
md2 : inactive sdd3[0] sdb3[2]
195318016 blocks
server1:~# mdadm --detail /dev/md2 [details omitted]
/dev/md2:
Raid Level : raid1
Device Size : 97659008 (93.13 GiB 100.00 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent
State : active, degraded
Active Devices : 0
Working Devices : 2
Failed Devices : 0
Spare Devices : 2
Number Major Minor RaidDevice State
0 8 51 0 spare rebuilding /dev/sdd3
1 0 0 - removed
2 8 19 - spare /dev/sdb3
------
note the line "spare rebuilding" - that's the result of: mdadm --add
/dev/md2 /dev/sdd3
unfortunately, it doesn't seem to really be doing anything - it's been
saying "rebuilding" for several hours
now for another mirror device, doing an mdadm --add, kicked off a resync
(as indicated by cat /proc/mdstat) that concluded just fine with a
rebuilt mirror array
but for this array, it just shows "active, degraged, and rebuilding" in
mdadm --detail, and "inactive" in /proc/mdstat
about the only difference I can see, is that the array that rebuilt
started with one primary drive, to which I added a 2nd drive, and then a
spare; the one that's hanging is running on a spare, and it thinks I'm
adding another spare (note: both serve as physical volumes underlying LVM)
so..... on to questions:
1. What's going on?
2. Any suggestions on how to reassemble the array? mdadm --assemble
/dev/md2 tells me I need to deactivate the device, but then, it's my /
volume - which leaves me a little stumped
Thanks very much,
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
next reply other threads:[~2009-04-05 2:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 2:31 Miles Fidelman [this message]
2009-04-05 6:54 ` rebuilding raided root partition Goswin von Brederlow
2009-04-05 13:31 ` Miles Fidelman
2009-04-05 21:35 ` Goswin von Brederlow
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=49D81804.6070102@traversetechnologies.com \
--to=mfidelman@traversetechnologies.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).