On 24/06/2022 15:09, Wilson Jonathan wrote:
On Fri, 2022-06-24 at 08:38 -0500, o1bigtenor wrote:
Greetings
I have a working (no issues) raid-10 array in one box.
Bummer. It's a raid-10. A raid-1 would have been easier.
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...
Seconded. And thirded and fourthed.
Actually, that might not be necessary ...
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.
Yup. Do you need the old disks in your new system? If not, DON'T MOVE
THEM and they'll be your backup.
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 )
Yup. If you move the disks, the UUID won't change.
What I went and did - which took some down-time because it was a pretty
big array ... was to create my new array on new disks in the new system.
Then I can't remember the syntax - I looked it up on the web - but I
just did a
cat //old-system/dev/old-array | network > //new-system/dev/newarray
So you're basically copying your filesystem across the network from the
old "disk" (array, actually) to the new equivalent on the new system.
Worked a treat, apart from the time it took ...
A major reason I went that route, rather than an rsync or whatever, is
that my system has hard-links all over the place, and while the various
filesystem copying mechanisms CAN handle it, they don't like it ... a
device copy simply doesn't need to know anything about it.
Cheers,
Wol
