All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wilson Jonathan <i400sjon@gmail.com>
To: o1bigtenor <o1bigtenor@gmail.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: moving a working array
Date: Fri, 24 Jun 2022 15:09:30 +0100	[thread overview]
Message-ID: <7683b644cf076f8db06d60fdd3e4f88424f35bd2.camel@gmail.com> (raw)
In-Reply-To: <CAPpdf595_7eW8amX8eueMxgjaWvLW-hWHh1SHHaGAt8YyP7yDw@mail.gmail.com>

On Fri, 2022-06-24 at 08:38 -0500, o1bigtenor wrote:
> Greetings
> 
> I have a working (no issues) raid-10 array in one box.
> 
> Want to move it to another (new) box.
> 
> Please - - - a list of the software steps?
> 
> (the physical moving is the easy part - - - the new box has room
> for a lot of drives and is ready for these 4 easily)
> 
> Just don't want a fubar situation because I've taken the wrong order
> or even wrong steps.

First make a backup...

Second check the backup...

Third make another backup...

Fourth check that backup as well...

Move disks... (I personally have just amended the /etc/mdadm/mdadm.conf
file to include the uuid prior to moving disks and been good to go. BUT
if I'd have lost all the data, without backups, I'd not have been
fussed as it could all have been recreated/downloaded so I guess it all
depends on how important or unique the data is.)

But if you've got a new machine, why not get new disks and set up a
nice new clean raid and then just rsync the data accross. That way your
old disks become the backup, to the data you've newly transfered to
clean a clean array. 

> 
> The section 'using the array' has information but I'm not sure how
> that will work moving from one box to the other.
> 
> (One question would be if the uuid of the array will remain the same
> as that would make things easier - - - I could copy the uuid from the
> existing and then just do the # mdadm --scan --assemble --uuid=
> blahblah )
> 
> TIA


  reply	other threads:[~2022-06-24 14:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 13:38 moving a working array o1bigtenor
2022-06-24 14:09 ` Wilson Jonathan [this message]
2022-06-24 14:49   ` Wols Lists
2022-06-27 10:41     ` what's wrong with RAID-10? (was "Re: moving a working array") David T-G
2022-06-27 15:10       ` Wols Lists
2022-06-27 15:23         ` what's wrong with RAID-10? David T-G
2022-06-27 18:41         ` what's wrong with RAID-10? (was "Re: moving a working array") Reindl Harald
2022-06-27 18:52           ` Wols Lists
2022-06-27 23:37             ` Reindl Harald

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=7683b644cf076f8db06d60fdd3e4f88424f35bd2.camel@gmail.com \
    --to=i400sjon@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.