From: Wols Lists <antlists@youngman.org.uk>
To: Nicolas Nicolaou <nicolaoun@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Problems with a RAID5 array
Date: Tue, 25 Oct 2016 13:48:24 +0100 [thread overview]
Message-ID: <580F5498.40902@youngman.org.uk> (raw)
In-Reply-To: <5C95474C-8A2A-4472-9629-2DD6B2143D28@GMAIL.COM>
On 25/10/16 08:45, Nicolas Nicolaou wrote:
> Hi all,
>
> I am a newbie in the RAID field but i encountered some problems
> with my RAID5 configuration on a QNAP NAS machine.
>
> In particular i added a 3TB drive and the array seemed to be rebuilt
> automatically. Originally i had 3 3TB drives on it.
> The rebuilt finished and i was able to access my data. For some weird reason
> one of the drives was not added and i tried to expand the RAID capacity.
> The expand failed but still no problems...
>
> When i rebooted the system however the RAID became inactive and
> now i cannot access any of the data.
>
> Below you can see the mdadm —examine information for the 4 drives.
>
> I saw a thread that recreating the RAID may solve the issue
> (https://raid.wiki.kernel.org/index.php/RAID_Recovery).
> Before going to that path though i wanted to see your take.
>
Firstly, using "--force" is not necessarily a bad idea, though you want
to avoid it if you can. Using "--create" is an absolutely crazy idea
unless you are being hand-held by an expert. DO NOT attempt that on your
own unless you really want to lose everything.
Secondly, if you *are* going to be mad enough to try "--create", make
sure you've run Phil's lsdrv utility and you have a hard copy of the
output saved somewhere safe!
Go back to the raid wiki, go to the home page, and read section 4, "When
things go wrogn". Read the entire section. It includes the page you've
referenced, but that's an old page that will be deprecated. It's a
moderately safe bet that when the experts chime in, they will want a lot
of the information that tells you to gather. And hopefully, working
through this will give you a few clues yourself.
Cheers,
Wol
next prev parent reply other threads:[~2016-10-25 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 7:45 Problems with a RAID5 array Nicolas Nicolaou
2016-10-25 12:48 ` Wols Lists [this message]
2016-10-25 17:54 ` Andreas Klauer
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=580F5498.40902@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=nicolaoun@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;
as well as URLs for NNTP newsgroup(s).