linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Powell <powellj@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Moving existing RAID5 disks to an alternate server
Date: Wed, 19 Jan 2011 19:05:52 -0800	[thread overview]
Message-ID: <AANLkTim4xsHXxBERJf0qucYgAizmzB8__66RR3XnT081@mail.gmail.com> (raw)

So practically speaking I don't have hardly any experience managing
RAID volumes. I have used some LSI web bios's to create RAID volumes
of various forms for functional dev/test and am familiar enough with
the terminology and implementation but when left with the choice of
building my own home NAS or buying some proprietary piece of hardware
pre-configured I chose the later in the interest of time and money.
Perhaps I made a poor choice there as my proprietary hardware died and
has left me with a seemingly intact RAID 5 volume spanned over 4 500GB
PATA disks. Seeing as how the hardware is bricked I am going to
attempt to pull out those disks and configure a RAID5 volume on a
custom built machine, (something I constructed over 5 years ago.. it
still as PATA interfaces :D ). The goal here is to copy the contents
of this volume to an alternate server that I will be using for backups
with some more updated hardware.

Anyhow, the point of my post: Is it really as simple as it sounds? Use
mdadm to recreate the RAID5 volume and away I go? Are there any
details that one can offer that I may need to be aware of or is simply
reading the man pages and various HOWTO's out on the net enough to get
started? Obviously I am taking this slow as the data on the disks is
important to me.

Thanks for your time in advance!

             reply	other threads:[~2011-01-20  3:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20  3:05 John Powell [this message]
2011-01-20  4:48 ` Moving existing RAID5 disks to an alternate server NeilBrown
2011-01-20 10:28 ` John Robinson

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=AANLkTim4xsHXxBERJf0qucYgAizmzB8__66RR3XnT081@mail.gmail.com \
    --to=powellj@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    /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).