From: Roberto Nunnari <roberto.nunnari@supsi.ch>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: linux-raid@vger.kernel.org
Subject: Re: failed drive in raid 1 array
Date: Wed, 23 Feb 2011 20:16:17 +0100 [thread overview]
Message-ID: <4D655D01.6040803@supsi.ch> (raw)
In-Reply-To: <AANLkTim+Sz9Hrpu0rPQt2r4-SgmGEt1svsrs26Ejrkoq@mail.gmail.com>
Roberto Spadim wrote:
> sata2 without hot plug?
Hi Roberto.
I mean that there is no hot-plug bay, with sliding rails etc..
The drives are connected to the mb using standard sata cables.
> check if your sda sdb sdc will change after removing it, it´s depends
> on your udev or another /dev filesystem
Ok, thank you.
That means that if I take care to check the above, and
the new drive will be sdb, then taking the steps indicated
in my original post will do the job?
Best regards.
Robi
>
> 2011/2/23 Roberto Nunnari <roberto.nunnari@supsi.ch>:
>> Hello.
>>
>> I have a linux box, with two 2TB sata HD in raid 1.
>>
>> Now, one disk is in failed state and it has no spares:
>> # cat /proc/mdstat
>> Personalities : [raid1]
>> md1 : active raid1 sdb4[2](F) sda4[0]
>> 1910200704 blocks [2/1] [U_]
>>
>> md0 : active raid1 sdb1[1] sda2[0]
>> 40957568 blocks [2/2] [UU]
>>
>> unused devices: <none>
>>
>>
>> The drives are not hot-plug, so I need to shutdown the box.
>>
>> My plan is to:
>> # sfdisk -d /dev/sdb > sdb.sfdisk
>> # mdadm /dev/md1 -r /dev/sdb4
>> # mdadm /dev/md0 -r /dev/sdb1
>> # shutdown -h now
>>
>> replace the disk and boot (it should come back up, even without one drive,
>> right?)
>>
>> # sfdisk /dev/sdb < sdb.sfdisk
>> # mdadm /dev/md1 -a /dev/sdb4
>> # mdadm /dev/md0 -a /dev/sdb1
>>
>> and the drives should start to resync, right?
>>
>> This is my first time I do such a thing, so please, correct me
>> if the above is not correct, or is not a best practice for
>> my configuration.
>>
>> My last backup of md1 is of mid november, so I need to be
>> pretty sure I will not lose my data (over 1TB).
>>
>> A bit abount my environment:
>> # mdadm --version
>> mdadm - v1.12.0 - 14 June 2005
>> # cat /etc/redhat-release
>> CentOS release 4.8 (Final)
>> # uname -rms
>> Linux 2.6.9-89.31.1.ELsmp i686
>>
>> Thank you very much and best regards.
>> Robi
>> --
>> 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
>>
>
>
>
--
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:[~2011-02-23 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 16:52 failed drive in raid 1 array Roberto Nunnari
2011-02-23 17:56 ` Roberto Spadim
2011-02-23 18:20 ` Albert Pauw
2011-02-23 21:21 ` Roberto Nunnari
2011-02-24 21:51 ` Roberto Nunnari
2011-02-24 22:00 ` Roberto Spadim
2011-02-23 19:16 ` Roberto Nunnari [this message]
2011-02-23 19:20 ` Roberto Spadim
2011-02-23 21:24 ` Roberto Nunnari
2011-02-23 21:34 ` Roberto Spadim
2011-02-23 22:13 ` Roberto Nunnari
2011-02-24 16:05 ` Iordan Iordanov
2011-02-24 20:08 ` Roberto Spadim
2011-02-24 21:32 ` Iordan Iordanov
2011-02-24 21:38 ` Roberto Spadim
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=4D655D01.6040803@supsi.ch \
--to=roberto.nunnari@supsi.ch \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
/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).