From: CoolCold <coolthecold@gmail.com>
To: Leslie Rhorer <lrhorer@satx.rr.com>
Cc: Kyler Laird <kyler-keyword-linuxraid00.a7e7f0@lairds.com>,
linux-raid@vger.kernel.org
Subject: Re: recovering from a controller failure
Date: Sun, 30 May 2010 17:17:41 +0400 [thread overview]
Message-ID: <AANLkTim0Du0TYrTOQNajPG6IsDnj4aCvjZ3UJtZnweGW@mail.gmail.com> (raw)
In-Reply-To: <12.2A.01646.B8CD10C4@cdptpa-omtalb.mail.rr.com>
On Sun, May 30, 2010 at 7:33 AM, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
>> On Sun, May 30, 2010 at 09:50:26AM +1200, Richard wrote:
>>
>> > How about adding entries to your mdadm.conf file containing the UUID
>> > of /dev/md0, eg:
>> >
>> > ARRAY /dev/md8 level=raid6 num-devices=16
>> > UUID=38a06a50:ce3fc204:728edfb7:4f4cdd43
>> >
>> > note this should be all one line.
>>
>> I'll be happy to do that.
>>
>> > mdadm -D /dev/md0 should get you the UUID.
>>
>> root@00144ff2a334:/# mdadm -D /dev/md0
>> mdadm: md device /dev/md0 does not appear to be active.
>>
>> So...how do I get the UUIDs? I tried blkid and got this.
>> http://lairds.us/temp/ucmeng_md/uuids
>> Those UUIDs are far from unique.
>
> After all your drives are visible, of course:
>
> `mdadm --examine /dev/sd* /dev/hd* > <filename>`
> `more <filename>`
>
> Make note of the array UUID for each drive. When done,
>
> `mdadm --assemble --assume-clean /dev/mdX /dev/<drive0> /dev/<drive1>
> /dev/<drive2> ...etc`
>
> where <drive0>, <drive1>, etc are all members of the same array UUID.
>
> Mount the file system, and fsck it. Once everything is verified
> good,
>
> `echo repair > /sys/block/mdX/md/sync_action`
Taking in account "Events" fields are differing on disks from 1st &
2nd controller, interesting question for me - what will happen on this
"repair" ?
And what this "Events" field really means? I didn't found description
in man pages.
> `mdadm --examine --scan >> /etc/mdadm/mdadm.conf`
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Best regards,
[COOLCOLD-RIPN]
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-30 13:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 19:07 recovering from a controller failure Kyler Laird
2010-05-29 19:46 ` Berkey B Walker
2010-05-29 20:44 ` Kyler Laird
2010-05-29 21:18 ` Richard
2010-05-29 21:36 ` Kyler Laird
2010-05-29 21:38 ` Richard
2010-05-29 21:45 ` Kyler Laird
2010-05-29 21:50 ` Richard
2010-05-30 0:15 ` Kyler Laird
2010-05-30 0:28 ` Richard
2010-05-30 0:54 ` Richard
2010-05-30 3:33 ` Leslie Rhorer
2010-05-30 13:17 ` CoolCold [this message]
2010-05-30 22:38 ` Leslie Rhorer
2010-05-31 8:33 ` CoolCold
2010-05-31 8:50 ` Leslie Rhorer
2010-05-30 18:55 ` Richard Scobie
2010-05-30 22:23 ` Leslie Rhorer
2010-05-29 21:59 ` Richard
2010-05-29 21:43 ` Berkey B Walker
-- strict thread matches above, loose matches on Subject: below --
2010-05-31 18:27 Kyler Laird
2010-06-01 15:49 ` Kyler Laird
2010-06-01 19:15 ` Richard Scobie
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=AANLkTim0Du0TYrTOQNajPG6IsDnj4aCvjZ3UJtZnweGW@mail.gmail.com \
--to=coolthecold@gmail.com \
--cc=kyler-keyword-linuxraid00.a7e7f0@lairds.com \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.com \
/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).