linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam van Ratt <sam.vanratt@gmx.net>
To: linux-raid@vger.kernel.org,
	Michael Samer EPOS GmbH <michael.samer@epos-cat.de>
Subject: MDADM after QNAP Support disaster QNAP 859 Pro
Date: Sat, 27 Oct 2012 17:26:42 +0200	[thread overview]
Message-ID: <508BFD32.7010901@gmx.net> (raw)

Hello
a few days I received a NAS with 8 Slots. The original config consistet 
of 8* 2TB HDs as a RAID6 mdadm softraid system. After a normal reboot 
the array was no longer found, so QNAP was contacted.
The support told the keyuser todo this:


mdadm -D /dev/md0 (zeigt das gesamte RAID auf)
to assemble the HDs you have to:
mdadm -A /dev/md0 /dev/sda3.... (take care here, depending on the HDs 
they get a value like /dev/sdb3 dev/sdc3 ...) - with 8 HDs:
mdadm -A /dev/md0 /dev/sda3 /sdb3 /dev/sdc3 /dev/sdd3 /dev/sde3 
/dev/sdf3 /dev/sdg3 /dev/sdh3 (be careful with the order!)
If you get an error message about the assemble, you have to stop md0
mdadm -S /dev/md0 (stopping md0)
umount /dev/md0 (unmount of md0)

After serveral failed tries it endet in have a RAID 1 Konfig on sda and 
sdb but not seeing anything else of the config before (funnily only a 
500MB partition (as /dev/md9 sounds as a lot of tries).
As I'm not using mdadm in my workplace anywhere:

How can I delete the RAID1 (pretty simple I know) and reconstruct the R6 
Array without damaging the config further (and therefore the datas). The 
R6 should be about 11TiB usable size.
Is there a init build with searching for the old conifg? As R6 it should 
even be readable without sda or sdb if this should be needed. I manly 
use HW RAID Controller where a few (ICP, Infortrend, Areca)  which 
allows a reassembly by just declaring the disks as member to mdx and 
assemble then again; I hope mdadm could offer something similar


Cheers
Sam

             reply	other threads:[~2012-10-27 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-27 15:26 Sam van Ratt [this message]
2012-10-30  2:58 ` MDADM after QNAP Support disaster QNAP 859 Pro NeilBrown

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=508BFD32.7010901@gmx.net \
    --to=sam.vanratt@gmx.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=michael.samer@epos-cat.de \
    /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).