From: Adam Goryachev <mailinglists@websitemanagers.com.au>
To: o1bigtenor <o1bigtenor@gmail.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Questions
Date: Sun, 14 Feb 2016 17:34:51 +1100 [thread overview]
Message-ID: <56C0200B.8030606@websitemanagers.com.au> (raw)
In-Reply-To: <CAPpdf58O+=Re1dBe1Rmj7jb=9iJkMZZBuZfEX4S32wMXcv6uWQ@mail.gmail.com>
On 14/02/2016 15:28, o1bigtenor wrote:
> Greetings
>
> My raid 10 array was the subject of a number of exchanges on this
> board a few months ago.
> With the generous assistance of members here things were reestablished
> and have been working well. Today I had a VirtualBox VM crater and in
> the process cause other system issues. In process to clear the mess a
> number of hard stops (shutting the system off using the button on the
> case) were used. In rebooting I found that one of the drives in the
> array is no longer responding issuing a number of clicks in the boot
> up process with nothing else happening. Even though it is a RAID 10
> array the array is no longer mounted nor available. I have removed the
> faulty drive already. I have an appropriately sized drive available
> that I could place into the machine.
>
> 1. should I reformat the drive (to be placed into the machine)?
> 2. what sequence of commands should I be using for this new drive to
> be included into the array?
> 3. what sequence of commands should I use to remount the array?
First thing I would suggest is to let everyone know the status of the
current array, and how to get it working.
Can you send the output of cat /proc/mdstat and mdadm --misc --detail
/dev/md?
Assuming the existing array is in a "normal" status, albeit degraded,
then it should be pretty simple to just partition the new drive to match
the other members, and then simply add the new partition to the array
(mdadm --manage /dev/md? --add /dev/sdxy)
Try to take things slowly, as doing the wrong thing might make a simple
recovery into a very sad event (loss of all the data).
Regards,
Adam
Regards,
Adam
next prev parent reply other threads:[~2016-02-14 6:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 4:28 Questions o1bigtenor
2016-02-14 6:34 ` Adam Goryachev [this message]
2016-02-14 11:53 ` Questions o1bigtenor
2016-02-14 12:24 ` Questions Adam Goryachev
2016-02-15 12:12 ` Questions o1bigtenor
2016-02-15 19:50 ` Questions Wols Lists
2016-02-15 21:01 ` Questions o1bigtenor
2016-02-15 22:05 ` Questions Adam Goryachev
2016-02-16 11:46 ` Questions o1bigtenor
2016-02-16 14:00 ` Questions Adam Goryachev
2016-02-16 18:33 ` Questions o1bigtenor
2016-02-16 14:32 ` Questions Wols Lists
2016-02-16 18:37 ` Questions o1bigtenor
2016-02-15 22:09 ` Questions Wols Lists
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=56C0200B.8030606@websitemanagers.com.au \
--to=mailinglists@websitemanagers.com.au \
--cc=linux-raid@vger.kernel.org \
--cc=o1bigtenor@gmail.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